←back to thread

698 points jgrahamc | 1 comments | | HN request time: 0s | source
Show context
jakejarvis ◴[] No.20422650[source]
Always appreciate the transparency from you and Cloudflare. :)

My main fright during this outage wasn't really the outage itself, but the fact that I couldn't log into the dashboard and simply click the orange cloud to bypass Cloudflare in the meantime. I'm assuming that this is now covered by this mitigation:

>> 6. Putting in place an emergency ability to take the Cloudflare Dashboard and API off Cloudflare's edge.

If so, and if this would have prevented the dashboard outage even during the WAF fiasco, this is a huge comfort to me. Just curious, though: how far can you really go in separating Cloudflare "the interface" from Cloudflare "the network?"

And in general, what does everyone on HN think about mission-critical companies using their own infrastructure and being their own customer? Especially when the alternative is using a competitor?

replies(2): >>20422707 #>>20423680 #
1. JaRail ◴[] No.20423680[source]
>> 6. Putting in place an emergency ability to take the Cloudflare Dashboard and API off Cloudflare's edge.

> If so, and if this would have prevented the dashboard outage even during the WAF fiasco

It wouldn't prevent the initial dashboard outage. However, in a similar situation where the main issue can't be resolved quickly, it would allow them to restore dashboard access.