Última hora

This revision as JSON · Prints cleanly from your browser's print command.

1What changed since the last material update?

Compared with brief revision 4 (incident revision 4):

  • Resolved · incident revision 5
FieldBeforeNow
statusmonitoringresolvedchanged
provider impactminorminorsame
servicesNetwork, Cloud Network Interconnect (CNI), Paris, France - (CDG)Network, Cloud Network Interconnect (CNI), Paris, France - (CDG)same
regionsFrançaFrançasame
mitigation or recoverythe provider reports a fix in place and is monitoringthe provider reports the incident resolved
From the provider's status term, not from a separate statement.
changed
cause——
Not stated by the provider in a structured field.
same

2Who says so, and when?

ClaimValueEvidence
Incident statusresolvedProvider statement Cloudflare · published 2026-11-18 04:51 UTC · incident revision 5 · fonte ↗
Provider impact levelminorProvider statement Cloudflare · published 2026-11-18 03:39 UTC · incident revision 1 · fonte ↗
Services namedNetwork, Cloud Network Interconnect (CNI), Paris, France - (CDG)Provider statement Cloudflare · published 2026-11-18 03:57 UTC · incident revision 4 · fonte ↗
Regions namedFrançaProvider statement Cloudflare · published 2026-11-18 03:49 UTC · incident revision 3 · fonte ↗
Latest provider updateThis incident has been resolved.Provider statement Cloudflare · published 2026-11-18 04:51 UTC · incident revision 5 · fonte ↗
Severity used for sorting1Spike inference SpikeTrendWatch · incident revision 5

Independent reporting and observable signals: none attached to this incident. Only the provider's own statements are shown. Public attention (for example a search spike) shows interest only. It is not evidence of cause or impact.

Conflict (incident revision 4): Cloudflare's update at incident revision 4 says: “This incident impacted Cloudflare Network Interconnect (CNI) only”. Its structured component list named Network, Paris, France - (CDG) as well. Spike shows both and does not narrow the scope itself.

Open questions

  • Cause: not stated by the provider in a structured field.
  • Customer impact: not established. The provider reports its own systems; impact on a specific business needs that business's own evidence.
Began (provider)2026-11-18 03:39 UTC
Published by Cloudflare2026-11-18 04:51 UTC
Observed and published by Spike2026-11-18 04:55 UTC
Deliveredper workspace, in its private view

3Which business service should I check?

That depends on what your business runs on. See the private view in a synthetic demo. In Spike Pro (free beta), list the providers and services you depend on; your private view of this brief then shows which business service each revision touches, whether it is a direct match or a possible exposure, and why. Customer impact always needs your own evidence.

4What did we know then?

Revision 5 uses only what Spike had recorded by 2026-11-18 04:55 UTC: incident revisions 1, 2, 3, 4, 5. Later updates are excluded, so this view reads the same every time it is opened (content fingerprint 101eeba9507c4806).

This is the latest revision.

5Who received the correction?

No correction has been published for this incident.

Delivery outcomes are private to each workspace and appear in its own view of this brief.

Handoff summary

Plain text to paste into a ticket or shift handoff.

Schema spike.evidence-brief/1. A brief is built from Spike's append-only incident revisions; it adds no facts of its own beyond the labeled Spike inferences. Incident record · API contract · Open another brief