OpenAI · API & platform status
ChatGPT, GPT-4o, GPT-4, o1, o3, DALL-E, Whisper, and OpenAI API platform services.
Official status data last reflected here:
[ STATUS AT A GLANCE ]
Current status of individual OpenAI services
When OpenAI has issues, Bifrost automatically routes your requests to a healthy alternative provider. Zero code changes. 99.999% effective uptime.
What OpenAI does, where the data on this page comes from, and recent reliability
[ ABOUT OPENAI ]
OpenAI provides ChatGPT, OpenAI API, GPT-4o, and o-series reasoning models. Teams depend on OpenAI for both end-user chat products and API-driven application traffic, so even short disruptions can affect support, automation, and revenue-critical workflows.
This page pulls data from OpenAI's official status page to show current service health, any active incidents, and a history of recent issues, all in one view.
[ DATA SOURCES ]
OpenAI publishes detailed component status, a full incident archive, and scheduled maintenance data through their official status page.
[ RELIABILITY ]
[ COMMON USE CASES ]
Teams depend on OpenAI for both end-user chat products and API-driven application traffic, so even short disruptions can affect support, automation, and revenue-critical workflows.
Active incidents, scheduled maintenance, and incident history for OpenAI
Nov 6, 2026
We’ve applied a mitigation and are monitoring the affected services to confirm recovery.
Investigating — We’re seeing payment declines on some U.S. business Mastercards. Affected cards have numbers beginning with 544015, 546400, 543502, 543799, or 512998. Some cards beginning with 513989 are also affected. For API customers, this can prevent automatic recharges and one-time credit purchases. If your prepaid balance runs out, your API requests may fail. If you use one of these cards, we recommend adding a card from a different issuer before your next payment, even if you haven’t seen a decline. If an API credit purchase has already failed, use the new card to retry the purchase. We’re working with our payment partners and will share updates here.
**Investigating — We’re seeing payment declines on some U.S. business Mastercards. Affected cards have numbers beginning with 544015, 546400, 543502, 543799, or 512998. Some cards beginning with 513989 are also affected.** **For API customers, this can prevent automatic recharges and one-time credit purchases. If your prepaid balance runs out, your API requests may fail.** **If you use one of these cards, we recommend adding a card from a different issuer before your next payment, even if you haven’t seen a decline. If an API credit purchase has already failed, use the new card to retry the purchase.** **We’re working with our payment partners and will share updates here.**
Nov 5, 2026 · Resolved Nov 6, 2026
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
We’ve applied a mitigation and are monitoring the affected services to confirm recovery.
We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.
We’re investigating a potential issue for the listed services and checking how it affects users. We’ll share an update when we know more.
We’re investigating a potential issue for the listed services and checking how it affects users. We’ll share an update when we know more.
+ 1 more updates
Nov 4, 2026 · Resolved Nov 5, 2026
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
We’ve applied a mitigation and are monitoring the affected services to confirm recovery.
Some users on paid ChatGPT plans may see errors when sending messages. We are working on implementing a mitigation.
Nov 3, 2026 · Resolved Nov 3, 2026
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
We’ve applied a mitigation and are monitoring the affected services to confirm recovery.
We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.
We’re investigating a potential issue for the listed services and checking how it affects users. We’ll share an update when we know more.
Some users are having trouble uploading files to ChatGPT or getting ChatGPT to read uploaded files. We are working on implementing a mitigation.
Oct 30, 2026 · Resolved Oct 30, 2026
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
We’re aware of issues affecting search in Dots, ChatGPT Work, and some ChatGPT thinking experiences. We’re investigating and will share updates here.
Oct 30, 2026 · Resolved Oct 30, 2026
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
We’ve applied a mitigation and are monitoring the affected services to confirm recovery.
We are experiencing elevated errors for some GPT Image 2 API image edit requests. We have identified the issue and are working on a fix
Oct 27, 2026 · Resolved Oct 27, 2026
All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
We’ve applied a mitigation and are monitoring the affected services to confirm recovery.
We’re investigating a potential issue for the listed services and checking how it affects users. We’ll share an update when we know more.
Oct 27, 2026 · Resolved Oct 27, 2026
The issue is now resolved.
We’ve applied a mitigation and are monitoring the affected services to confirm recovery.
We’re investigating a potential issue for the listed services and checking how it affects users. We’ll share an update when we know more.
Oct 26, 2026 · Resolved Oct 26, 2026
All impacted services have now fully recovered.
We have applied the mitigation and are monitoring the recovery.
We have identified that users are experiencing elevated errors for POST /ads/* endpoints. We are working on implementing a mitigation.
Oct 23, 2026 · Resolved Oct 23, 2026
All impacted services have now fully recovered.
Some ChatGPT app connections experienced failures when connecting a new app or refreshing an existing connection. The affected authentication metadata endpoint is available again, and we are monitoring recovery.
We have applied the mitigation and are monitoring the recovery.
We are investigating the issue for the listed services.
Oct 23, 2026 · Resolved Oct 23, 2026
All impacted services have now fully recovered.
We have applied the mitigation and are monitoring the recovery.
We’re currently experiencing degraded performance with the Help Center chat support experience. While we work to resolve the issue, we recommend contacting our Support team via email at [support@openai.com](mailto:support@openai.com "support@openai.com") for assistance. We apologize for the inconvenience and will provide updates as they become available.
Oct 23, 2026 · Resolved Oct 23, 2026
All impacted services have now fully recovered.
We have applied the mitigation and are monitoring the recovery.
A fix is being implemented for the issue affecting our support systems. Customers may continue to experience delays in receiving support responses. We will provide further updates as recovery progresses.
As a temporary solution, customers looking to reach out to OpenAI Support can email [support@openai.com](mailto:support@openai.com "support@openai.com").
We are investigating technical issues affecting our customer support systems. Customers may experience longer than usual response times. We are working to restore normal operations.
Oct 22, 2026 · Resolved Oct 23, 2026
All impacted services have now fully recovered.
We have applied the mitigation and are monitoring the recovery.
We have identified the issue and are working to implement the mitigation.
We have identified that new ad accounts are failing to assign their creator admin. We are investigating the issue.
Oct 22, 2026 · Resolved Oct 22, 2026
All impacted services have now fully recovered.
Our teams have identified the issue and are actively implementing a mitigation. At this time the majority of impact is affecting enterprise customers.
Users are experiencing failures sending messages to dots.
Oct 22, 2026 · Resolved Oct 22, 2026
All impacted services have now fully recovered.
This is impacting users in India, Japan, and Korea. We have applied the mitigation and are monitoring the recovery.
This is impacting users in India, Japan, and Korea. We are investigating the issue for the listed services.
Oct 21, 2026 · Resolved Oct 21, 2026
All impacted services have now fully recovered.
We have applied the mitigation and are monitoring the recovery.
We are investigating the issue for the listed services.
We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.
Oct 21, 2026 · Resolved Oct 21, 2026
All impacted services have now fully recovered.
We have applied the mitigation and are monitoring the recovery.
We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.
Oct 21, 2026 · Resolved Oct 21, 2026
All impacted services have now fully recovered.
We have applied the mitigation and are monitoring the recovery.
We are investigating the issue for the listed services.
Oct 21, 2026 · Resolved Oct 20, 2026
On October 20, from 9:35 to 10:35 a.m. PDT, some users near Illinois experienced authentication errors with the API, ChatGPT, and Codex. We rolled back a configuration change, and service was restored.
Some users near Illinois experienced authentication errors with the API, ChatGPT, and Codex.
Oct 19, 2026 · Resolved Oct 19, 2026
All impacted services have now fully recovered.
We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.
Oct 14, 2026 · Resolved Oct 16, 2026
All impacted services have now fully recovered.
We have deployed a fix and are monitoring recovery. Costs data in the Compliance API remains delayed while we process the backlog. We will provide further updates as processing catches up.
We have identified an issue causing delays in publishing organization cost data through the Costs API. A fix is in progress and currently undergoing testing. API and ChatGPT usage are not affected, and other reporting channels remain available. We are continuing work to restore normal data freshness.
We have identified an issue causing delays in publishing organization cost data through the Costs API. API and ChatGPT usage are not affected, and other reporting channels remain available. We are working to restore normal data freshness.
We have identified an issue causing delays in publishing organization cost data through the Costs API. API and ChatGPT usage are not affected, and other reporting channels remain available. We are working to restore normal data freshness.
Check the status indicator at the top of this page. It pulls directly from OpenAI's official status page. If OpenAI is experiencing any issues, you'll see it reflected here. This real-time monitoring helps teams quickly identify whether performance problems are caused by OpenAI infrastructure or their own systems.
This page tracks ChatGPT, OpenAI API, GPT-4o, o-series reasoning models, and DALL-E using data from OpenAI's official status page. You can see current component health, active incidents, and a history of past issues. This visibility is crucial for teams building resilient AI applications that need to route around provider outages.
We check OpenAI's status page every 60 seconds to ensure you get near real-time status updates. How quickly issues show up here depends on how fast OpenAI updates their own official status. For production systems that need instant failover, Bifrost can automatically detect and route around degraded providers.
Teams depend on OpenAI for both end-user chat products and API-driven application traffic, so even short disruptions can affect support, automation, and revenue-critical workflows. Real-time status monitoring enables proactive incident response and helps teams decide when to route traffic to alternative providers for maximum uptime.
When OpenAI experiences an outage, the best practice is automatic failover to alternative AI providers. Bifrost is an open-source AI gateway that automatically detects OpenAI degradation and routes LLM traffic to healthy alternatives like Anthropic (Claude), Azure OpenAI, Groq, keeping your application running with zero manual intervention. This intelligent routing ensures your users never experience downtime from a single provider's issues.
Production AI applications should never depend on a single provider. Bifrost AI Gateway provides automatic multi-provider failover, intelligent load balancing, and health-based routing. When OpenAI degrades, Bifrost instantly routes requests to operational alternatives while maintaining API compatibility. This architecture approach is used by teams running mission-critical AI features.
Common causes of OpenAI issues include infrastructure scaling challenges, regional cloud provider problems, API gateway overload, and deployment errors. Monitor this page to stay informed, and consider implementing automatic failover with Bifrost to maintain uptime during OpenAI incidents.
When OpenAI experiences issues, Bifrost AI Gateway can automatically route your LLM traffic to these alternatives
💡 Build resilient AI apps: Configure Bifrost to automatically detect OpenAI outages and route requests to healthy alternatives. This multi-provider approach ensures your application maintains uptime even when individual providers experience issues. Learn more about Bifrost AI Gateway
OpenAI offers 160 models across 8 modes (103 chat, 24 responses, 11 image generation, 9 realtime, 5 audio transcription, 4 embedding, 3 audio speech, 1 decisions)