Is ChatGPT down right now?
Authenticated API inference - 2 models monitored · How we classify outages
Weekly AI pricing & uptime digest
Price drops, new model releases, and incident summaries - every Monday. Free.
ChatGPT is currently operational - but official reports minor issues - 57ms HTTP response. Last checked . 90-day uptime: 100%. ChatGPT API: all 2 models responding - fastest TTFT 802ms.
Delayed Costs data in the Compliance API
Stay informed
Follow @tickerr_ai
We post when tier 1 LLM APIs go down - before the official status page updates.
Follow on X →Or get the weekly reliability digest:
Add a status badge
Show live ChatGPT status on your site, README, or docs.
HTTP uptime (90d)
100%
20 incidents (90d)
HTTP response now
57ms
HTTP p50 (7d)
130ms
median ping response
HTTP p95 (7d)
260ms
tail ping response
API Inference Monitoring
Live · every 5 minBest TTFT (p50)
802ms
time to first token
Best throughput
94tok/s
output tokens/sec (24h avg)
Min success rate
100%
worst model (24h)
P50 = typical speed. P95 = worst case 95% of the time. Measured by Tickerr's independent inference checks. Requires ≥10 checks to display.
TTFT over 24 hours
ⓘ Authenticated streaming API calls via native fetch. TTFT = milliseconds from request start to first streamed token chunk. Throughput = output tokens ÷ generation time. Checks run from Vercel us-east-1. Independent of the provider's official status page.
Is ChatGPT slow right now?
ChatGPT is currently experiencing degraded performance. All 2 monitored models are responding within their normal speed range.Last checked just now.
HTTP endpoint response: 57ms (7-day p50: 130ms). This measures basic reachability, not model inference speed.
TTFT (time-to-first-token) is measured via authenticated streaming API calls every 5 minutes. Current values are compared against 7-day and 30-day rolling baselines. A minimum of 5 successful checks is required before classification. Methodology
ChatGPT speed FAQ
Is ChatGPT slow right now?
ChatGPT is currently experiencing degraded performance. All 2 monitored models are responding within their normal speed range.
Why is ChatGPT so slow today?
ChatGPT is experiencing elevated latency compared to its normal baseline. This can happen during high-demand periods, model updates, or infrastructure issues. Tickerr monitors time-to-first-token (TTFT) every 5 minutes across all ChatGPT models to detect slowdowns automatically.
Is ChatGPT down or just responding slowly?
ChatGPT is not fully down, but it is experiencing degraded performance. Some features or models may be slower or less reliable than usual.
How does Tickerr determine whether ChatGPT is slow?
Tickerr sends authenticated API requests to ChatGPT every 5 minutes and measures time-to-first-token (TTFT). Current TTFT is compared against a rolling 7-day and 30-day baseline. A model is classified as slow when its current p50 TTFT exceeds 2x its baseline, and severely slow at 3.5x. At least 5 successful checks are required before any classification is made.
What is normal response time for ChatGPT?
The normal p50 TTFT for ChatGPT is approximately 847ms based on the trailing 7-day baseline. This means half of all requests receive their first token within 847ms. The HTTP endpoint typically responds in 130ms.
Can one ChatGPT model be slow while others are working normally?
Yes. ChatGPT runs multiple models (e.g. gpt-4.1-mini, gpt-4o-mini), and each can have independent performance characteristics. Tickerr monitors each model separately. A slowdown on one model doesn't necessarily affect others.
Experimental capability checks
PUBLIC PILOTTickerr sends deterministic test prompts to ChatGPT every hour and evaluates the output using code-based pass/fail checks. These results are informational onlyduring the pilot period and do not affect the tool's status verdict.
How Tickerr tests this
Every hour, Tickerr sends three deterministic test prompts to each monitored model via the provider's API. Each response is evaluated with a code-based pass/fail check — no subjective judgement.
- Instruction following: asks the model to reply with an exact word. Graded by exact string match.
- JSON schema: asks for a JSON object matching a fixed schema. Graded by parse + field validation.
- Tool call: asks the model to call a function with specific arguments. Graded by parsing the tool-call response.
Infrastructure errors (timeouts, rate limits, auth failures) are tracked separately and excluded from capability pass rates. Models that don't support tool calls are marked “not supported” rather than counted as failures. Full methodology
HTTP endpoint response time (7 days)
p50 130ms·p95 260msⓘ HTTP response times to ChatGPT's status endpoint - measures infrastructure availability, not API inference speed. For TTFT and model-level API status, see the ChatGPT API Status section above.
90-day uptime comparison
Independent monitoring catches issues faster - official pages sometimes lag by hours before acknowledging problems.
Service components
via status.openai.com ↗Incident history
We are investigating an issue affecting some ChatGPT workspace administrators’ ability to view and manage plugin availability and settings. Some users may also see plugins as unavailable. We will prov…
We have identified an issue affecting the ChatGPT Android app where users may see “This content is unavailable in this version of the app” instead of certain content. A fix is rolling out gradually in…
We have identified an issue causing delays in publishing organization cost data through the Costs API. API and ChatGPT usage are not affected, and other reporting channels remain available. We are wor…
We are investigating the issue for the listed services.
We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.
We are investigating the issue for the listed services.
We are investigating the issue for the listed services.
We are investigating the issue. Version 26.1002.51308 is affected
We are investigating the issue for workspace agents, users may not see the responses during the issue time.
We are investigating issues for agents api and computer use.
We are investigating the issue for the listed services.
We are investigating the issue for the listed services.
We are investigating the issue for the listed services.
We are investigating the issue for the listed services.
We have identified that users are experiencing elevated errors within Codex Cloud. We are working on implementing a mitigation.
We are investigating elevated error rates affecting some ChatGPT conversations. Error rates are improving, and our team is continuing to assess recovery. We will share further updates as they become a…
We are investigating the issue for the listed services.
We are investigating the issue for the listed services. Some users may be unable to save changes or reconnect to live editing sessions.
We are observing elevated Work Mode errors. Scheduled tasks may also be impacted.
Some users experienced errors when running code, analyzing data or creating files in ChatGPT. We have applied the mitigation and are monitoring the recovery.
Related pages
ChatGPT API not working? Common error codes
If ChatGPT's API is returning errors, the table below explains what each code means and how to fix it. If errors are widespread, check the live status above - a service incident will appear there within minutes.
| Error | What it means & what to do |
|---|---|
| HTTP 429 | Rate limit or quota exceeded - check tier limits and retry with backoff |
| HTTP 500 | Internal server error - retry once; if persistent, check status.openai.com |
| HTTP 503 | Service unavailable - check for active OpenAI incidents |
| "context_length_exceeded" | Input too long for model - truncate or summarize context |
Note: Tickerr monitors ChatGPT's status endpoint, not individual API calls. An HTTP 429 or 500 in your app may be specific to your account tier - check the rate limits page for plan-specific thresholds.
About ChatGPT status
ChatGPT is an AI chatbot and API built by OpenAI, powering millions of apps and users globally. This page tracks two independent signals: HTTP availability (is chatgpt.com reachable?) and live API inference (is the OpenAI API actually working for developers?). Tickerr makes authenticated API calls to GPT-4o-mini, GPT-4o, and o4-mini every 5–15 minutes, measuring TTFT (time-to-first-token) and output throughput. This catches model-layer failures and overloads that don't show up as HTTP outages. Common ChatGPT API errors: HTTP 429 (rate limit or quota exceeded - check your tier and add backoff), HTTP 500 (internal server error - retry once), HTTP 503 (service unavailable - check for active incidents). OpenAI's official status page at status.openai.com is typically updated within 15–30 minutes of a confirmed incident; Tickerr's independent inference monitoring surfaces issues faster.
You can also check the official ChatGPT status page.