Same problem, I tried like 5 minutes per request, don’t know the reason why.
Same here. Fully paid account. 429s even when making 30 requests per hour. At a total loss with no comms from OpenAI…
1 Like
I’m a paid account. I meet this too…help. I make no more than 100 requests a day also not reach the limit…
This is so strange.
I make a lot of daily API calls, and have never had this problem except when I pulled 100s of text strings out of a DB and sent them to the embeddings API without a delay in the loop! That broken things fast, after a few iterations.
However, for all “normal” (not in a fast loop) API call, I have never had this issue, ever.
My best guess is that there is some “strangeness” going on with Cloudflare, based on some access / rate limiting criteria we are not aware of. It is also possible that OpenAI has been so busy that the have not updated their "work flow " to update Cloudflare rate limiting on a “per user” basis. However, I “think” (from all the posts here) the issue resides in Cloudflare.
You can see from this Cloudflare doc, that every user would have to match a criteria and the Cloudflare rate limiting rule updated / created:
I’m not a Cloudflare person (or a big fan of Cloudflare, TBH), but it does not seem “trivial” to set up Cloudflare on a “per user” basis based on a OpenAI plan which is outside of the Cloudflare ecosystem.
It could easily be possible that the OpenAI staff is not aware of what must happen on the Clouldflare end of things to support their new paid plans?
1 Like
I am have been seeing this issue for the past 12 hrs. I am a free account, but was considering moving to a paid account. I’ll be waiting to pay until I can at least see a request go through!
Someone above stated earlier that had success when changing models. Unfortunately, I see the same behavior regardless of using 001, 002, or 003.
Same issue here. Pay as you go, old account… should have 3,000 requests / minute as limit. Yet, keep receiving 429 - too many requests error, after only a couple of dozen requests in a row
Same here. Staff stand by to use the new functions built on top of this and it’s useless. Also a paid user. - I would say its getting worse.
Same here, I have paid plan and it’s getting worse, sometimes it’s smooth and sometimes all my API calls have 429 error as a response.
I am using cache in order to reduce the number of API calls, and I checked the number of call per minute and I am far far away from the limit.
1 Like
VERY intermittent yes.
Same here, GTP3 being a crucial part of my app, this will hopefully get fixed soon 
Same here - clearly an issue. Please fix asap
Please fix this, I’m tired of sending emails to our users saying that our servers are overloaded when they’re not…
1 Like
Same here, really annoying. Haveing a paid account and maybe sending 1 or 2 requests per minute for testing 
Sometimes its running, sometimes it fails
1 Like
You can add a test condition to your code and when the API is overloaded and fails, you can wait a few “random” seconds and resubmit.
It’s just a few lines of code. Of course, you will need to parse the API error messages and make sure it is a type of “overloading” issue, testing it, etc.
Maybe on every retry send an email to OpenAI support. Complaining haha 
3 Likes
It feels a bit wrong to implement a retry-mechanism when the API returns “too many requests” 
but I guess it will have to do for now.
1 Like
Make sure your account is attached to a card even if youre under the $18
I implemented retry logic in my code with a random time out and varied the davinci model, but still getting the too many requests. are you a paid account?
Similar issue here. Any requests through the API gives the same 429 error. Even sending a single request with the API playground gives the ‘You’ve reached your usage limit.’ error. I have a paid account, and am not even close to the usage limit. I tried creating a second account with a new email, credit card and phone number and got the same error.
Anyone else completely locked out of the API?
Just getting set up so could be a noob issue but my initial request are returning status code 429.
