Skip to content
All alerts

OpenAI posts another status-page incident in quick succession, "Incorrect cost data in Costs API exports" (impact: none, status: monitoring), continuing a cluster of same-day incident postings.

notable

OpenAI has posted a cluster of status-page incidents in quick succession, which clears our tripwire for repeated same-day postings regardless of any one incident's impact. The incident cited here, "Incorrect cost data in Costs API exports," carries impact "none" and status "monitoring," so the signal is the clustering itself rather than this incident's own severity.

status.openai.com86e599f45bd68aa3e97753e7a75f938f8be3267789a3858a004ee17cb3019132

Cited changes

Every field of each cited change, before and after.

added incidentIncorrect cost data in Costs API exports · none · open

Record fields before and after the change
Field Before After
components ∅[]
impact ∅none
incident_id ∅01M71W79MAGEXEX93QTVTBYJ4K
incident_url ∅https://status.openai.com/incidents/01M71W79MAGEXEX93QTVTBYJ4K
provider ∅openai
resolved_at ∅∅
started_at ∅2026-11-10T04:42:21Z
status ∅monitoring
title ∅Incorrect cost data in Costs API exports
status.openai.comincident:openai:01M71W79MAGEXEX93QTVTBYJ4K detected

Data from the last 90 days is CC BY 4.0. Older data is CC BY-NC 4.0, except what we published before 2026-11-04, which stays CC BY 4.0. How you can reuse it.