All is resolved now. Sorry for the interruption, everyone! There was a configuration error pushed to production at 5:15am Pacific Time. Alerts fired shortly after but did not page our on-call team due to another misconfiguration. We'll be fixing both of these problems today. Good news is that this had nothing to do with the throughput or scalability of the hub itself. Thanks for your patience.
-Brett On Wed, Feb 10, 2010 at 5:48 AM, [email protected] <[email protected]> wrote: > Hey there, > just a quick note, in case it's not a known problem already, the hub seems > to have completely stopped sending us (twitterfeed) notifications at ca. > 13:15 GMT today. I've checked with Julien from superfeedr, and he is seeing > the same, so looks like something broke? > Cheers, > Mario.
