Is ChatGPT down right now?
Authenticated API inference - 2 models monitored · How we classify outages
ChatGPT is currently operational - but official reports minor issues - 54ms HTTP response. Last checked . 90-day uptime: 99.8%. ChatGPT API: all 2 models responding - fastest TTFT 930ms.
Codex Context Compaction Latency
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)
99.8%
20 incidents (90d)
HTTP response now
54ms
HTTP p50 (7d)
190ms
median ping response
HTTP p95 (7d)
790ms
tail ping response
API Inference Monitoring
Live · every 5 minBest TTFT (p50)
930ms
time to first token
Best throughput
87tok/s
output tokens/sec (24h avg)
Min success rate
98%
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.
Agent monitoring active · 13 agents reporting · Powered by Tickerr MCP
HTTP endpoint response time (7 days)
p50 190ms·p95 790msⓘ 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
Identified - Codex Context Compaction Latency
Investigating - Android ChatGPT Business users having trouble switching workspaces
Investigating - Elevated Latency and Errors on API
Identified - Users unable to access chat support on help center
Investigating - Login issues for FedRAMP users who recently logged out
gpt-4o-mini API Latency Degraded
Independent monitoring detected elevated API latency for gpt-4o-mini. Current TTFT is 2.1× above the rolling p50 baseline (1453ms vs p50 700ms). The service is responding but slower than normal. Ticke…
Investigating - Increase in users hitting Codex rate limits
Identified - Elevated latency and error rates for ChatGPT 5.5 Thinking
Identified - Elevated error rates on ChatGPT paid plans
Identified - API users may see increased error rates for GPT-5.4 and GPT-5.5
gpt-4.1-mini API Latency Degraded
Independent monitoring detected elevated API latency for gpt-4.1-mini. Current TTFT is 2.9× above the rolling p50 baseline (2449ms vs p50 850ms). The service is responding but slower than normal. Tick…
Investigating - GPT5.5 Performance Degradation
Identified - Codex Cloud and Code Review experiencing high failure rate
Investigating - Issues accessing ChatGPT for logged-out users
Investigating - Codex 5.5 engines are experiencing high error rate
Investigating - Realtime API - SIP/WebRTC flow are down
Investigating - Elevated error rates with GPT 5.5
Investigating - Users may experience elevated errors in ChatGPT uploading files and Codex Cloud creating tasks
gpt-4.1-mini API Latency Degraded
Independent monitoring detected elevated API latency for gpt-4.1-mini. Current TTFT is 2× above the rolling p50 baseline (1495ms vs p50 733ms). The service is responding but slower than normal. Ticker…
Monitoring - Elevated errors for Responses API
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.