If it appears to be taking slightly longer than usual to get fresh data from the API, that's intentional. One of the databases in our cluster went wonky over the weekend, and to weather the storm of traffic on Monday morning we're slowing down our rate of cache invalidation - but just slightly. You should never see responses more than 3 to 5 minutes out of date, which is within the realm of the default settings of most well-behaved Twitter clients.
As soon as the traffic surge wanes, we'll be back to normal. Thanks for your understanding. -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
