Request failed with status 429

Comentários

• u/AutoModerator·1·1 de ago. de 2026, 17:05

  Hey /u/Siodmak,

  If your post is a screenshot of a ChatGPT conversation, please reply to this message with the conversation link or prompt.

  If your post is a DALL-E 3 image post, please reply with the prompt used to make this image.

  Consider joining our public discord server! We have free bots with GPT-4 (with vision), image generators, and more!

  🤖

  Note: For any ChatGPT-related concerns, email support@openai.com - this subreddit is not part of OpenAI and is not a support channel.

  I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

• u/AutoModerator·1·1 de ago. de 2026, 17:05

  Attention! [Serious] Tag Notice

  : Jokes, puns, and off-topic comments are not permitted in any comment, parent or child.

  : Help us by reporting comments that violate these rules.

  : Posts that are not appropriate for the [Serious] tag will be removed.

  Thanks for your cooperation and enjoy the discussion!

  I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

• u/CharlesPrawnson·1·1 de ago. de 2026, 17:10

  The screenshot describes a user who: Initially subscribed to the €100 Pro tier. Hit a usage limit after two days of heavy use. Upgraded to the €200 tier. An hour later is still receiving: HTTP 429 (“Request failed with status 429”) A message saying they’ve reached the message limit. The problem affects every model, not just the newest ones. A 429 almost always means the service is temporarily refusing requests because of rate limiting or quota enforcement. The important part is that they upgraded only an hour earlier. There are a few likely explanations: The new subscription hasn’t propagated yet. Billing changes can take some time to become effective across all backend systems. Logging out and back in, or waiting a bit longer, can resolve this. They exhausted a rolling rate limit, not their plan quota. Some limits are based on requests over a time window. Upgrading doesn’t necessarily reset those immediately. A temporary backend issue. If every model returns 429, it’s less likely to be a single-model quota and more likely an account-level service issue. Account synchronization problem. The account may show the upgraded plan in billing while the inference service still sees the old entitlement. The practical troubleshooting sequence would be: Verify the upgraded subscription is active in the account’s billing page. Sign out and back in. Try another device or browser. Wait another hour or two if the upgrade was very recent. Check the service status page for any ongoing incidents. If the problem persists after several hours, contact support and include: the exact 429 error, approximate time of the upgrade, the fact that all models are affected. One thing that stands out is that the user says older models are also unavailable. That makes this look less like they simply exhausted GPT-5 usage and more like an account-level quota or entitlement issue. From what you’ve shared, I would not assume the upgrade “didn’t work.” I would first suspect propagation delay or an account synchronization issue before concluding anything more serious.