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 08:04:29 GMT |
| Latest update published (provider) | Wed, 18 Nov 2026 08:46:42 GMT |
| Seen by Spike | Wed, 18 Nov 2026 08:53:25 GMT |
| Delivered | Per customer, in each Spike Pro workspace's delivery receipts. |
What the provider states
| Claim | Value | Evidence |
|---|---|---|
| service status | resolved | Direct: Cloudflare status page · source ↗ |
| affected services | Ahmedabad, India - (AMD), Hyderabad, India - (HYD), Kanpur, India - (KNU), Mumbai, India - (BOM), Nagpur, India - (NAG), New Delhi, India - (DEL), Patna, India - (PAT) | Direct: Cloudflare status page · source ↗ |
| affected regions | India | 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 4 · Resolved
Published by Cloudflare 2026-11-18 08:46 UTC · seen by Spike 7 min laterCloudflare said: “This incident has been resolved.”
- Revision 3 · Status changed: identified → monitoring
Published by Cloudflare 2026-11-18 08:38 UTC · seen by Spike 2 min laterCloudflare said: “A fix has been implemented and we are monitoring the results.”
- Revision 2 · Status changed: investigating → identified
Published by Cloudflare 2026-11-18 08:22 UTC · seen by Spike 1 min laterCloudflare said: “The issue has been identified and a fix is being implemented.”
- Revision 1 · Incident opened
Published by Cloudflare 2026-11-18 08:04 UTC · seen by Spike 2 min laterCloudflare said: “Cloudflare is investigating a network disruption across multiple datacenters in India, impacting some Cloudflare services in region. We are working to analyse and mitigate this problem. More updates to follow shortly.”