Is OpenAI down in the US?
Vendor reports no incidentWhat OpenAI reports
OpenAI reports no incident on its status page.
As of the last successful poll, 2026-11-05 14:34 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingin the US, measured from Ashburn, San Jose, and Chicago
All 3 of our probes in the US, in Ashburn, San Jose, and Chicago, read checks passing when they last checked OpenAI at Nov 5, 2026, 2:42 PM UTC.
Over the last 24 hours we completed 1387 checks from Ashburn, San Jose, and Chicago and 1387 answered cleanly, 100.00% availability.
Of the 7 other regions we check OpenAI from, all 7 read checks passing right now.
Email me when OpenAI reports an incident on its status page, and again when it reports it resolved.
What our Ashburn, San Jose, and Chicago probes measured
Last checked Nov 5, 2026, 2:42 PM UTC.
OpenAI from Ashburn, San Jose, and Chicago over the last 30 days
Over the last 30 days, OpenAI answered our San Jose probe in 333 ms on average, and 1 check in 20 took longer than 584 ms.
Over the last 30 days, OpenAI answered our Ashburn probe in 365 ms on average, and 1 check in 20 took longer than 616 ms.
Over the last 30 days, OpenAI answered our Chicago probe in 436 ms on average, and 1 check in 20 took longer than 837 ms.
Ranked by average response time across the 10 cities we check OpenAI from, San Jose 2nd, Ashburn 3rd, Chicago 5th; Frankfurt was fastest at 313 ms and Sydney slowest at 823 ms.
From Ashburn, San Jose, and Chicago we ran 51,819 checks of OpenAI in 30 days, and 51,814 answered cleanly: 99.99% availability.
5 of the 30 days had at least one failed check. The weakest was Nov 3 (UTC), at 99.92% across 1,345 checks.
In Ashburn local time (EST), OpenAI was slowest around 10 PM, at 539 ms on average over the last 14 days, and quickest around 2 PM, at 457 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 837 | 100.00% | 399 ms |
| Wed, Nov 4 | 1,373 | 100.00% | 387 ms |
| Tue, Nov 3 | 1,345 | 99.92% | 463 ms |
| Mon, Nov 2 | 1,618 | 100.00% | 474 ms |
| Sun, Nov 1 | 1,796 | 100.00% | 413 ms |
| Sat, Oct 31 | 1,795 | 100.00% | 455 ms |
| Fri, Oct 30 | 1,799 | 100.00% | 445 ms |
| Thu, Oct 29 | 1,791 | 100.00% | 496 ms |
| Wed, Oct 28 | 1,797 | 100.00% | 484 ms |
| Tue, Oct 27 | 1,796 | 100.00% | 507 ms |
| Mon, Oct 26 | 1,796 | 99.94% | 571 ms |
| Sun, Oct 25 | 1,794 | 99.94% | 543 ms |
| Sat, Oct 24 | 1,798 | 100.00% | 538 ms |
| Fri, Oct 23 | 1,800 | 100.00% | 480 ms |
OpenAI outages measured from the US
Our Ashburn, San Jose, and Chicago probes measured no confirmed OpenAI outage in the last 90 days.
How the other regions read right now
Of the 7 other regions we check OpenAI from, all 7 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 389 checks |
| Tokyo | Checks passing | 100.00% of 243 checks |
| Toronto | Checks passing | 100.00% of 357 checks |
| London | Checks passing | 100.00% of 357 checks |
| Singapore | Checks passing | 100.00% of 355 checks |
| Sydney | Checks passing | 100.00% of 352 checks |
| São Paulo | Checks passing | 100.00% of 355 checks |
Other countries we check OpenAI from
How we measured this
The US readings on this page come from RealUptime's own Ashburn, San Jose, and Chicago probes against OpenAI's public endpoints. They are not user reports, and they are not OpenAI's own status page.
See OpenAI's full check readings, the 90-day history by region, or the outage tracker methodology.
Check your own site from Ashburn
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter