The updated estimate I've just received from our ops guys is "more than 15 minutes and less than 12 hours". They have to restore from a nightly database backup. Said backups are quite large, and take some time to get through. Thanks for your patience.
On Tue, Dec 2, 2008 at 18:39, Yu-Shan Fung <[EMAIL PROTECTED]> wrote: > Thanks for being so responsive. You guys rock! > > On Tue, Dec 2, 2008 at 6:37 PM, Alex Payne <[EMAIL PROTECTED]> wrote: >> >> Just talked to our Operations team. It looks like some database >> maintenance inadvertently truncated our table of whitelisted users. >> We're restoring that as I type and everything will be back to normal >> shortly. >> >> On Tue, Dec 2, 2008 at 18:25, Alex Payne <[EMAIL PROTECTED]> wrote: >> > No, there's no change in policy, but perhaps we have a bug. Yours is >> > the second report of a rate limit issue. >> > >> > On Tue, Dec 2, 2008 at 18:23, Yu-Shan Fung <[EMAIL PROTECTED]> >> > wrote: >> >> Hi, >> >> Our app (mrtweet.net), which has been whitelisted (@mrtweet) since a >> >> couple >> >> of weeks back, has suddenly began seeing the "rate limit exceeded" >> >> error >> >> since around 3:45pm (pacific) today. Was there a change in policy, or >> >> do I >> >> have to reapply for whitelisting? >> >> Thanks! >> >> Yu-Shan. >> >> >> > >> > >> > >> > -- >> > Alex Payne - API Lead, Twitter, Inc. >> > http://twitter.com/al3x >> > >> >> >> >> -- >> Alex Payne - API Lead, Twitter, Inc. >> http://twitter.com/al3x > > > > -- > "Reality is that which, when you stop believing in it, doesn't go away." > - Philip K. Dick, American Writer > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
