Skip to content

Outage tracker / OpenAI

Is OpenAI down?

I'm having a problem

Vendor reports no incidentWhat OpenAI reports

OpenAI reports no incident on its status page.

As of the last successful poll, 2026-10-14 04:59 UTC.

OpenAI's status page

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 passingchecked moments ago

Our checks of OpenAI pass from all 10 regions we check.

As of Oct 14, 2026, 5:05 AM UTC, RealUptime's checks of OpenAI passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 14, 2026, 5:05 AM UTC
US-East184 msChecks passing
US-West357 msChecks passing
Europe231 msChecks passing
Asia-Pacific218 msChecks passing
US-Central108 msChecks passing
Canada306 msChecks passing
UK211 msChecks passing
Southeast Asia493 msChecks passing
Australia819 msChecks passing
South America184 msChecks passing
their status pagetheir claim, not our reading

OpenAI reports: All systems operational (“All Systems Operational”)

from OpenAI's own status page, checked Oct 14, 2026, 4:49 AM UTC
OpenAI's own status page shows no incident, and our checks of OpenAI pass right now.

OpenAI's own component breakdown, as they publish it

  • Chat CompletionsOperational
  • ResponsesOperational
  • AgentsOperational
  • DecisionsOperational
  • Fine-tuningOperational
  • EmbeddingsOperational
  • ImagesOperational
  • BatchOperational
  • AudioOperational
  • ModerationsOperational
  • RealtimeOperational
  • FilesOperational
  • LoginOperational
  • ConversationsOperational
  • LoginOperational
  • ChatGPT WorkOperational
  • Codex in ChatGPT DesktopOperational
  • 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
347msp95 · 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-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 267ms2026-10-06 UTC: p95 248ms2026-10-07 UTC: p95 294ms2026-10-08 UTC: p95 313ms2026-10-09 UTC: p95 329ms2026-10-10 UTC: p95 262ms2026-10-11 UTC: p95 251ms2026-10-12 UTC: p95 270ms2026-10-13 UTC: p95 284ms2026-10-14 UTC: p95 347ms
Sep 15Sep 29Oct 14
US-West
266msp95 · 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-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 234ms2026-10-06 UTC: p95 234ms2026-10-07 UTC: p95 253ms2026-10-08 UTC: p95 243ms2026-10-09 UTC: p95 220ms2026-10-10 UTC: p95 305ms2026-10-11 UTC: p95 280ms2026-10-12 UTC: p95 286ms2026-10-13 UTC: p95 290ms2026-10-14 UTC: p95 266ms
Sep 15Sep 29Oct 14
Europe
257msp95 · 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-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 311ms2026-10-06 UTC: p95 287ms2026-10-07 UTC: p95 330ms2026-10-08 UTC: p95 376ms2026-10-09 UTC: p95 370ms2026-10-10 UTC: p95 326ms2026-10-11 UTC: p95 277ms2026-10-12 UTC: p95 342ms2026-10-13 UTC: p95 282ms2026-10-14 UTC: p95 257ms
Sep 15Sep 29Oct 14
Asia-Pacific
349msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-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 327ms2026-10-06 UTC: p95 340ms2026-10-07 UTC: p95 400ms2026-10-08 UTC: p95 550ms2026-10-09 UTC: p95 438ms2026-10-10 UTC: p95 339ms2026-10-11 UTC: p95 323ms2026-10-12 UTC: p95 360ms2026-10-13 UTC: p95 393ms2026-10-14 UTC: p95 349ms
Sep 15Sep 29Oct 14
US-Central
391msp95 · 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-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 416ms2026-10-06 UTC: p95 316ms2026-10-07 UTC: p95 536ms2026-10-08 UTC: p95 306ms2026-10-09 UTC: p95 411ms2026-10-10 UTC: p95 323ms2026-10-11 UTC: p95 343ms2026-10-12 UTC: p95 330ms2026-10-13 UTC: p95 459ms2026-10-14 UTC: p95 391ms
Sep 15Sep 29Oct 14
Canada
366msp95 · 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-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 308ms2026-10-06 UTC: p95 468ms2026-10-07 UTC: p95 564ms2026-10-08 UTC: p95 318ms2026-10-09 UTC: p95 475ms2026-10-10 UTC: p95 452ms2026-10-11 UTC: p95 348ms2026-10-12 UTC: p95 399ms2026-10-13 UTC: p95 476ms2026-10-14 UTC: p95 366ms
Sep 15Sep 29Oct 14
UK
450msp95 · 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-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 421ms2026-10-06 UTC: p95 405ms2026-10-07 UTC: p95 344ms2026-10-08 UTC: p95 453ms2026-10-09 UTC: p95 382ms2026-10-10 UTC: p95 364ms2026-10-11 UTC: p95 346ms2026-10-12 UTC: p95 427ms2026-10-13 UTC: p95 420ms2026-10-14 UTC: p95 450ms
Sep 15Sep 29Oct 14
Southeast Asia
978msp95 · 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-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 619ms2026-10-06 UTC: p95 627ms2026-10-07 UTC: p95 558ms2026-10-08 UTC: p95 678ms2026-10-09 UTC: p95 998ms2026-10-10 UTC: p95 797ms2026-10-11 UTC: p95 575ms2026-10-12 UTC: p95 684ms2026-10-13 UTC: p95 770ms2026-10-14 UTC: p95 978ms
Sep 15Sep 29Oct 14
Australia
864msp95 · 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-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 685ms2026-10-06 UTC: p95 654ms2026-10-07 UTC: p95 648ms2026-10-08 UTC: p95 704ms2026-10-09 UTC: p95 702ms2026-10-10 UTC: p95 729ms2026-10-11 UTC: p95 744ms2026-10-12 UTC: p95 719ms2026-10-13 UTC: p95 888ms2026-10-14 UTC: p95 864ms
Sep 15Sep 29Oct 14
South America
712msp95 · 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-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 608ms2026-10-06 UTC: p95 660ms2026-10-07 UTC: p95 734ms2026-10-08 UTC: p95 686ms2026-10-09 UTC: p95 659ms2026-10-10 UTC: p95 658ms2026-10-11 UTC: p95 817ms2026-10-12 UTC: p95 714ms2026-10-13 UTC: p95 943ms2026-10-14 UTC: p95 712ms
Sep 15Sep 29Oct 14

Check your own site while you wait on OpenAI

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • AuthprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when OpenAI reports an incident on its status page, and again when it reports it resolved.

Get an email when OpenAI reports an incident

Email me when OpenAI reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is OpenAI's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 184msstatus code: 401checked: Oct 14, 2026, 5:04 AM 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
      Checks passinglatency: 357msstatus code: 401checked: Oct 14, 2026, 5:05 AM 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
      Checks passinglatency: 108msstatus code: 401checked: Oct 14, 2026, 5:04 AM 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
      Checks passinglatency: 306msstatus code: 401checked: Oct 14, 2026, 5:02 AM 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
    Checks passinglatency: 184msstatus code: 401checked: Oct 14, 2026, 5:04 AM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 231msstatus code: 401checked: Oct 14, 2026, 5:04 AM 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
      Checks passinglatency: 211msstatus code: 401checked: Oct 14, 2026, 5:03 AM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 218msstatus code: 401checked: Oct 14, 2026, 5:05 AM 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
      Checks passinglatency: 493msstatus code: 401checked: Oct 14, 2026, 5:03 AM 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
      Checks passinglatency: 819msstatus code: 401checked: Oct 14, 2026, 5:02 AM 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 probe events

Degraded performance in GPT-6.1 Sol Codex and Work mode, 8h 27mdeclared on their status page2026-10-13
Workspace admins may be unable to manage plugins, 1h 38mdeclared on their status page2026-10-09
Some ChatGPT content may be unavailable on Android, 3h 26mdeclared on their status page2026-10-09
Delayed Costs data in the Compliance API, 70h 39mdeclared on their status page2026-10-09
Some APAC users are seeing errors in ChatGPT Work, conversations, and GPTs., 1h 34mdeclared on their status page2026-10-08
Elevated errors with GPT-5.6 Instant in FedRAMP workspaces, 21mdeclared on their status page2026-10-07
Degraded performance in Codex and Work mode: Dot turn failures, delayed responses, and reduced proactivity, 1h 2mdeclared on their status page2026-10-07
Dot in Codex may fail to create new threads, 1h 35mdeclared on their status page2026-10-07

check 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 check readings and OpenAI's own claim at the time, side by side.

Full check history for OpenAI: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 by RealUptime's checksLive, from this page's own readings.
[![OpenAI uptime by RealUptime's checks](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 by RealUptime's checks"></a>

The badge shows the share of our checks that passed 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is OpenAI down?", https://realuptime.io/outages/openai. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

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 OpenAI failing here. See “Awaiting data” below.
gpt-5-nanoChecks passing
Europe · 878ms · last completed call Oct 14, 2026, 5:04 AM UTC
gpt-5-nanoChecks passing
South America · 810ms · last completed call Oct 14, 2026, 5:04 AM UTC
gpt-5-nanoChecks passing
US-East · 965ms · last completed call Oct 14, 2026, 5:04 AM UTC
gpt-5-nanoChecks passing
UK · 818ms · last completed call Oct 14, 2026, 5:03 AM UTC
gpt-5-nanoChecks passing
Asia-Pacific · 963ms · last completed call Oct 14, 2026, 5:05 AM UTC
gpt-5-nanoChecks passing
US-Central · 809ms · last completed call Oct 14, 2026, 5:04 AM UTC
gpt-5-nanoChecks passing
Southeast Asia · 1038ms · last completed call Oct 14, 2026, 5:03 AM UTC
gpt-5-nanoChecks passing
US-West · 952ms · last completed call Oct 14, 2026, 5:05 AM UTC
gpt-5-nanoChecks passing
Australia · 1462ms · last completed call Oct 14, 2026, 5:02 AM UTC
gpt-5-nanoChecks passing
Canada · 929ms · last completed call Oct 14, 2026, 5:02 AM UTC
gpt-5.6Checks passing
Europe · 990ms · last completed call Oct 14, 2026, 5:04 AM UTC
gpt-5.6Checks passing
South America · 1693ms · last completed call Oct 14, 2026, 5:04 AM UTC
gpt-5.6Checks passing
US-East · 1108ms · last completed call Oct 14, 2026, 5:04 AM UTC
gpt-5.6Checks passing
UK · 1085ms · last completed call Oct 14, 2026, 5:03 AM UTC
gpt-5.6Checks passing
Asia-Pacific · 759ms · last completed call Oct 14, 2026, 5:05 AM UTC
gpt-5.6Checks passing
US-Central · 1236ms · last completed call Oct 14, 2026, 5:04 AM UTC
gpt-5.6Checks passing
Southeast Asia · 1402ms · last completed call Oct 14, 2026, 5:03 AM UTC
gpt-5.6Checks passing
US-West · 905ms · last completed call Oct 14, 2026, 5:05 AM UTC
gpt-5.6Checks passing
Australia · 1039ms · last completed call Oct 14, 2026, 5:02 AM UTC
gpt-5.6Checks passing
Canada · 1198ms · last completed call Oct 14, 2026, 5:02 AM 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

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.openai.com

RealUptime is not affiliated with OpenAI; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.