Independent monitoring

OpenAI status

Operational

Merlonix has monitored OpenAI around the clock and recorded every status change we observed. Below is a 30-day timeline of those observations and any incidents OpenAI reported.

Snapshot as observed by Merlonix at Oct 8, 2026, 08:31 AM UTC. This is a point-in-time snapshot, not real-time — see the live vendor board for the current minute-by-minute status.

Independent monitoring by Merlonix. Not affiliated with, endorsed by, or an official status page of OpenAI. All observations are Merlonix’s own, sampled independently from OpenAI’s published status source. OpenAI is a trademark of its respective owner and is named here only to describe what we monitor.

30-day observation timeline

Each cell is one UTC day, coloured by the most severe status we observed that day. A “degraded” day reflects OpenAI’s own published component-level status and may mean a single component was affected while the overall service was fine.

OperationalDegradedPartial outageMajor outageMaintenanceNo data

Observations recorded

106

distinct status changes over 30 days we have data for

Most recent change

Oct 8, 2026

last time the observed status changed

Days by observed status

  • Operational13d
  • Degraded12d
  • Partial outage4d
  • Major outage1d

What Merlonix monitors for OpenAI

Merlonix polls OpenAI's published status source around the clock and records every change we observe — overall status, component-level incidents, and their start/resolve times. The timeline and incidents below are Merlonix's own observations, sampled independently of OpenAI.

Recent incidents OpenAI reported

No incidents recorded from OpenAI’s status source in the current observation window.

Get alerted the moment OpenAI has a bad day.

Merlonix watches OpenAI and your other upstreams around the clock and suppresses the false alerts they would otherwise trigger on your own sites — so you only get paged when the problem is actually yours.

How vendor-aware alerting works →