Skip to content

Outage tracker / OpenAI

Is OpenAI down?

I'm having a problem

Vendor reports an incidentWhat OpenAI reports

OpenAI reports an incident on its status page: New Ad Accounts failing to provision admins.

Impact: minor. Since 2026-10-22 19:36 UTC.

Latest update, 2026-10-22 19:36 UTC: We have identified that new ad accounts are failing to assign their creator admin. We are investigating the issue.

One more incident is open on its status page.

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 22, 2026, 8:05 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 Oct 22, 2026, 8:05 PM UTC
US-East469 msChecks passing
US-West297 msChecks passing
Europe351 msChecks passing
Asia-Pacific521 msChecks passing
US-Central379 msChecks passing
Canada895 msChecks passing
UK948 msChecks passing
Southeast Asia689 msChecks passing
Australia1395 msChecks passing
South America511 msChecks passing
their status pagetheir claim, not our reading

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

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

OpenAI reports an active incident: New Ad Accounts failing to provision admins (minor incident, since Oct 22, 2026, 7:36 PM UTC)

OpenAI's status page reports Partial System Degradation. Our checks of OpenAI currently pass with normal latency. Our checks currently pass 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 the vendor's report and our check reading side by side. A check can miss problems that users see. 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
  • 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
669msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-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 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 669ms
Sep 23Oct 7Oct 22
US-West
885msp95 · 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-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 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 885ms
Sep 23Oct 7Oct 22
Europe
874msp95 · 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-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 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 874ms
Sep 23Oct 7Oct 22
Asia-Pacific
1.0sp95 · 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-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 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.0s
Sep 23Oct 7Oct 22
US-Central
1.1sp95 · 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-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 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.1s
Sep 23Oct 7Oct 22
Canada
1.1sp95 · 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-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 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.1s
Sep 23Oct 7Oct 22
UK
932msp95 · 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-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 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 932ms
Sep 23Oct 7Oct 22
Southeast Asia
1.6sp95 · 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-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 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.6s
Sep 23Oct 7Oct 22
Australia
2.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-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 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.4s
Sep 23Oct 7Oct 22
South America
2.2sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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 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.2s
Sep 23Oct 7Oct 22

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: 469msstatus code: 401checked: Oct 22, 2026, 8:04 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: 297msstatus code: 401checked: Oct 22, 2026, 8:05 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: 379msstatus code: 401checked: Oct 22, 2026, 8:03 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: 895msstatus code: 401checked: Oct 22, 2026, 8:03 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: 511msstatus code: 401checked: Oct 22, 2026, 8:03 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: 351msstatus code: 401checked: Oct 22, 2026, 8:05 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: 948msstatus code: 401checked: Oct 22, 2026, 8:03 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: 521msstatus code: 401checked: Oct 22, 2026, 8:04 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: 689msstatus code: 401checked: Oct 22, 2026, 8:03 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: 1395msstatus code: 401checked: Oct 22, 2026, 8:03 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

New Ad Accounts failing to provision adminsdeclared on their status page2026-10-22
Degraded Performance of Dots on Enterprisedeclared on their status page2026-10-22
Elevated ChatGPT conversation and Responses API errors, 6h 32mdeclared on their status page2026-10-22
Elevated error rates for gpt-5.6-luna API requests, 1h 9mdeclared on their status page2026-10-21
Elevated FedRAMP API error rates for Astra and Sol, 5h 17mdeclared on their status page2026-10-21
Degraded performance in ChatGPT, Codex, and APIs, 1h 2mdeclared on their status page2026-10-21
Authentication errors for some users, 1hdeclared on their status page2026-10-20
File Download errors, 42mdeclared on their status page2026-10-19

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

The badge shows the share of our checks that passed over the last 30 days. 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 · 1285ms · last completed call Oct 22, 2026, 8:05 PM UTC
gpt-5-nanoChecks passing
South America · 1714ms · last completed call Oct 22, 2026, 8:03 PM UTC
gpt-5-nanoChecks passing
US-East · 1456ms · last completed call Oct 22, 2026, 8:04 PM UTC
gpt-5-nanoChecks passing
UK · 1607ms · last completed call Oct 22, 2026, 8:03 PM UTC
gpt-5-nanoChecks passing
Asia-Pacific · 2245ms · last completed call Oct 22, 2026, 8:04 PM UTC
gpt-5-nanoChecks passing
US-Central · 1420ms · last completed call Oct 22, 2026, 8:03 PM UTC
gpt-5-nanoChecks passing
Southeast Asia · 1695ms · last completed call Oct 22, 2026, 8:03 PM UTC
gpt-5-nanoChecks passing
US-West · 929ms · last completed call Oct 22, 2026, 8:05 PM UTC
gpt-5-nanoChecks passing
Australia · 2111ms · last completed call Oct 22, 2026, 8:03 PM UTC
gpt-5-nanoChecks passing
Canada · 1987ms · last completed call Oct 22, 2026, 8:03 PM UTC
gpt-5.6Checks passing
Europe · 1259ms · last completed call Oct 22, 2026, 8:05 PM UTC
gpt-5.6Checks passing
South America · 1384ms · last completed call Oct 22, 2026, 8:03 PM UTC
gpt-5.6Checks passing
US-East · 1353ms · last completed call Oct 22, 2026, 8:04 PM UTC
gpt-5.6Checks passing
UK · 1689ms · last completed call Oct 22, 2026, 8:03 PM UTC
gpt-5.6Checks passing
Asia-Pacific · 1370ms · last completed call Oct 22, 2026, 8:04 PM UTC
gpt-5.6Checks passing
US-Central · 1318ms · last completed call Oct 22, 2026, 8:03 PM UTC
gpt-5.6Checks passing
Southeast Asia · 1382ms · last completed call Oct 22, 2026, 8:03 PM UTC
gpt-5.6Checks passing
US-West · 1021ms · last completed call Oct 22, 2026, 8:05 PM UTC
gpt-5.6Checks passing
Australia · 1818ms · last completed call Oct 22, 2026, 8:03 PM UTC
gpt-5.6Checks passing
Canada · 1528ms · last completed call Oct 22, 2026, 8:03 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

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.