DownForAI

OpenAI status: API, auth, latency & outage reports

OpenAI is operational right now. Last tracked incident: September 3, 2026. DownForAI checks 4 monitored surfaces every ~75 minutes.

Operational
Last probe 1h ago·4 surfaces·9 reports / 24h
Official statusHigh confidence
📡 Official status page →📚 Docs →💳 Pricing →
100.0%
24h Uptime
222ms
p50 Network Latencyⓘ
393ms
p95 Network Latencyⓘ
3
Incidents (30d)

DownForAI tracks OpenAI across 4 monitoring surfaces: OpenAI API, ChatGPT, DALL-E, and Sora. Current status: operational — all surfaces are responding normally. Measured uptime over the last 24 hours: 100.0%. Median response time (24 h): 243 ms; p95: 425 ms.

OpenAI had 3 tracked incidents in the last 30 days. Most recent: "Community-reported issues: OpenAI" on September 3, 2026 lasting 28 min. 9 community reports were submitted in the last 24 hours, primarily down.

Data confidence: HighLast checked 1h 14m ago · 4 monitored surfaces · 4 with 24 h latency data

Current Status

✅
Operational
Everything works normally
✓Checked by our probes · 184ms
Verified 1h ago
✓No major incident reported
ⓘ9 user reports in the last 24h

Having issues?

Help other users by reporting if OpenAI is not working for you.

9reports in the last 24 hours

Surface Health

OpenAI APIOperational
HTTP 200p50 243ms3h ago
ChatGPTOperational
HTTP 200p50 214ms2h ago
DALL-EOperational
HTTP 200p50 189ms1h ago
SoraOperational
HTTP 200p50 243ms3h ago

Uptime — last 24h

100.0%

Network latency — last 20 probes

Loading…

What DownForAI can verify about OpenAI

No confirmed provider-side issue detected
DownForAI currently sees OpenAI as operational based on available monitoring signals.
Signal source: official status API · Monitoring confidence: High
Still having trouble?

The issue may be account-specific, regional, network-related, or related to authentication, billing, quota, or rate limits.

Incident history (30d)

3 incidents
Community-reported issues: OpenAI
Resolved
Sep 3, 16:02· 28mMINOR
Community signal: 1 reports in the last 30 min (threshold 5). Peak 1.
Community-reported issues: OpenAI
Resolved
Sep 3, 15:30· 31mMINOR
Community signal: 5 reports in the last 30 min (threshold 5). Peak 5.
openai experiencing issues
Resolved
Aug 31, 16:16· 4h 14mMAJOR
Our monitoring detected that openai may be experiencing an outage.

Reported symptoms

9 reports / 24h
💬DOWN
9×100%

Community reports

What users are saying right now

A
Anonymous💬 down16h ago
404 error
A
Anonymous💬 down10d ago
It is not responding to anything I send
A
Anonymous💬 down40d ago
unexpected status 503 Service Unavailable: {"detail":"{\"error\":\"Too many concurrent requests\"}"}, url: cf-ray: a20a0ccd4ca64e17-ICN, request id: 6a67d888-e7eb-48cb-8b97-b121bc6e230b
A
Anonymous💬 down46d ago
abo can not be loaded
A
Anonymous💬 down72d ago
uploads not working

Known error signatures

Common failure patterns and how to diagnose them

Provider details

The OpenAI API provides programmatic access to OpenAI models (chat completions, responses, realtime, images, audio, embeddings, batch, files, assistants). Different infrastructure from ChatGPT web.

What we monitor
Chat Completions API —
Responses API —
Realtime API — Streaming audio/text
Images API —
Audio API — TTS/Whisper
Embeddings API —
Batch API — Async
Assistants API —
Files API —
Status page segments
APIsChatGPTCodexSora
Model families
GPT-5, GPT-4o, GPT-4o minio1, o3 (reasoning)DALL-E 3 (images)Whisper (STT), TTS
Common limits & quotas
  • API access uses tiered rate limits (Tier 1-5) based on payment history and usage
  • Rate limits expressed per-model in requests-per-minute (RPM) and tokens-per-minute (TPM)
  • Tier thresholds and exact limits are published on platform.openai.com
Ecosystem dependencies
Many third-party apps depend on OpenAI APIs; dependency patterns varyAzure OpenAI Service is a distinct infrastructure, not a proxyAssistants API depends on Files API for attached resources
Operator notes
  • The Azure OpenAI/direct OpenAI split is the most important fallback for production users
  • Rate limit headers (x-ratelimit-*) return real quota state on every response — log them proactively, don't wait for 429
  • Tier upgrades are often automatic based on spending; programmatic tier probing is unnecessary
  • For Realtime API, connection drops are expected; implement reconnect logic, don't flag as outage
Diagnostic signals
x-request-idx-ratelimit-limit-requestsx-ratelimit-remaining-requestsx-ratelimit-reset-requestsx-ratelimit-limit-tokensx-ratelimit-remaining-tokensretry-after$ curl https://api.openai.com/v1/models -H "Authorization: Bearer $OPENAI_API_KEY" — basic reachability + lists models$ curl https://api.openai.com/v1/chat/completions -H "Authorization: Bearer $OPENAI_API_KEY" -H "Content-Type: application/json" -d '{"model":"gpt-4o","messages":[{"role":"user","content":"ping"}]}' — real inference test$ curl -I https://api.openai.com — TLS/DNS sanity check

Fallback alternatives

What to use if this service is down

Direct OpenAI API is degraded
Azure OpenAI Service can reduce downtime for prod workloads (separate infrastructure)
Low-medium cost if already provisioned
Easy switch
Full OpenAI ecosystem unavailable
Anthropic API, Google Gemini API, Mistral API can reduce downtime for general chat
Low cost with abstraction layer
Easy switch
Embeddings API down
Voyage AI or Cohere Embed are drop-in alternatives
Easy switch
Latency-sensitive workloads
Groq (fast inference on open-weight models) can reduce latency tail
Different model quality
Moderate effort

How we monitor

DownForAI checks monitored AI service surfaces on a rotating schedule, roughly every 75 minutes per surface, from a single centralized probe infrastructure. For services with an official machine-readable status page, we use that official status signal when available. For other services, we perform a basic public-surface check. Some services block datacenter probes; in those cases we mark them as “Monitoring limited” instead of treating a failed probe as a confirmed outage. Status is classified as Operational, Degraded, or Outage. Network latency (check response time) measures how long the monitored endpoint took to respond to our probe — it is not model inference speed, time-to-first-token, or tokens-per-second performance. We are independent of all providers listed and receive no compensation to report any particular status.

OpenAI statusEmbed this status badgeREADME · docs ▾
Markdown
[![OpenAI status](https://downforai.com/api/badge/openai.svg)](https://downforai.com/openai)
HTML
<a href="https://downforai.com/openai"><img src="https://downforai.com/api/badge/openai.svg" alt="OpenAI status" /></a>

Community Discussion

0/1000
No comments yet. Be the first to share your experience!

Still having issues with OpenAI?

Let the community know and help others experiencing the same problem.