WhatBrokeToday
GTA 6FAQ
OpenAI

OpenAI: Elevated conversation errors for Free and Go users

medium

Is it fixed? Yes.

Resolved after 1 h 58 min. First reported Nov 18, 12:15 UTC, resolved Nov 18, 14:13 UTC. The vendor posted it on its status page first.

What happened

OpenAI experienced elevated conversation errors impacting the Conversations component for Free and Go users. The incident has since been resolved.

What caused it?

Under active investigation. No report has identified a root cause yet.

No verified workaround yet

This incident was resolved upstream without a reported workaround.

Official fix

Timeline

  1. Investigating(done)
  2. Workaround available(skipped)
  3. Resolved(current)
  1. First report on status page

    Elevated conversation errors for Free and Go users

    Source
  2. Official statement

    Status: Identified We have identified that users are experiencing elevated errors for the impacted services.

    Source
  3. Official statement

    ⚠️ OpenAI is reporting an incident: Elevated conversation errors for Free and Go users Identified: We are working on implementing a mitigation.

    Source
  4. Status changed

    Status changed: investigating → resolved (official status page reports resolution).

  5. Official statement

    ✅ Resolved: OpenAI - Elevated conversation errors for Free and Go users

    Source
Show all 6 updates
  1. First report on status page

    Elevated conversation errors for Free and Go users

    Source
  2. Official statement

    Status: Identified We have identified that users are experiencing elevated errors for the impacted services.

    Source
  3. Confirmed on Bluesky post

    ⚠️ OpenAI is reporting an incident: Elevated conversation errors for Free and Go users

    Source
  4. Official statement

    ⚠️ OpenAI is reporting an incident: Elevated conversation errors for Free and Go users Identified: We are working on implementing a mitigation.

    Source
  5. Status changed

    Status changed: investigating → resolved (official status page reports resolution).

  6. Official statement

    ✅ Resolved: OpenAI - Elevated conversation errors for Free and Go users

    Source

Evidence

3 reports · 1 Status, 2 BlueskyShow
  1. [1]
    Status First report
    Elevated conversation errors for Free and Go users(opens official status page in a new tab)

    Status: Identified We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation. Affected components Conversations (Degraded performance)

    by openai status

  2. [2]
    Bluesky
    ⚠️ OpenAI is reporting an incident: Elevated conversation errors for Free and Go users(opens the official status page in a new tab)

    ⚠️ OpenAI is reporting an incident: Elevated conversation errors for Free and Go users Identified: We are working on implementing a mitigation. Affected components Conversations (Degraded performance) t.lpl.dev/3TpZVQe

    by telescope.littleplanetlabs.comOpens the official status page 0upvotes 2comments97% match

  3. [3]
    Bluesky
    ✅ Resolved: OpenAI - Elevated conversation errors for Free and Go users(opens the official status page in a new tab)

    ✅ Resolved: OpenAI - Elevated conversation errors for Free and Go users

    by telescope.littleplanetlabs.comOpens the official status page 0upvotes 0comments92% match

FAQ

What happened in the OpenAI outage?

OpenAI experienced elevated conversation errors impacting the Conversations component for Free and Go users. The incident has since been resolved.

What is affected by the OpenAI outage?

OpenAI.

When did the OpenAI outage start and end?

It started Nov 18, 12:15 UTC and was resolved Nov 18, 14:13 UTC, after 1 h 58 min.

How do I get alerts for OpenAI?

Subscribe to the OpenAI RSS feed for every new OpenAI incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether OpenAI is down. OpenAI feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 3 reports from 2 independent sources, including the vendor’s own status page.