Comcastbonnie confirms this is not unusual:

http://twitter.com/ComcastBonnie/statuses/13083585494


That this error happens for some and not others is not surprising.
With new focus on the Search API this type of issue can be addressed :)

Reply via email to