BREAKING: Cloudflare MINOR ⚠️ Dedicated Egress London Down [7dk3g4k188ky]

Cloudflare Dedicated Egress in London experiencing partial disruption. Immediate workarounds for indie hackers affected by egress routing issues.

BREAKING: Cloudflare Dedicated Egress London — Partial Disruption

Status: Identified | Severity: MINOR | Updated: NOW

---

What's Down & Who's Affected

Cloudflare's Dedicated Egress service in the London data center is experiencing partial disruption. This affects:

Projects using Cloudflare Workers with dedicated egress IPs routed through London

API calls, webhooks, and outbound connections from Worker functions in that region

Static IP allowlisting scenarios where your app depends on London egress

Any Workers using cf.colo targeting London zones

Not affected: Standard Cloudflare CDN, DNS, WAF, or egress from other regions. If your traffic doesn't explicitly route through London dedicated egress, you're likely fine.

---

Immediate Workarounds (Do This Now)

1. Switch Egress Region

If your Worker supports it, immediately change your dedicated egress routing: ```javascript // Instead of London, route through Frankfurt or Amsterdam // Contact support or update your Cloudflare dashboard settings ```

2. Failover to Standard Egress

Temporarily disable dedicated egress if your allowlist permits:

Go to Workers → Settings → Egress

Switch to standard egress (shared IP pool)

Your static IP won't be stable, but traffic flows

3. Redirect Traffic Elsewhere

If you operate multi-region:

Route EU traffic through Frankfurt/Amsterdam workers temporarily

Update DNS or load balancer to bypass London

Test failover now—don't wait for full recovery

4. Notify External Services

If you're calling third-party APIs with IP allowlisting:

Contact them immediately: "Temporarily using different egress IP due to Cloudflare incident"

Request temporary IP allowlist expansion if possible

---

How to Check If You're Affected

Quick diagnosis:

1. Check your Cloudflare Workers dashboard → Settings → Egress. Is "Dedicated" enabled with London selected? 2. Run a test call from your Worker to an external service. Is it timing out or failing? 3. Use curl https://whatismyipaddress.com from your Worker. Does the IP match your dedicated static IP? 4. Check Cloudflare Status Page: [status.cloudflare.com](https://status.cloudflare.com) for updates

If all three are yes → you're affected. Act now.

---

Alternative Tools to Consider

If Cloudflare egress continues degrading:

Fly.io: Dedicated egress with global region selection

AWS Lambda + NAT Gateway: Full control, static IPs, multi-region

Heroku: Legacy but stable egress from multiple regions

Bunny CDN: Egress options in 30+ regions

Render: Workers alternative with egress control

Don't migrate yet. Cloudflare usually resolves these in 1-2 hours. Use alternatives only if this persists beyond 4 hours.

---

Monitor Recovery

1. Watch Cloudflare Status: [status.cloudflare.com](https://status.cloudflare.com) — they update every 15-30 min 2. Join Cloudflare Discord: Real-time reports from other devs 3. Test Actively: Don't passively wait. Run actual requests to external APIs every 10 minutes 4. Set Alerts: Monitor your Worker error logs; recovery will show zero egress timeouts

---

Bottom Line

This is not a critical issue unless London egress is your only path. Immediate action: switch regions or disable dedicated egress. Cloudflare's London infrastructure will recover. Stay calm, test your fallback, and monitor.

Next update: 30 minutes.