It is really stupid. There is no news, nothing online. Nobody knows open ai has committed this blunder. And its been more than 6 hours now. We are exploring google’s api. There is too much reliance on openai!
This is usually how it goes with OpenAI: Minimal communications (if any), and never any follow-up.
I only use OpenAI servers for personal & development projects. For anything production-grade I highly recommend using something like Azure, atleast as a backup.
Expiring prepaid credits, constant unannounced changes, and extreme lack of support is enough to justify it.
I don’t have a negative balance but the $98.92 that should be there is gone. Had auto-recharge on and so it billed me the $25 that was set and that is all I have now as a balance. I went back to when I put the initial $100 on there and checked usage every month and total usage is $1.08 so the $98 I had on there wasn’t used, it just disappeared.
More than likely someone/something made a mistake causing all recent credit grants to expire.
OpenAI is shut down for the week, so I imagine there’s a lot of turmoil in their slack channel. They’re going to need to reconcile their ledger and fix all the mistakes while respecting all the current transactions.
Picture someone operating on a car… While it’s moving… And the top mechanics are currently in Costa Rica
If you are going to try and increase your balance: take a screenshot and write down the transaction ID, basically anything possible to prove what you’ve done, just in case that data is destroyed (unlikely but not zero)
OpenAI has always been generous with returning credits and even providing a little extra for the disruption. In the meantime your best bet is to have a backup system in place.
There is finally an update on https://status.openai.com/
I had the same issues here, but my balance has gone back to approximately what it was and it’s no longer negative. However, I’m still getting an error saying I don’t have enough quota.
Or rather, some CRON trigger runs that detects zero or negative account balances. It then shuts off the account.
Likely the only need then anticipated previously was to pay to turn an account back on. A new credit being received would switch an account from “status 429” to “useful”.
Chronology here:
- Yesterday “too many requests, slow down” when trying to make payments or add cards. This is a symptom seen before around the first of the month when OpenAI exceeds their Stripe account with auto-billings of monthly enterprise accounts (that take days to process through);
- Tons of accounts having “impossible” negative balance credit grant line items shown as a symptom at the start of this topic;
- That resulting in a large negative total “credit balance”.
- Also, recharges hitting cards against the errored balances - you can imagine this was an attempt against EVERY symptomatic organization set to recharge;
- then later in this topic, that errored balance then precipitating organization shutoffs.
We now have many org users that didn’t observe their screwed up account balance of negative hundreds or thousands of dollars - but still have the symptom of being shut off - contrary to “status”.
Still have the same quota error…
I got my credits back but the API still doesn’t work. Keeps failing with 429
I know that this practice is no real solution, but I recharged 10 dollar on top of my rewoked balance and my chat is working again. But I really have no clue if only the 10$ work or if the rest of my balance also is reactivated
Hi guys, I am having this error 429 problem as well, and I’ve been checking the OpenAI Status page, and they have updated the status there as a Partial Outage, let’s see if they are going to actually solve things
Thanks, this worked! Saved my over $100 credit balance with a new $5 charge
Got a support message via email that they solved it. But have still the API problem?
Automated systems: Wonderful for 99% of the time, absolute mayhem for the 1%.
So it’s clear that this issue has been ongoing since July 1st, causing a some of the billing API to lock down. Even bigger yikes.
Thanks, the APIs stopped giving 429s a small recharge.
Now in my case the situation has been resolved.
Wow…
What a day…