Yes, this is a known issue. The process that feeds the public timeline
is particularly susceptible to database replication lag. We've just
added some capacity that should alleviate this issue.

On Tue, Mar 17, 2009 at 15:08, bootchec <[email protected]> wrote:
>
> Recently I have noticed that sometimes 
> http://twitter.com/statuses/public_timeline.rss
> returns bit odd results, which is the same time for each update and
> they are always old: 7-8 hours. And they are repeaded, so no matetr
> how many times I call it, it gives me the same updates. At the moment
> I tried it several times and I gotalwasy this as a first update:
> <title>
> billthomas: via Sammy Simpson @tunedin  Talk radio idea for this
> economy http://ow.ly/11w4
> </title>
> -
> <description>
> billthomas: via Sammy Simpson @tunedin  Talk radio idea for this
> economy http://ow.ly/11w4
> </description>
> <pubDate>Tue, 17 Mar 2009 14:17:49 +0000</pubDate>
> <guid>http://twitter.com/billthomas/statuses/1342266945</guid>
> <link>http://twitter.com/billthomas/statuses/1342266945</link>
> </item>
>



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

Reply via email to