Space for ads
Checked every 5 minutes · How we measure this
As of 03:00 EDT on 8 Oct 2026, chatgpt.com responded to our check in 128 ms, with 100.00% availability over the last 24 hours.
Checked every 5 minutes · last checked 9 minutes ago
The line is response time measured from our probe to chatgpt.com, which rises when the service slows down. Shaded red marks intervals where checks actually failed. It excludes your own connection and browser rendering.
Reported by ChatGPT on its own status page. Verify on their status page.
0 problem reports
ChatGPT degraded performance
DownBits detected degraded performance on ChatGPT between 8 Oct 2026, 08:55 – 10:30 IST, lasting ongoing. Detected across 19 consecutive automated checks of chatgpt.com.
Detected by DownBits probe
Some APAC users are seeing errors in ChatGPT Work, conversations, and GPTs.
We are investigating the issue for the listed services.
Confirmed on the vendor status page
Elevated errors with GPT-5.6 Instant in FedRAMP workspaces
We have applied the mitigation and are monitoring the recovery and no longer seeing any errors.
Confirmed on the vendor status page
Degraded performance in Codex and Work mode: Dot turn failures, delayed responses, and reduced proactivity
We are investigating the issue for the listed services.
Confirmed on the vendor status page
Dot in Codex may fail to create new threads
We have applied the mitigation and are monitoring the recovery.
Confirmed on the vendor status page
ChatGPT degraded performance
DownBits detected degraded performance on ChatGPT between 7 Oct 2026, 11:10 – 17:30 IST, lasting ongoing. Detected across 76 consecutive automated checks of chatgpt.com.
Detected by DownBits probe
ChatGPT degraded performance
DownBits detected degraded performance on ChatGPT between 7 Oct 2026, 06:50 – 08:40 IST, lasting ongoing. Detected across 22 consecutive automated checks of chatgpt.com.
Detected by DownBits probe
Unable to create new ChatGPT Work threads in latest version of desktop app
We are actively working on a fixed app version for Windows.
Confirmed on the vendor status page
Workspace Agents Degraded and Responses Impacted
We have applied the mitigation and are monitoring the recovery.
Confirmed on the vendor status page
ChatGPT degraded performance
DownBits detected degraded performance on ChatGPT between 6 Oct 2026, 21:25 – 01:50 IST, lasting ongoing. Detected across 53 consecutive automated checks of chatgpt.com.
Detected by DownBits probe
ChatGPT degraded performance
DownBits detected degraded performance on ChatGPT between 6 Oct 2026, 19:15 – 19:30 IST, lasting ongoing. Detected across 3 consecutive automated checks of chatgpt.com.
Detected by DownBits probe
Computer Use Is Experiencing Issues
We are investigating issues for agents api and computer use.
Confirmed on the vendor status page
Errors processing large PDFs in the Responses API
We are implementing the mitigation.
Confirmed on the vendor status page
Elevated error rates in ChatGPT Go conversations
We have applied the mitigation and are monitoring the recovery.
Confirmed on the vendor status page
Elevated errors affecting multiple products including ChatGPT (conversations), Image generations, Spaces and Pages, API rehydration, and Dots.
We have applied the mitigation and are monitoring the recovery.
Confirmed on the vendor status page
ChatGPT is responding normally. Our last automated check of chatgpt.com completed 9 minutes ago and succeeded in 128 ms. Over the past 24 hours the service answered 100.00% of our checks.
Measured from our automated checks, ChatGPT has been available 100.00% over 24 hours, 99.95% over 7 days, 99.95% over 30 days. We recorded 65 incidents in the last 30 days.
ChatGPT has averaged 149 ms across our successful checks in the past 24 hours, which is fast — comfortably within what a healthy service should return. Response time is measured from our probe to chatgpt.com and does not include rendering time in your browser.
The most recent incident DownBits recorded for ChatGPT began on 8 October 2026 at 08:55 IST and lasted 1 hr 35 min. It was logged as degraded performance. Detected by DownBits probe.
Our probe is reaching chatgpt.com normally right now, so the problem is more likely to be local to you than a full outage. Use the report button on this page to add your own signal — when several people report the same problem within a short window, it appears on the chart above.
A working marketing site does not mean a working API. Call the API host directly — curl -s -o /dev/null -w "%{http_code}" https://chatgpt.com/ — and check the vendor status page linked above for component-level detail, since one component can fail while the rest stay green.
HTTP 429 and 529 mean you are being throttled, not that the service is down. Inspect the response headers for a retry-after value and back off exponentially rather than retrying immediately.
A 401 or 403 is an authentication problem on your side. Rotated keys, an expired billing method, or a revoked token all present as sudden total failure.
Open any other site. If nothing loads, the issue is your network rather than ChatGPT. On Windows run ping chatgpt.com and nslookup chatgpt.com in Command Prompt; on macOS or Linux use Terminal. A DNS failure and a server failure look identical in a browser but are very different problems.
Load chatgpt.com in a private or incognito window. If it works there, clear cookies and site data for chatgpt.com in your normal browser rather than clearing everything.
Switch from Wi-Fi to mobile data, or vice versa. Regional ISP routing problems are common and often affect one carrier while others are unaffected.
We link the vendor status page so you can check our reading against theirs.
No comments received
