Who is down right now

20 down now · 248 this week

Cloudflare · Cloud and hostingSep 11, 2026, 06:22 UTC 8 weeks ago

Issues with Workers VPC hostname route resolution on 2026-09-11

InformationalDeploymentUpdated 46d ago
Sep 11, 06:22 UTCSep 11, 06:22 UTC
Duration
0m
Impact
Informational
Root cause
Deployment
Cloudflare, 90 days
187 incidents
Affected
Not listed by the vendor.
Status page

Final update

An issue prevented Workers VPC from correctly resolving hostname routes for a small subset of accounts between 06:22 and 09:38 UTC on Friday, September 11th, 2026. This problem has been fully resolved, and all services are operating normally. During this timeframe, affected accounts may have experienced connection failures, timeouts, or routing errors when Workers VPC attempted to fetch requests via hostname routes. The issue was strictly limited to hostname route resolution within Workers VPC for the impacted accounts; direct IP-based and public routing, standard Workers executions, and all other services were not affected. Our engineering team identified and deployed a fix for the root cause, and we are continuing to monitor service metrics to ensure stability. We sincerely apologize for any disruption this may have caused.

Timeline

  1. Resolved · Sep 11, 06:22 UTC
    An issue prevented Workers VPC from correctly resolving hostname routes for a small subset of accounts between 06:22 and 09:38 UTC on Friday, September 11th, 2026. This problem has been fully resolved, and all services are operating normally. During this timeframe, affected accounts may have experienced connection failures, timeouts, or routing errors when Workers VPC attempted to fetch requests via hostname routes. The issue was strictly limited to hostname route resolution within Workers VPC for the impacted accounts; direct IP-based and public routing, standard Workers executions, and all other services were not affected. Our engineering team identified and deployed a fix for the root cause, and we are continuing to monitor service metrics to ensure stability. We sincerely apologize for any disruption this may have caused.

More from Cloudflare

Full history

Also caused by deployment or rollout

All