Última hora
United States flag Teerão tem armas biológicas? Trump pondera atacar o Irão Observador · agora mesmo•France flag França: Estrasburgo lidera mercados de Natal mais acessíveis da Europa Euronews · há 1 h•Europa quer que as famílias estejam preparadas para as crises. Mas e se não for possível preparar-se? Euronews · há 1 h•Assista ao Jornal da Manhã g1 · há 1 h•Tânia Graça: “Não odeio os homens, o que odeio é este sistema patriarcal” Público · há 1 h•“Será difícil abrir mão de armas nucleares”, diz Trump diante de Putin e Xi CNN Brasil · há 1 h•Gil de graça em Niterói, eventos da Semana da Consciência Negra, Honk! Rio: o que fazer no Rio g1 · há 1 h•Portugal flag Isaltino deve achar que em Portugal vale tudo Observador · há 1 h•United States flag Teerão tem armas biológicas? Trump pondera atacar o Irão Observador · agora mesmo•France flag França: Estrasburgo lidera mercados de Natal mais acessíveis da Europa Euronews · há 1 h•Europa quer que as famílias estejam preparadas para as crises. Mas e se não for possível preparar-se? Euronews · há 1 h•Assista ao Jornal da Manhã g1 · há 1 h•Tânia Graça: “Não odeio os homens, o que odeio é este sistema patriarcal” Público · há 1 h•“Será difícil abrir mão de armas nucleares”, diz Trump diante de Putin e Xi CNN Brasil · há 1 h•Gil de graça em Niterói, eventos da Semana da Consciência Negra, Honk! Rio: o que fazer no Rio g1 · há 1 h•Portugal flag Isaltino deve achar que em Portugal vale tudo Observador · há 1 h

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

1What changed since the last material update?

Compared with brief revision 6 (incident revision 6):

  • Resolved · incident revision 7
FieldBeforeNow
statusmonitoringresolvedchanged
provider impactminorminorsame
servicesCache Reserve, D1, R2Cache Reserve, D1, R2same
regionsEurope, Asia PacificEurope, Asia Pacificsame
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-19 03:19 UTC · incident revision 7 · fonte ↗
Provider impact levelminorProvider statement Cloudflare · published 2026-11-18 22:26 UTC · incident revision 1 · fonte ↗
Services namedCache Reserve, D1, R2Provider statement Cloudflare · published 2026-11-18 22:26 UTC · incident revision 4 · fonte ↗
Regions namedEurope, Asia PacificProvider statement Cloudflare · published 2026-11-18 22:26 UTC · incident revision 3 · fonte ↗
Latest provider updateThis incident has been resolved.Provider statement Cloudflare · published 2026-11-19 03:19 UTC · incident revision 7 · fonte ↗
Severity used for sorting1Spike inference SpikeTrendWatch · incident revision 7

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.

Late-arriving evidence (incident revision 2): Cloudflare dated this update 2026-11-18 22:26 UTC, before Spike's previous record at 2026-11-18 22:27 UTC. It was not in the provider's feed until later, so no reader could have seen it earlier. Brief revision 1 did not include it, although the provider dates it earlier.

Late-arriving evidence (incident revision 3): Cloudflare dated this update 2026-11-18 22:26 UTC, before Spike's previous record at 2026-11-18 22:56 UTC. It was not in the provider's feed until later, so no reader could have seen it earlier. Brief revisions 1, 2 did not include it, although the provider dates it earlier.

Late-arriving evidence (incident revision 4): Cloudflare dated this update 2026-11-18 22:26 UTC, before Spike's previous record at 2026-11-18 23:47 UTC. It was not in the provider's feed until later, so no reader could have seen it earlier. Brief revisions 1, 2, 3 did not include it, although the provider dates it earlier.

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 22:26 UTC
Published by Cloudflare2026-11-19 03:19 UTC
Observed and published by Spike2026-11-19 03:20 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 7 uses only what Spike had recorded by 2026-11-19 03:20 UTC: incident revisions 1, 2, 3, 4, 5, 6, 7. Later updates are excluded, so this view reads the same every time it is opened (content fingerprint e4233b0222c1531b).

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