Rate limit exceeded for whitelisted app

12 views
Skip to first unread message

Yu-Shan Fung

unread,
Dec 2, 2008, 9:23:10 PM12/2/08
to twitter-deve...@googlegroups.com, Steve Ng Ming Yeow
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

unread,
Dec 2, 2008, 9:25:18 PM12/2/08
to twitter-deve...@googlegroups.com, Steve Ng Ming Yeow
No, there's no change in policy, but perhaps we have a bug. Yours is
the second report of a rate limit issue.

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

Alex Payne

unread,
Dec 2, 2008, 9:37:43 PM12/2/08
to twitter-deve...@googlegroups.com, Steve Ng Ming Yeow
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.

Yu-Shan Fung

unread,
Dec 2, 2008, 9:39:49 PM12/2/08
to twitter-deve...@googlegroups.com
Thanks for being so responsive. You guys rock!
--
"Reality is that which, when you stop believing in it, doesn't go away."
- Philip K. Dick, American Writer

Alex Payne

unread,
Dec 2, 2008, 10:15:19 PM12/2/08
to twitter-deve...@googlegroups.com
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.

Jesse Stay

unread,
Dec 3, 2008, 4:27:25 AM12/3/08
to twitter-deve...@googlegroups.com
Any idea how long this has been going on for?  I've had  a few users complaining about my script not working and I want to verify if this was the cause.

Thanks,

Jesse

fastest963

unread,
Dec 3, 2008, 6:40:35 AM12/3/08
to Twitter Development Talk
It seems they are still restoring the database...

DustyReagan

unread,
Dec 3, 2008, 3:05:43 AM12/3/08
to Twitter Development Talk
Same problem here. Glad to hear you guys are on it. :)

Dusty

On Dec 2, 9:15 pm, "Alex Payne" <a...@twitter.com> wrote:
> 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 <ambivale...@gmail.com> wrote:
> > Thanks for being so responsive. You guys rock!
>
> > On Tue, Dec 2, 2008 at 6:37 PM, Alex Payne <a...@twitter.com> 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 <a...@twitter.com> 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 <ambivale...@gmail.com>

Swap

unread,
Dec 3, 2008, 3:10:27 AM12/3/08
to Twitter Development Talk
Thanks Alex!

On Dec 3, 8:15 am, "Alex Payne" <a...@twitter.com> wrote:
> 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 <ambivale...@gmail.com> wrote:
> > Thanks for being so responsive. You guys rock!
>
> > On Tue, Dec 2, 2008 at 6:37 PM, Alex Payne <a...@twitter.com> 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 <a...@twitter.com> 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 <ambivale...@gmail.com>

Michael E. Carluen

unread,
Dec 3, 2008, 1:44:57 AM12/3/08
to twitter-deve...@googlegroups.com
Alex, Seems like my whitelisted app got hit by this. Currently, 10:45pm PST
and TwitWall.com is getting hit by the rate limit.

Thanks in advance.
Michael E. Carluen

fastest963

unread,
Dec 3, 2008, 10:36:48 AM12/3/08
to Twitter Development Talk
It looks like IPs still work? Twittertrend is still running perfectly
fine?
I think whitelisted users/IPs are hitting the rate_limit but the API
isn't acknowledging it? My "remaining_hits" is -36 but my API requests
are still processing fine.

Alex Payne

unread,
Dec 3, 2008, 11:54:51 AM12/3/08
to twitter-deve...@googlegroups.com
The database restore is complete, everything should be back to normal.

--

Bruno G

unread,
Dec 3, 2008, 12:51:48 PM12/3/08
to Twitter Development Talk
Great! Thanks for being on top of it.

On Dec 3, 11:54 am, "Alex Payne" <a...@twitter.com> wrote:
> The database restore is complete, everything should be back to normal.
>
Reply all
Reply to author
Forward
0 new messages