#19

Yes, as it seems it should be affecting all users.

#20

Many thanks for confirming that. I’m surprised there isn’t more internet chatter about this bug. There must be many developers/users pulling their hair out with frustration. At least the twitter people are ‘on the case’. Hope a solution is found sooner than a week!.

#21

We are seeing much more that 10:1 drops in the number of results. In some cases, we are seeing 50:1 drops. Practically no results.

Here’s a picture of such a case: http://twitter.yfrog.com/z/h621edp

#22

Unfortunately not, we’ll just have to wait for the fix.

#23

OK, Is there an updated ETA on this? This is seriously affecting our site (http://trendsmap.com/) along with a number of our clients, so would be great to at least have something more concrete to work with. Thanks!

#24

As soon as possible please!! Thanks.

#25

Any update on ETA to fix?

#26

Taylor, can you update us on this issue? Thanks.

#27

Any update on when this will be fixed?

#28

Has anyone seen a fix for this? Or at least as ETA?

#29

+1

#30

+1
I’ve seen some spikes in our feeds over the 5th and 6th and a 55 minute flat spot early am on 7th, but there appears to be no fix yet?

#31

Our engineers have completed the fix – the proper indexing based on user-defined locations should be correct for recent tweets forward now (Tweets that were already indexed prior to today’s fix are not being re-indexed retroactively).

Please keep in mind that you won’t see exactly the same behavior or result set breadth you may have been used to with the former geocoding provider we used – it’s likely you’ll see less results than you saw a month ago, but you’ll definitely see more than when we were in the buggy state last week.

#32

I can confirm that I’m seeing increased volume now, thanks! I’ll keep an eye on it and will report back about the difference compared to the previous geocoding provider.

#33

Yes, things seem back to where they were before, or at least very close to it. Thanks.

#34

Whippeedo! Elvis is back in the building. Thanks Twitter Team.

#35

Glad things are back to a predictable fidelity. Thanks again for your patience.

#36

As of 31 October 2013, this problem has reappeared !!! Please help!!

#37

Yep, I am seeing this as well. Not as dramatic a drop as the previous issue, but still a drop nonetheless.

#38

Yep, I am seeing this as well. Not as dramatic a drop as the previous issue, but still a drop nonetheless.