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 13:45:19 GMT |
| Latest update published (provider) | Wed, 18 Nov 2026 15:03:07 GMT |
| Seen by Spike | Wed, 18 Nov 2026 15:04: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 | R2 | Direct: Cloudflare status page · source ↗ |
| affected regions | Japan | 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 3 · Resolved
Published by Cloudflare 2026-11-18 15:03 UTC · seen by Spike 1 min laterCloudflare said: “This incident has been resolved.”
- Revision 2 · Status changed: investigating → monitoring
Published by Cloudflare 2026-11-18 14:40 UTC · seen by Spike 1 min laterCloudflare said: “A fix has been implemented and we are monitoring the results.”
- Revision 1 · Incident opened
Published by Cloudflare 2026-11-18 13:45 UTC · seen by Spike 1 min laterCloudflare said: “Cloudflare is aware of, and investigating an issue where R2 Downloads are stalling for users connecting via datacenters in Japan. Further detail will be provided as more information becomes available.”