Skip to content

Outage tracker / OpenAI

Is OpenAI down?

I'm having a problem

Operationalchecked 1 minute ago

We reached OpenAI from all 10 regions we check.

As of Oct 5, 2026, 8:16 PM UTC, OpenAI answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

Last outage: 11 min on Aug 28, 2026 (API, from Europe, US-East and US-West).

OpenAI reports an active incident: "Elevated error rates in Codex Cloud" (all systems operational, since Oct 5, 2026, 5:58 PM UTC). That is their claim, not our measurement: our probes are currently reaching OpenAI, and an incident they declare can affect parts of the service our checks do not exercise. We show both and never merge them.

our independent probeslive · checked Oct 5, 2026, 8:16 PM UTC
US-East134 msOperational
US-West113 msOperational
Europe256 msOperational
Asia-Pacific210 msOperational
US-Central118 msOperational
Canada124 msOperational
UK462 msOperational
Southeast Asia239 msOperational
Australia575 msOperational
South America430 msOperational
their status pagetheir claim, not our reading

OpenAI reports: Minor incident (“Partial System Degradation”)

from OpenAI's own status page, checked Oct 5, 2026, 7:52 PM UTC

OpenAI reports an active incident: Elevated error rates in Codex Cloud (all systems operational, since Oct 5, 2026, 5:58 PM UTC)

OpenAI's status page reports Partial System Degradation. Our probes are currently reaching OpenAI successfully with normal latency. RealUptime's independent checks are currently succeeding from all 10 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show what we measured, not what they report: differences can mean a partial or user-specific issue that a simple reachability check won't catch. Read both before you draw a conclusion.

OpenAI's own component breakdown, as they publish it

  • Chat CompletionsOperational
  • ResponsesOperational
  • AgentsOperational
  • DecisionsOperational
  • Fine-tuningOperational
  • EmbeddingsOperational
  • ImagesOperational
  • BatchOperational
  • AudioOperational
  • ModerationsOperational
  • RealtimeOperational
  • FilesOperational
  • LoginOperational
  • ConversationsDegraded performance
  • LoginOperational
  • ChatGPT WorkDegraded performance
  • Codex in ChatGPT DesktopDegraded performance
  • Compliance APIOperational
  • SearchOperational
  • File uploadsOperational
  • Voice modeOperational
  • GPTsOperational
  • Image GenerationOperational
  • Deep ResearchOperational
  • AgentOperational

These are OpenAI's components, named and scored by OpenAI. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is OpenAI's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

OpenAI response time, by region

US-East
268msp95 · latest
500ms250ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 217ms2026-09-07 UTC: p95 216ms2026-09-08 UTC: p95 242ms2026-09-09 UTC: p95 237ms2026-09-10 UTC: p95 270ms2026-09-11 UTC: p95 249ms2026-09-12 UTC: p95 219ms2026-09-13 UTC: p95 344ms2026-09-14 UTC: p95 216ms2026-09-15 UTC: p95 279ms2026-09-16 UTC: p95 281ms2026-09-17 UTC: p95 281ms2026-09-18 UTC: p95 251ms2026-09-19 UTC: p95 232ms2026-09-20 UTC: p95 229ms2026-09-21 UTC: p95 254ms2026-09-22 UTC: p95 258ms2026-09-23 UTC: p95 279ms2026-09-24 UTC: p95 300ms2026-09-25 UTC: p95 259ms2026-09-26 UTC: p95 256ms2026-09-27 UTC: p95 242ms2026-09-28 UTC: p95 246ms2026-09-29 UTC: p95 326ms2026-09-30 UTC: p95 273ms2026-10-01 UTC: p95 280ms2026-10-02 UTC: p95 284ms2026-10-03 UTC: p95 297ms2026-10-04 UTC: p95 186ms2026-10-05 UTC: p95 268ms
Sep 6Sep 20Oct 5
US-West
215msp95 · latest
500ms250ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 170ms2026-09-07 UTC: p95 183ms2026-09-08 UTC: p95 262ms2026-09-09 UTC: p95 306ms2026-09-10 UTC: p95 221ms2026-09-11 UTC: p95 285ms2026-09-12 UTC: p95 143ms2026-09-13 UTC: p95 185ms2026-09-14 UTC: p95 153ms2026-09-15 UTC: p95 280ms2026-09-16 UTC: p95 259ms2026-09-17 UTC: p95 415ms2026-09-18 UTC: p95 200ms2026-09-19 UTC: p95 188ms2026-09-20 UTC: p95 187ms2026-09-21 UTC: p95 306ms2026-09-22 UTC: p95 235ms2026-09-23 UTC: p95 295ms2026-09-24 UTC: p95 252ms2026-09-25 UTC: p95 240ms2026-09-26 UTC: p95 228ms2026-09-27 UTC: p95 201ms2026-09-28 UTC: p95 228ms2026-09-29 UTC: p95 247ms2026-09-30 UTC: p95 266ms2026-10-01 UTC: p95 242ms2026-10-02 UTC: p95 227ms2026-10-03 UTC: p95 199ms2026-10-04 UTC: p95 202ms2026-10-05 UTC: p95 215ms
Sep 6Sep 20Oct 5
Europe
316msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 255ms2026-09-07 UTC: p95 251ms2026-09-08 UTC: p95 254ms2026-09-09 UTC: p95 338ms2026-09-10 UTC: p95 292ms2026-09-11 UTC: p95 326ms2026-09-12 UTC: p95 246ms2026-09-13 UTC: p95 268ms2026-09-14 UTC: p95 243ms2026-09-15 UTC: p95 254ms2026-09-16 UTC: p95 369ms2026-09-17 UTC: p95 244ms2026-09-18 UTC: p95 247ms2026-09-19 UTC: p95 232ms2026-09-20 UTC: p95 242ms2026-09-21 UTC: p95 285ms2026-09-22 UTC: p95 311ms2026-09-23 UTC: p95 382ms2026-09-24 UTC: p95 251ms2026-09-25 UTC: p95 260ms2026-09-26 UTC: p95 259ms2026-09-27 UTC: p95 258ms2026-09-28 UTC: p95 260ms2026-09-29 UTC: p95 264ms2026-09-30 UTC: p95 341ms2026-10-01 UTC: p95 305ms2026-10-02 UTC: p95 532ms2026-10-03 UTC: p95 266ms2026-10-04 UTC: p95 254ms2026-10-05 UTC: p95 316ms
Sep 6Sep 20Oct 5
Asia-Pacific
328msp95 · latest
500ms250ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 344ms2026-09-07 UTC: p95 301ms2026-09-08 UTC: p95 349ms2026-09-09 UTC: p95 335ms2026-09-10 UTC: p95 289ms2026-09-11 UTC: p95 379ms2026-09-12 UTC: p95 293ms2026-09-13 UTC: p95 352ms2026-09-14 UTC: p95 419ms2026-09-15 UTC: p95 342ms2026-09-16 UTC: p95 319ms2026-09-17 UTC: p95 345ms2026-09-18 UTC: p95 346ms2026-09-19 UTC: p95 393ms2026-09-20 UTC: p95 297ms2026-09-21 UTC: p95 319ms2026-09-22 UTC: p95 372ms2026-09-23 UTC: p95 375ms2026-09-24 UTC: p95 367ms2026-09-25 UTC: p95 372ms2026-09-26 UTC: p95 352ms2026-09-27 UTC: p95 329ms2026-09-28 UTC: p95 342ms2026-09-29 UTC: p95 327ms2026-09-30 UTC: p95 301ms2026-10-01 UTC: p95 318ms2026-10-02 UTC: p95 497ms2026-10-03 UTC: p95 337ms2026-10-04 UTC: p95 383ms2026-10-05 UTC: p95 328ms
Sep 6Sep 20Oct 5
US-Central
424msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 331ms2026-09-07 UTC: p95 356ms2026-09-08 UTC: p95 346ms2026-09-09 UTC: p95 351ms2026-09-10 UTC: p95 423ms2026-09-11 UTC: p95 571ms2026-09-12 UTC: p95 301ms2026-09-13 UTC: p95 366ms2026-09-14 UTC: p95 410ms2026-09-15 UTC: p95 488ms2026-09-16 UTC: p95 391ms2026-09-17 UTC: p95 444ms2026-09-18 UTC: p95 558ms2026-09-19 UTC: p95 818ms2026-09-20 UTC: p95 763ms2026-09-21 UTC: p95 817ms2026-09-22 UTC: p95 460ms2026-09-23 UTC: p95 513ms2026-09-24 UTC: p95 603ms2026-09-25 UTC: p95 304ms2026-09-26 UTC: p95 355ms2026-09-27 UTC: p95 321ms2026-09-28 UTC: p95 352ms2026-09-29 UTC: p95 473ms2026-09-30 UTC: p95 548ms2026-10-01 UTC: p95 436ms2026-10-02 UTC: p95 916ms2026-10-03 UTC: p95 494ms2026-10-04 UTC: p95 345ms2026-10-05 UTC: p95 424ms
Sep 6Sep 20Oct 5
Canada
319msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 391ms2026-09-07 UTC: p95 355ms2026-09-08 UTC: p95 401ms2026-09-09 UTC: p95 386ms2026-09-10 UTC: p95 436ms2026-09-11 UTC: p95 469ms2026-09-12 UTC: p95 378ms2026-09-13 UTC: p95 478ms2026-09-14 UTC: p95 369ms2026-09-15 UTC: p95 371ms2026-09-16 UTC: p95 639ms2026-09-17 UTC: p95 768ms2026-09-18 UTC: p95 852ms2026-09-19 UTC: p95 848ms2026-09-20 UTC: p95 698ms2026-09-21 UTC: p95 829ms2026-09-22 UTC: p95 710ms2026-09-23 UTC: p95 628ms2026-09-24 UTC: p95 506ms2026-09-25 UTC: p95 328ms2026-09-26 UTC: p95 381ms2026-09-27 UTC: p95 335ms2026-09-28 UTC: p95 389ms2026-09-29 UTC: p95 501ms2026-09-30 UTC: p95 602ms2026-10-01 UTC: p95 448ms2026-10-02 UTC: p95 480ms2026-10-03 UTC: p95 510ms2026-10-04 UTC: p95 326ms2026-10-05 UTC: p95 319ms
Sep 6Sep 20Oct 5
UK
387msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 410ms2026-09-07 UTC: p95 326ms2026-09-08 UTC: p95 362ms2026-09-09 UTC: p95 362ms2026-09-10 UTC: p95 354ms2026-09-11 UTC: p95 377ms2026-09-12 UTC: p95 339ms2026-09-13 UTC: p95 346ms2026-09-14 UTC: p95 347ms2026-09-15 UTC: p95 364ms2026-09-16 UTC: p95 476ms2026-09-17 UTC: p95 724ms2026-09-18 UTC: p95 730ms2026-09-19 UTC: p95 703ms2026-09-20 UTC: p95 375ms2026-09-21 UTC: p95 481ms2026-09-22 UTC: p95 443ms2026-09-23 UTC: p95 447ms2026-09-24 UTC: p95 342ms2026-09-25 UTC: p95 349ms2026-09-26 UTC: p95 616ms2026-09-27 UTC: p95 341ms2026-09-28 UTC: p95 339ms2026-09-29 UTC: p95 382ms2026-09-30 UTC: p95 405ms2026-10-01 UTC: p95 506ms2026-10-02 UTC: p95 339ms2026-10-03 UTC: p95 333ms2026-10-04 UTC: p95 324ms2026-10-05 UTC: p95 387ms
Sep 6Sep 20Oct 5
Southeast Asia
632msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 757ms2026-09-07 UTC: p95 570ms2026-09-08 UTC: p95 561ms2026-09-09 UTC: p95 627ms2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 765ms2026-09-12 UTC: p95 493ms2026-09-13 UTC: p95 562ms2026-09-14 UTC: p95 632ms2026-09-15 UTC: p95 666ms2026-09-16 UTC: p95 914ms2026-09-17 UTC: p95 863ms2026-09-18 UTC: p95 775ms2026-09-19 UTC: p95 602ms2026-09-20 UTC: p95 658ms2026-09-21 UTC: p95 913ms2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 724ms2026-09-26 UTC: p95 954ms2026-09-27 UTC: p95 540ms2026-09-28 UTC: p95 638ms2026-09-29 UTC: p95 765ms2026-09-30 UTC: p95 666ms2026-10-01 UTC: p95 674ms2026-10-02 UTC: p95 679ms2026-10-03 UTC: p95 502ms2026-10-04 UTC: p95 566ms2026-10-05 UTC: p95 632ms
Sep 6Sep 20Oct 5
Australia
706msp95 · latest
1s500ms0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 726ms2026-09-07 UTC: p95 728ms2026-09-08 UTC: p95 697ms2026-09-09 UTC: p95 645ms2026-09-10 UTC: p95 736ms2026-09-11 UTC: p95 650ms2026-09-12 UTC: p95 925ms2026-09-13 UTC: p95 729ms2026-09-14 UTC: p95 705ms2026-09-15 UTC: p95 684ms2026-09-16 UTC: p95 715ms2026-09-17 UTC: p95 725ms2026-09-18 UTC: p95 691ms2026-09-19 UTC: p95 733ms2026-09-20 UTC: p95 702ms2026-09-21 UTC: p95 992ms2026-09-22 UTC: p95 869ms2026-09-23 UTC: p95 809ms2026-09-24 UTC: p95 961ms2026-09-25 UTC: p95 692ms2026-09-26 UTC: p95 774ms2026-09-27 UTC: p95 761ms2026-09-28 UTC: p95 757ms2026-09-29 UTC: p95 717ms2026-09-30 UTC: p95 736ms2026-10-01 UTC: p95 594ms2026-10-02 UTC: p95 703ms2026-10-03 UTC: p95 859ms2026-10-04 UTC: p95 697ms2026-10-05 UTC: p95 706ms
Sep 6Sep 20Oct 5
South America
617msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 597ms2026-09-07 UTC: p95 685ms2026-09-08 UTC: p95 813ms2026-09-09 UTC: p95 780ms2026-09-10 UTC: p95 731ms2026-09-11 UTC: p95 752ms2026-09-12 UTC: p95 674ms2026-09-13 UTC: p95 674ms2026-09-14 UTC: p95 697ms2026-09-15 UTC: p95 674ms2026-09-16 UTC: p95 973ms2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 876ms2026-09-19 UTC: p95 728ms2026-09-20 UTC: p95 715ms2026-09-21 UTC: p95 833ms2026-09-22 UTC: p95 815ms2026-09-23 UTC: p95 743ms2026-09-24 UTC: p95 877ms2026-09-25 UTC: p95 649ms2026-09-26 UTC: p95 664ms2026-09-27 UTC: p95 809ms2026-09-28 UTC: p95 612ms2026-09-29 UTC: p95 765ms2026-09-30 UTC: p95 755ms2026-10-01 UTC: p95 707ms2026-10-02 UTC: p95 784ms2026-10-03 UTC: p95 939ms2026-10-04 UTC: p95 710ms2026-10-05 UTC: p95 617ms
Sep 6Sep 20Oct 5

Is it OpenAI, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not OpenAI -- it cannot diagnose OpenAI's own systems.

What we measured, function by function

OpenAI answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the auth row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see OpenAI go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching OpenAI, and again when they can reach it again. That is our own measurement from ten regions, not OpenAI's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 134msstatus code: 401checked: Oct 5, 2026, 8:15 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach OpenAI normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 113msstatus code: 401checked: Oct 5, 2026, 8:16 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach OpenAI normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 118msstatus code: 401checked: Oct 5, 2026, 8:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach OpenAI normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 124msstatus code: 401checked: Oct 5, 2026, 8:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach OpenAI normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 430msstatus code: 401checked: Oct 5, 2026, 8:13 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach OpenAI normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 256msstatus code: 401checked: Oct 5, 2026, 8:15 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach OpenAI normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 462msstatus code: 401checked: Oct 5, 2026, 8:15 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach OpenAI normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 210msstatus code: 401checked: Oct 5, 2026, 8:16 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach OpenAI normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 239msstatus code: 401checked: Oct 5, 2026, 8:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach OpenAI normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 575msstatus code: 401checked: Oct 5, 2026, 8:15 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach OpenAI normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using OpenAI, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for OpenAI yet, which is not evidence that nothing is wrong.

Recent outages

Elevated error rates in Codex Clouddeclared on their status page2026-10-05
Elevated errors in ChatGPT conversationsdeclared on their status page2026-10-05
Admin Console Intermittently Inaccessibledeclared on their status page2026-10-05
Issues saving and editing Pages, 20mdeclared on their status page2026-10-05
Elevated Work Mode errorsdeclared on their status page2026-10-05
Issues with data analysis and file creation in ChatGPT, 48mdeclared on their status page2026-10-02
Issues with login, signup, and ads, 53mdeclared on their status page2026-10-01
Elevated latency for some API requests, 3h 30mdeclared on their status page2026-09-30

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring OpenAI since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for OpenAI covering any window you pick, with our measurements and OpenAI's own claim at the time, side by side.

Full availability history for OpenAI: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

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 servers

Put this badge in your README

OpenAI uptime measured by RealUptimeLive, from this page's own readings.
[![OpenAI uptime measured by RealUptime](https://realuptime.io/outages/openai/badge.svg?days=30)](https://realuptime.io/outages/openai)
<a href="https://realuptime.io/outages/openai"><img src="https://realuptime.io/outages/openai/badge.svg?days=30" alt="OpenAI uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What OpenAI's SLA implies, from our measurement

At or above your target

We measured none of downtime for OpenAI over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from OpenAI's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

Per-model status

No vendor publishes per-model status, so this is the closest thing available: a real, credentialed completion call to each model below, on our own schedule. A rejected credential of ours never renders as a OpenAI outage here -- see “Awaiting data” below.
gpt-5-nanoOperational
Europe · 714ms · last verified completion Oct 5, 2026, 8:15 PM UTC
gpt-5-nanoOperational
South America · 870ms · last verified completion Oct 5, 2026, 8:13 PM UTC
gpt-5-nanoOperational
US-East · 848ms · last verified completion Oct 5, 2026, 8:15 PM UTC
gpt-5-nanoOperational
UK · 969ms · last verified completion Oct 5, 2026, 8:15 PM UTC
gpt-5-nanoOperational
Asia-Pacific · 926ms · last verified completion Oct 5, 2026, 8:16 PM UTC
gpt-5-nanoOperational
US-Central · 795ms · last verified completion Oct 5, 2026, 8:13 PM UTC
gpt-5-nanoOperational
Southeast Asia · 921ms · last verified completion Oct 5, 2026, 8:13 PM UTC
gpt-5-nanoOperational
US-West · 621ms · last verified completion Oct 5, 2026, 8:16 PM UTC
gpt-5-nanoOperational
Australia · 1037ms · last verified completion Oct 5, 2026, 8:15 PM UTC
gpt-5-nanoOperational
Canada · 905ms · last verified completion Oct 5, 2026, 8:14 PM UTC
gpt-5.6Operational
Europe · 1327ms · last verified completion Oct 5, 2026, 8:15 PM UTC
gpt-5.6Operational
South America · 1032ms · last verified completion Oct 5, 2026, 8:13 PM UTC
gpt-5.6Operational
US-East · 894ms · last verified completion Oct 5, 2026, 8:15 PM UTC
gpt-5.6Operational
UK · 1204ms · last verified completion Oct 5, 2026, 8:15 PM UTC
gpt-5.6Operational
Asia-Pacific · 942ms · last verified completion Oct 5, 2026, 8:16 PM UTC
gpt-5.6Operational
US-Central · 665ms · last verified completion Oct 5, 2026, 8:13 PM UTC
gpt-5.6Operational
Southeast Asia · 1049ms · last verified completion Oct 5, 2026, 8:13 PM UTC
gpt-5.6Operational
US-West · 1136ms · last verified completion Oct 5, 2026, 8:16 PM UTC
gpt-5.6Operational
Australia · 1208ms · last verified completion Oct 5, 2026, 8:15 PM UTC
gpt-5.6Operational
Canada · 1678ms · last verified completion Oct 5, 2026, 8:14 PM UTC

What we check

primaryfunctional: auth surface
https://api.openai.com/v1/models
secondary
https://status.openai.com/
secondaryfunctional: live API
https://api.openai.com/v1/chat/completions
secondaryfunctional: live API
https://api.openai.com/v1/chat/completions?rea427_model=flagship
secondaryfunctional: auth surface
https://auth.openai.com/.well-known/openid-configuration
RealUptime is not affiliated with OpenAI; the name identifies what we measured, and nothing here speaks for OpenAI's own team. We send a single web request to OpenAI from 10 regions on our own schedule and time the response. We do not see inside OpenAI's systems, do not use an account or real transaction, and are not the same signal OpenAI's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for OpenAI is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.