CheckWebsiteNow

Live status check

Is OpenAI down right now?

We check openai.com from one measurement point when you open this page. This shows what we saw, not a worldwide verdict.

A fresh check of openai.com runs in your browser. If no result appears, run the check on the start page.

Our last check

Not checked yet — a fresh check starts when you open this page.

About OpenAI problems

Problems with openai.com can concern the OpenAI API, where errors such as rate limits, invalid API keys and temporary server errors come back as HTTP status codes. A rate limit or quota error is about your account or organisation, not a sign that the API is down. OpenAI's status page lists known problems with the API and ChatGPT separately.

Official information

OpenAI official status page (verified )

Our check and OpenAI's own status page can disagree. We test from one location and read only the homepage response. The provider reports what it knows about its own systems, such as sign-in, apps or single regions. A site can answer our check while one feature is broken, and a regional problem can affect one location but not another.

OpenAI help pages

How this check works

  • One measurement location (single-self-hosted-probe), not a worldwide test.
  • We read only the response headers of the HTTPS homepage; page content and features are not tested.
  • We follow at most 5 HTTPS redirects and check every new address again.
  • The whole check stops after 10 seconds.
  • Results are reused for 60 seconds; this page refreshes its saved check at most every 10 minutes.

Full method and limits

Typical OpenAI problems

An editorial list of typical problems, not based on live user reports.

  • API rate limit or quota reached The OpenAI API returns a 429 when your organisation sends requests too fast or has used up its quota, so check your usage and limits in the OpenAI dashboard. Guide: 429 Too Many Requests
  • Invalid or missing API key A 401 from the OpenAI API means the key is missing, mistyped, revoked or belongs to a different project than the one you are calling. Guide: 401 Unauthorized
  • API server errors An internal error from the OpenAI API is on OpenAI's side, so retry with a short delay and check status.openai.com if it continues. Guide: 500 Internal Server Error
  • API overloaded or unavailable When the OpenAI API answers that it is unavailable or overloaded, waiting and retrying with backoff is safer than sending the request again immediately. Guide: 503 Service Unavailable
  • Requests time out Long OpenAI API requests can hit the timeout of your own client or proxy before the answer is ready, so check the timeout settings in your code. Guide: ERR_TIMED_OUT

General fixes: AI

  1. Read the exact message AI services can show usage limits and real errors as different messages. A limit message may say when you can continue, while a general error can point to a problem on the service's side.
  2. Start a new conversation Very long conversations or large attachments can fail on their own. Ask the same question in a new chat, with a smaller file if you attached one.
  3. Keep a copy of long prompts Write long prompts in a text editor first. If an answer breaks off or the page reloads, you can paste the prompt again instead of retyping it.
  4. Check the API key and usage For API access, compare the key, the project and the remaining quota in the provider's console before you change your code.

Check another website

One measurement point. Results explain what we saw, not a worldwide verdict.