Cache Purging Delays Affecting Requests Routed Through EEUR
Cloudflare · 最近保存的提供方状态：monitoring
官方来源文字以原始语言显示。
最近保存的事件状态不是当前服务状态。来源列表可能不完整，事件从来源消失不确认恢复。请打开当前报告或官方来源查看较新证据。
已保存事件详情
- 提供方状态
- monitoring
- 提供方影响程度
- minor
- 提供方记录创建时间
- 27 10月 2026, 15:10:35 UTC
- 提供方记录更新时间
- 27 10月 2026, 16:02:33 UTC
- 提供方明确报告的开始时间
- 27 10月 2026, 15:10:35 UTC
- 提供方明确报告的结束时间
- 不可用
提供方报告的受影响组件
- Stockholm, Sweden - (ARN)
755n430pjn1s - CDN Cache Purge
fbvx0hxhhdj0
这些关联描述此事件的报告范围。不能确认当前组件可用性或已核实依赖关系。
记录创建时间未必是故障开始时间。未报告的时间保持不可用。我们不根据采集时间计算故障时长。
Cloudflare 完整的已发布平台报告和提供方地点。这些是提供方报告，不是独立网络观测或应用上游依赖的证据。Workers AI、AI Gateway 和 Replicate 有独立组件视图。
已保存修订中的提供方更新
最新优先。最多显示最近 20 份已保存内容修订中的 100 条不同更新。同一提供方时间的文字修订单独保留。
- monitoring
A fix has been implemented and we are monitoring the results.
在 27 10月 2026, 16:04:42 UTC 的已保存修订中观察到 - 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.
在 27 10月 2026, 16:04:42 UTC 的已保存修订中观察到 - 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.
在 27 10月 2026, 15:13:39 UTC 的已保存修订中观察到