PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if OpenAI is down?

PulseWatch evaluates user reports and replay-approved automated evidence for OpenAI. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported OpenAI issues today?

As of Sep 27, 2026 05:43 UTC, 0 users had reported issues with OpenAI in the previous 24 hours.

How can I report a OpenAI outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Productivity

Is OpenAI down right now?

NormalOfficial status last polled Sep 27, 2026 05:40 UTCopenai.com Official status page

OpenAI API, ChatGPT, Assistants, embeddings, and model platform availability.

Are you on the OpenAI team and see something inaccurate? Report it to us. We respond within one business day.

Is OpenAI down right now?

No. OpenAI has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Sep 27, 2026 05:43 UTC

Normal

OpenAI is operating normally

As of Sep 27, 2026 05:43 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

Sep 26, 2026 00:46 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for OpenAI.

Incident days

No recorded incident

62h 18m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for OpenAI. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

2 incidents

Busiest day

62h 18m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

OpenAI outage on September 25 — 1h 39m disruption

Sep 25, 11:07 PM → Sep 26, 12:46 AM · 1h 39m · high

On September 25, OpenAI experienced a high-severity service disruption. The incident was detected via automated signals, including the vendor's status page. Service was fully restored on September 26.

Peak reports

in 15 min

Total reports

during outage

Duration

1h 39m

until recovery

Impact

This high-severity incident affected OpenAI services for a duration of 1 hour and 39 minutes. During this period, automated monitoring systems detected a disruption. No user-reported data was collected for this incident, and therefore, no specific user-visible features, regions, or issue types can be identified from user reports.

Outage timeline

Sep 25, 11:07 PM
PulseWatch detected the incident from automated vendor and probe signals (high severity)
Sep 25, 11:07 PM
Status updated: possible issue
Sep 26, 12:46 AM
Signals cleared — incident resolved

Official updates

Sep 25, 11:07 PM
OpenAI status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

91.3%

90-day uptime

0.0%

Calculated from OpenAI's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other productivity services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedHigh

OpenAI: the vendor reports a critical-impact incident on its own status page. Single origin, not independently confirmed. Users who watch OpenAI or have an alert rule on it can be alerted, labelled vendor-reported.

9/25/2026, 11:07:02 PM · 1h 39m

11:07 PM12:46 AM

Detection9/25/2026, 11:07:02 PM · 1d ago

Detected — high severity

ResolvedMedium

OpenAI: the vendor reports an incident on its own status page without a structured impact level. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/24/2026, 7:07:07 PM · 59 min

07:07 PM08:07 PM

Detection9/24/2026, 7:07:07 PM · 2d ago

Detected — medium severity

ResolvedMedium