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

What to do

• Check whether your product depends on Cloudflare. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-09-11 06:22 UTC and 2026-09-11 06:22 UTC may need a replay.

• Subscribe to Cloudflare's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=cloudflare works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Cloudflare 1

1. resolvedSep 11, 2026, 6:22 AM 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.