@ Alpha32. As far as I know its a twitter glitch. As I get similar errors when browsing twitter on my browser. I have gone weeks with no problem, then have a string of No finds in a block of 3 hrs. And hadn't changed the code at all. Knowing twitter and the many glitches. I would say its a twitter api fail.
But if some one sees a glitch that could cause that in my code, do tell, cause I don't see anything that would cause it.