OpenAI reported "Elevated FedRAMP API error rates for Astra and Sol" on its status page at 2026-10-21 14:17 UTC.

OpenAI did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-10-21 14:17 UTC and ended at 2026-10-21 19:34 UTC. It lasted 5 h 17 min.

How do I get alerts for OpenAI?

Subscribe to the OpenAI live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of OpenAI. outages.live reads it every few minutes and keeps every update.

OpenAIIncident · 2026-10-21 14:17 UTC

Elevated FedRAMP API error rates for Astra and Sol

ResolvedOfficial update

All impacted services have now fully recovered.

The latest update from OpenAI.

State

Resolved

Started

11 d ago

2026-10-21 14:17 UTC

Lasted

5 h 17 min

until 2026-10-21 19:34 UTC

Worst impact

Degraded

Timeline

4 updates

14:1715:3616:5618:1519:34

DegradedUpdate postedTimes in UTC

Investigating

2 h 28 min 47%

Monitoring

2 h 49 min 53%

Updates

Times in UTC

As posted by OpenAI

Resolved2026-10-21 19:34 UTC

All impacted services have now fully recovered.

Monitoring2026-10-21 16:46 UTC

We have applied the mitigation and are monitoring the recovery.

Investigating2026-10-21 13:51 UTC

We are investigating the issue for the listed services.

Identified2026-10-21 13:42 UTC

We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.

OpenAI in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 51 min

This incident

2.9× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

3 days

median 1 h 51 min

90 days agoToday

Other OpenAI incidents

All incidents

OpenAI·Elevated errors with search in Dots, ChatGPT Work, and certain ChatGPT thinking experiences

All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.

Resolvedresolved 1 d ago

OpenAI·Elevated errors for GPT Image 2 API image edits

All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.

Resolvedresolved 2 d ago

OpenAI·6.1 Sol Degraded Model Performance

All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.

Resolvedresolved 5 d ago

OpenAI·Elevated error rates for most hosted Code Reviews and Security Reviews on private GitHub repositories

The issue is now resolved.

Resolvedresolved 5 d ago

OpenAI·Elevated error rates for Ads POST requests

All impacted services have now fully recovered.

Resolvedresolved 6 d ago

Follow OpenAI

Your coding agent knows when OpenAI is down, and tells you when a failure is theirs, not yours. You can also get OpenAI incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "openai" and tell me if OpenAI has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=openai

Slack

/feed subscribe https://outages.cc/feed.xml?providers=openai

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane