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-11-05 14:14 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 1 minute ago

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

As of Nov 5, 2026, 2:33 PM 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 Nov 5, 2026, 2:33 PM UTC
US-East1188 msChecks passing
US-West397 msChecks passing
Europe435 msChecks passing
Asia-Pacific472 msChecks passing
US-Central489 msChecks passing
Canada426 msChecks passing
UK383 msChecks passing
Southeast Asia429 msChecks passing
Australia769 msChecks passing
South America233 msChecks passing
their status pagetheir claim, not our reading

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

from OpenAI's own status page, checked Nov 5, 2026, 1:08 PM 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
  • LiveOperational
  • ConversationsOperational
  • LoginOperational
  • ChatGPT WorkOperational
  • Codex in ChatGPT DesktopOperational
  • Compliance APIOperational
  • SearchOperational
  • File uploadsOperational
  • Voice modeOperational
  • GPTsOperational
  • Image GenerationOperational
  • Deep ResearchOperational

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
695msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 306ms2026-10-15 UTC: p95 275ms2026-10-16 UTC: p95 246ms2026-10-17 UTC: p95 525ms2026-10-18 UTC: p95 642ms2026-10-19 UTC: p95 705ms2026-10-20 UTC: p95 783ms2026-10-21 UTC: p95 728ms2026-10-22 UTC: p95 669ms2026-10-23 UTC: p95 673ms2026-10-24 UTC: p95 879ms2026-10-25 UTC: p95 834ms2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 682ms2026-10-28 UTC: p95 719ms2026-10-29 UTC: p95 691ms2026-10-30 UTC: p95 813ms2026-10-31 UTC: p95 780ms2026-11-01 UTC: p95 636ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 804ms2026-11-05 UTC: p95 695ms
Oct 7Oct 21Nov 5
US-West
620msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-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 414ms2026-10-15 UTC: p95 404ms2026-10-16 UTC: p95 325ms2026-10-17 UTC: p95 476ms2026-10-18 UTC: p95 633ms2026-10-19 UTC: p95 801ms2026-10-20 UTC: p95 659ms2026-10-21 UTC: p95 785ms2026-10-22 UTC: p95 869ms2026-10-23 UTC: p95 795ms2026-10-24 UTC: p95 682ms2026-10-25 UTC: p95 735ms2026-10-26 UTC: p95 865ms2026-10-27 UTC: p95 916ms2026-10-28 UTC: p95 803ms2026-10-29 UTC: p95 772ms2026-10-30 UTC: p95 783ms2026-10-31 UTC: p95 664ms2026-11-01 UTC: p95 668ms2026-11-02 UTC: p95 691ms2026-11-03 UTC: p95 732ms2026-11-04 UTC: p95 559ms2026-11-05 UTC: p95 620ms
Oct 7Oct 21Nov 5
Europe
538msp95 · 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-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 310ms2026-10-15 UTC: p95 318ms2026-10-16 UTC: p95 312ms2026-10-17 UTC: p95 417ms2026-10-18 UTC: p95 509ms2026-10-19 UTC: p95 569ms2026-10-20 UTC: p95 684ms2026-10-21 UTC: p95 851ms2026-10-22 UTC: p95 906ms2026-10-23 UTC: p95 443ms2026-10-24 UTC: p95 491ms2026-10-25 UTC: p95 647ms2026-10-26 UTC: p95 569ms2026-10-27 UTC: p95 618ms2026-10-28 UTC: p95 514ms2026-10-29 UTC: p95 547ms2026-10-30 UTC: p95 614ms2026-10-31 UTC: p95 489ms2026-11-01 UTC: p95 459ms2026-11-02 UTC: p95 549ms2026-11-03 UTC: p95 539ms2026-11-04 UTC: p95 521ms2026-11-05 UTC: p95 538ms
Oct 7Oct 21Nov 5
Asia-Pacific
881msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 445ms2026-10-15 UTC: p95 425ms2026-10-16 UTC: p95 410ms2026-10-17 UTC: p95 602ms2026-10-18 UTC: p95 771ms2026-10-19 UTC: p95 869ms2026-10-20 UTC: p95 782ms2026-10-21 UTC: p95 887ms2026-10-22 UTC: p95 1.0s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 965ms2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 892ms2026-10-29 UTC: p95 923ms2026-10-30 UTC: p95 951ms2026-10-31 UTC: p95 936ms2026-11-01 UTC: p95 958ms2026-11-02 UTC: p95 1.0s2026-11-03 UTC: p95 1.0s2026-11-04 UTC: p95 961ms2026-11-05 UTC: p95 881ms
Oct 7Oct 21Nov 5
US-Central
897msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 435ms2026-10-15 UTC: p95 411ms2026-10-16 UTC: p95 446ms2026-10-17 UTC: p95 647ms2026-10-18 UTC: p95 750ms2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 983ms2026-10-26 UTC: p95 1.0s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 655ms2026-11-02 UTC: p95 923ms2026-11-03 UTC: p95 936ms2026-11-04 UTC: p95 736ms2026-11-05 UTC: p95 897ms
Oct 7Oct 21Nov 5
Canada
795msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 438ms2026-10-15 UTC: p95 443ms2026-10-16 UTC: p95 470ms2026-10-17 UTC: p95 992ms2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 987ms2026-10-30 UTC: p95 948ms2026-10-31 UTC: p95 993ms2026-11-01 UTC: p95 769ms2026-11-02 UTC: p95 863ms2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 812ms2026-11-05 UTC: p95 795ms
Oct 7Oct 21Nov 5
UK
697msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 417ms2026-10-15 UTC: p95 399ms2026-10-16 UTC: p95 387ms2026-10-17 UTC: p95 435ms2026-10-18 UTC: p95 568ms2026-10-19 UTC: p95 609ms2026-10-20 UTC: p95 811ms2026-10-21 UTC: p95 805ms2026-10-22 UTC: p95 989ms2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 655ms2026-10-25 UTC: p95 753ms2026-10-26 UTC: p95 822ms2026-10-27 UTC: p95 735ms2026-10-28 UTC: p95 1.0s2026-10-29 UTC: p95 818ms2026-10-30 UTC: p95 799ms2026-10-31 UTC: p95 709ms2026-11-01 UTC: p95 585ms2026-11-02 UTC: p95 548ms2026-11-03 UTC: p95 471ms2026-11-04 UTC: p95 548ms2026-11-05 UTC: p95 697ms
Oct 7Oct 21Nov 5
Southeast Asia
1.4sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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 843ms2026-10-15 UTC: p95 628ms2026-10-16 UTC: p95 760ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.7s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Australia
1.4sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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 679ms2026-10-15 UTC: p95 745ms2026-10-16 UTC: p95 716ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 2.2s2026-10-24 UTC: p95 2.2s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 2.3s2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 995ms2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
South America
1.4sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-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 811ms2026-10-15 UTC: p95 626ms2026-10-16 UTC: p95 812ms2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 8.3s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 2.0s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 2.1s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5

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
  • RealtimeUS-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: 1188msstatus code: 401checked: Nov 5, 2026, 2:32 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
      Checks passinglatency: 397msstatus code: 401checked: Nov 5, 2026, 2:32 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
      Checks passinglatency: 489msstatus code: 401checked: Nov 5, 2026, 2:33 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
      Checks passinglatency: 426msstatus code: 401checked: Nov 5, 2026, 2:30 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
    Checks passinglatency: 233msstatus code: 401checked: Nov 5, 2026, 2:29 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 435msstatus code: 401checked: Nov 5, 2026, 2:33 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
      Checks passinglatency: 383msstatus code: 401checked: Nov 5, 2026, 2:30 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 472msstatus code: 401checked: Nov 5, 2026, 2:32 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
      Checks passinglatency: 429msstatus code: 401checked: Nov 5, 2026, 2:29 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
      Checks passinglatency: 769msstatus code: 401checked: Nov 5, 2026, 2:30 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 probe events

Elevated error rates across paid ChatGPT plans, 1h 54mdeclared on their status page2026-11-04
File upload errors in ChatGPT, 4h 53mdeclared on their status page2026-11-03
Elevated errors with search in Dots, ChatGPT Work, and certain ChatGPT thinking experiences, 1h 35mdeclared on their status page2026-10-30
Elevated errors for GPT Image 2 API image edits, 4h 1mdeclared on their status page2026-10-30
Degraded Performace on ChatGPT Workdeclared on their status page2026-10-28
6.1 Sol Degraded Model Performance, 1h 18mdeclared on their status page2026-10-27
Elevated error rates for most hosted Code Reviews and Security Reviews on private GitHub repositories, 29mdeclared on their status page2026-10-27
Elevated error rates for Ads POST requests, 11mdeclared on their status page2026-10-26

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

Run 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

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" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

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.

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 · 1293ms · last completed call Nov 5, 2026, 2:33 PM UTC
gpt-5-nanoChecks passing
South America · 1456ms · last completed call Nov 5, 2026, 2:29 PM UTC
gpt-5-nanoChecks passing
US-East · 1697ms · last completed call Nov 5, 2026, 2:32 PM UTC
gpt-5-nanoChecks passing
UK · 825ms · last completed call Nov 5, 2026, 2:30 PM UTC
gpt-5-nanoChecks passing
Asia-Pacific · 1003ms · last completed call Nov 5, 2026, 2:32 PM UTC
gpt-5-nanoChecks passing
US-Central · 1006ms · last completed call Nov 5, 2026, 2:33 PM UTC
gpt-5-nanoChecks passing
Southeast Asia · 1184ms · last completed call Nov 5, 2026, 2:29 PM UTC
gpt-5-nanoChecks passing
US-West · 1387ms · last completed call Nov 5, 2026, 2:32 PM UTC
gpt-5-nanoChecks passing
Australia · 1734ms · last completed call Nov 5, 2026, 2:30 PM UTC
gpt-5-nanoChecks passing
Canada · 1529ms · last completed call Nov 5, 2026, 2:30 PM UTC
gpt-5.6Checks passing
Europe · 1433ms · last completed call Nov 5, 2026, 2:33 PM UTC
gpt-5.6Checks passing
South America · 1439ms · last completed call Nov 5, 2026, 2:29 PM UTC
gpt-5.6Checks passing
US-East · 1423ms · last completed call Nov 5, 2026, 2:32 PM UTC
gpt-5.6Checks passing
UK · 965ms · last completed call Nov 5, 2026, 2:30 PM UTC
gpt-5.6Checks passing
Asia-Pacific · 1007ms · last completed call Nov 5, 2026, 2:32 PM UTC
gpt-5.6Checks passing
US-Central · 1567ms · last completed call Nov 5, 2026, 2:33 PM UTC
gpt-5.6Checks passing
Southeast Asia · 1330ms · last completed call Nov 5, 2026, 2:29 PM UTC
gpt-5.6Checks passing
US-West · 1433ms · last completed call Nov 5, 2026, 2:32 PM UTC
gpt-5.6Checks passing
Australia · 1530ms · last completed call Nov 5, 2026, 2:30 PM UTC
gpt-5.6Checks passing
Canada · 1272ms · last completed call Nov 5, 2026, 2:30 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
secondary
wss://api.openai.com/v1/realtime?model=gpt-realtime

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.