- Recovery did not erase the disclosed monitoring gap.
What changed
Cloudflare opened a load-balancing monitoring incident on September 14 and marked it resolved on September 15 at 02:27 UTC. Its recovery update says health-event analytics and notifications are current again, but events and notifications between 22:02 and 22:45 UTC were skipped. The initial notice explicitly said traffic steering remained operational.
Why it matters
Service availability and the evidence used to monitor it can diverge. Operators reviewing that interval should distinguish missing monitoring records from an absence of health changes. The disclosed gap matters for incident reconstruction even though Cloudflare says the mechanism directing traffic continued to work.
What remains unproven
The notice does not explain the cause, quantify affected customers or promise reconstruction of the skipped records. Resolution establishes the provider’s reported recovery state, rather than a complete historical record.
Read beyond this page.
Recorded source-check date: 15 Sep 2026. A link is not, by itself, evidence that every claim has been independently verified.
Changes & version history
Version 3 · 15 Sep 2026
Scheduled release of checksum-bound AI-assisted editorial review
Version 2 · 15 Sep 2026
Checksum-bound editorial review scheduled for release
Version 1 · 15 Sep 2026
Source-linked private review edition