Here's an update: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/047365fe3cfa8a02
Taylor On Fri, Jul 16, 2010 at 12:35 AM, Tomo Osumi <tomo.os...@gmail.com> wrote: > Dear John, > > Great thanks for your info. > > My accounts to have streaming API traffic are @frostia_rina and > @frosita_solage . @frostia_rina is for garden hose on development > environment and @frostia_solage is for 'sample' on production > environment. The situation is the same as Tim. Both garden hose and > sample have 1/3 - 1/5 as much traffic as usual. Hope you rescue me. > > On 7ζ16ζ₯, εεΎ1:54, John Kalucki <j...@twitter.com> wrote: > > I hoped we'd have an email out on Thursday about this, but I'd imagine > it'll > > go out on Friday. There isn't a problem with your client. > > > > -John Kaluckihttp://twitter.com/jkalucki > > Infrastructure, Twitter Inc. > > > > > > > > On Thu, Jul 15, 2010 at 9:48 PM, Tim Haines <tmhai...@gmail.com> wrote: > > > This was addressed in a previous email to the list. @jkalucki > acknowledged > > > a bug and was going to report on it soon.. > > > > > On Fri, Jul 16, 2010 at 3:57 PM, Kam <kamerondeckerhar...@gmail.com > >wrote: > > > > >> Hi, we've noticed that we're receiving about 1/4-1/3 the number of > > >> tweets that were coming in two days ago. This seems to have begun the > > >> night of 14.07 at around 23:54 EST. The connection to the stream was > > >> dropped, and when our client automatically reconnected we saw this > > >> decrease in the number of messages received. > > > > >> Has anyone experienced a similar problem or know of a reason why this > > >> happened? > > > > >> Admins: I can send along our account information in a email if you > > >> think it might be a whitelisting problem. > > > > >> Thanks! >
