View Evidence Brief What changed, who says so and when, and what was known at each revision.
Four clocks
| Began (provider) | Tue, 10 Nov 2026 01:53:58 GMT |
| Latest update published (provider) | Wed, 11 Nov 2026 05:05:06 GMT |
| Seen by Spike | Wed, 18 Nov 2026 03:34:25 GMT |
| Delivered | Per customer, in each Spike Pro workspace's delivery receipts. |
What the provider states
| Claim | Value | Evidence |
|---|---|---|
| service status | identified | Direct: Cloudflare status page · source ↗ |
| affected services | Workers, Queues | Direct: Cloudflare status page · source ↗ |
| Cause | Cloudflare 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 · First recorded by Spike
Published by Cloudflare 2026-11-11 05:05 UTC · seen by Spike 9989 min later (first read of this status page)Cloudflare said: “The issue has been identified and a fix is being implemented.”