← Back to Cloudflare History
minor✓ Resolved
Increase in R2 Sippy 404s
Status
resolved
Duration
2h 9m
Updates
3
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedThu, Feb 12, 2026, 08:25 PM
This incident has been resolved.
monitoringThu, Feb 12, 2026, 08:10 PM
We are continuing to monitor for any further issues.
monitoringThu, Feb 12, 2026, 08:10 PM
A fix has been implemented and we are monitoring the results.
investigatingThu, Feb 12, 2026, 06:15 PM
Cloudflare is investigating reports of Sippy returning 404 on objects which do exist at the upstream provider. We are working to understand the full impact and mitigate this problem.
Updates will be posted as they become available.
📊 TECHNICAL DETAILS
Internal ID
30f36b21-8745-499e-ada5-86baa8c06601
External ID
79c2573c1n3r
🕐 Started
Thu, Feb 12, 2026, 06:15 PM
🔄 Last Updated
Thu, Feb 12, 2026, 08:25 PM
✓ Resolved
Thu, Feb 12, 2026, 08:25 PM
MINOR
Impact Level
2h 9m
Total Duration
3
Status Updates
Affected Components
R2
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed