Breaking

View Evidence Brief What changed, who says so and when, and what was known at each revision.

Four clocks

Began (provider)Thu, 19 Nov 2026 06:48:06 GMT
Latest update published (provider)Thu, 19 Nov 2026 08:32:01 GMT
Seen by SpikeThu, 19 Nov 2026 08:32:25 GMT
DeliveredPer customer, in each Spike Pro workspace's delivery receipts.

What the provider states

ClaimValueEvidence
service statusmonitoringDirect: Cloudflare status page · source ↗
affected servicesAccessDirect: Cloudflare status page · source ↗
CauseCloudflare has not stated a cause in a structured field. Read the provider's updates.
Customer impactDepends on what you run. Spike Pro matches this incident to the services a workspace lists.

Revisions, newest first

  • Revision 2 · Status changed: identified → monitoring
    Published by Cloudflare 2026-11-19 08:32 UTC · seen by Spike 0 min later

    Cloudflare said: “A fix has been implemented and we are monitoring the results.”

  • Revision 1 · Incident opened
    Published by Cloudflare 2026-11-19 06:48 UTC · seen by Spike 0 min later

    Cloudflare said: “Cloudflare is investigating an issue with Cloudflare Access. A recent Cloudflare Access release removed the sub claim from service token JWTs, which can cause authentication failures for applications that strictly validate token claims. The change has been reverted and the fix…”

This record as JSON · All outages