View Evidence Brief What changed, who says so and when, and what was known at each revision.
Four clocks
| Began (provider) | Wed, 18 Nov 2026 12:15:02 GMT |
| Latest update published (provider) | Wed, 18 Nov 2026 12:15:02 GMT |
| Seen by Spike | Wed, 18 Nov 2026 12:18:25 GMT |
| Delivered | Per customer, in each Spike Pro workspace's delivery receipts. |
What the provider states
| Claim | Value | Evidence |
|---|---|---|
| service status | identified | Direct: OpenAI status page · source ↗ |
| Cause | OpenAI has not stated a cause in a structured field. Read the provider's updates. | |
| Customer impact | Depends on what you run. Spike Pro matches this incident to the services a workspace lists. | |
Revisions, newest first
- Revision 1 · Incident opened
Published by OpenAI 2026-11-18 12:15 UTC · seen by Spike 3 min laterOpenAI said: “We have identified that users are experiencing elevated errors for the impacted services. We are working on implementing a mitigation.”