Cloudflare Argo was down

cloudflarestatus.com

49 points·rkwasny··10 comments

Reminds me of an old tweet by @DEVOPS_BORAT [0]:

> To make error is human. To propagate error to all server in automatic way is #devops.

[0]: https://twitter.com/devops_borat/status/41587168870797312

Unfortunately this is a problem with adding another layer, now not only provider has to be up, bgp etc but also cloudflare.

> Cloudflare is investigating issues with Argo Tunnel connections in our Los Angeles data center. New tunnel registration attempts are impacted globally, as well.

Doesn't disrupt existing non-LAX connections at least.

Resolved - This incident has been resolved. Jan 8, 22:59 UTC

Monitoring - New tunnel connections should now succeed. Cloudflare is monitoring the issue. Jan 8, 22:13 UTC

Update - Cloudflare is investigating issues with Argo Tunnel connections in our Los Angeles data center. New tunnel registration attempts are impacted globally, as well. Jan 8, 21:12 UTC

Investigating - Cloudflare is investigating issues with Argo Tunnel connections in our Los Angeles data center. Existing connections and new connections may be impacted.

We are working to mitigate this problem. More updates to follow shortly. Jan 8, 20:34 UTC

Hats off to the NOC team.

For those not familiar with Argo - https://www.cloudflare.com/products/argo-smart-routing/

It's not that. It's the Argo Tunnel connector https://www.cloudflare.com/products/argo-tunnel/

Also, it wasn't down globally but new connections were failing. Existing ones were fine.

I enabled Argo today on a site and I don't see any difference in latency...

So, is it routing around the damage?

You mean CloudFlare?

Reply on news.ycombinator.com