← Back to Cloudflare History
minor✓ Resolved

Cache Purging Delays in Amsterdam

Cloudflare•
Status
resolved
Duration
1h 41m
Updates
4
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
This incident has been resolved.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
Cloudflare single-file cache purging (purge by URL) called via the Dashboard/API is delayed in Amsterdam. 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.

📊 TECHNICAL DETAILS

Internal ID
bf4704c4-596f-45eb-bc6e-1a0d1cd236c6
External ID
xsgbfncq7of7
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
1h 41m
Total Duration
4
Status Updates
Affected Components
CDN Cache Purge
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed