ARCHIVED OFFICIAL INCIDENT

Cache Purging Delays Affecting Requests Routed Through EEUR

Cloudflare · Last saved provider status: monitoring

Current service report →
This is historical evidence.

The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.

Saved event details

Provider status
monitoring
Provider impact
minor
Provider record created
27 Oct 2026, 15:10:35 UTC
Provider record updated
27 Oct 2026, 16:02:33 UTC
Explicit provider start
27 Oct 2026, 15:10:35 UTC
Explicit provider end
Not available

Affected components reported by the provider

  • Stockholm, Sweden - (ARN) 755n430pjn1s
  • CDN Cache Purge fbvx0hxhhdj0

These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.

A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.

Cloudflare's complete published platform report and provider locations. These are provider reports, not independent network observations or evidence of an application's upstream dependencies. Workers AI, AI Gateway and Replicate have separate component views.

Provider updates in saved revisions

Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.

  1. monitoring

    A fix has been implemented and we are monitoring the results.

    Seen in a saved revision at 27 Oct 2026, 16:04:42 UTC
  2. investigating

    Some single-file cache purge requests (purge by URL) submitted through the Dashboard or API and routed through our EEUR purge queues are experiencing delays of up to 30 minutes. Cache invalidation for these requests may be delayed across our global network. This also affects Always Online. We are working to resolve the issue. As a temporary workaround, you may use Purge Everything, but this may cause a surge in traffic to your origin server(s) More updates to follow.

    Seen in a saved revision at 27 Oct 2026, 16:04:42 UTC
  3. investigating

    Cloudflare single-file cache purging (purge by URL) called via the Dashboard/API is running up to 30 minutes behind. This also affects the "Always Online" feature. We are working to resolve this issue as soon as possible. Until then, you may use the Purge Everything feature but do be aware it may cause a surge in traffic to your origin server(s). More updates to follow.

    Seen in a saved revision at 27 Oct 2026, 15:13:39 UTC

Cookie preferences

With your permission, we use Google Analytics and Umami to understand service queries. These tools use cookies or browser storage. Optional analytics stay off until you accept.

Cookies and storage details