Home → Problems →

Rate limit exceeded - please wait 1 minute before shortening further URLs.

robtlee

28 Apr, 2011 02:07 PM via web

Admin Functions

• Edit
• Remove

This seems to be an ongoing issue.

1. I have a bit.ly API key. Still getting this error at least once per day.
2. I have contacted bit.ly and they haven't been able to help.
3. I have read your suggestions that "It isn't your problem". It is. Please help fix this with us. Or tell us what is going on to fix it. Tweethopper is your service and if a 3rd party app is not working correctly with your service, you should be engaged at helping solve it.
4. Please take a look at my settings and let me know the best way to fix it.
   The account is under @sansforensics

Carving SQLite databases from unallocated clusters Error: Rate limit exceeded - please wait 1 minute before shortening further URLs.
PlayStation data theft hits 70m gamers Error: Rate limit exceeded - please wait 1 minute before shortening further URLs.

1. Support Staff 2 Posted by Paolo Miguel on 01 May, 2011 05:33 PM

   

   Robtlee,

   Thanks for contacting us. We will look into this asap. We'll keep you posted.

   Paolo

   Admin Functions

   • Edit
   • Remove

2. Support Staff 3 Posted by Josh Owens on 02 Jun, 2011 04:09 AM

   

   Hey guys,

   It took us a while, but as part of our major overhaul this weekend, we wrote a new url shortener, twthpr.co! This seems to have resolved the issue for people not using custom bit.ly keys. If you are using a custom key and getting the error, please let me know.

   I am excited to get this bug resolved! Thanks for reporting it robtlee.

   Admin Functions

   • Edit
   • Remove

3. Josh Owens closed this discussion on 02 Jun, 2011 04:09 AM.

4. robtlee re-opened this discussion on 02 Jun, 2011 06:49 PM

5. 4 Posted by robtlee on 02 Jun, 2011 06:49 PM

   

   I am using a custom bit.ly API Key and it has been happening. R_454e13e21a3259b103bef76a8e5d2eff

   I keep getting complaints about it and am looking at other solutions, but am encouraged you are looking at it.

   What are the next steps? And why is my custom API key failing?

   Admin Functions

   • Edit
   • Split
   • Remove

6. Support Staff 5 Posted by Josh Owens on 02 Jun, 2011 06:55 PM

   

   Robtlee,

   The error was from is.gd, we had some logic errors that caused it to use that automatically and they started rate limited us a few months ago.

   I have taken a couple steps to resolve the issue, and looking at your feed, you are fixed since we launched the new code on Tuesday evening:

   1) We fixed the code up to work for custom bit.ly key accounts

   2) We created twthpr.co shortener for people who don't care about stats and don't use bit.ly. There is no rate limit, it just works.

   We are also working on a new UI that is easy to understand and configure so we can add more options like how often to check a feed, how often to post, etc. Our new job code is much easier to change and monitor for bugs, so we are keeping a close eye on it!

   Thanks again for your patience with this bug.

   Admin Functions

   • Edit
   • Remove

7. Support Staff 6 Posted by Paolo Miguel on 03 Jul, 2011 08:04 PM

   

   Robtlee,

   I believe this issue has already been resolved. Don't hesitate to contact us should you need further assistance. Thanks!

   Paolo

   Admin Functions

   • Edit
   • Remove

8. Paolo Miguel closed this discussion on 03 Jul, 2011 08:04 PM.

Comments are currently closed for this discussion. You can start a new one.