3 ms·
> On-call attempts to re-enable the R2 Gateway service using our internal admin tooling, however this tooling was unavailable because it relies on R2. It's com
by ko_pivot 2y ago
> On-call attempts to re-enable the R2 Gateway service using our internal admin tooling, however this tooling was unavailable because it relies on R2.
It's comforting to see this happen to a big tech co!
- S0y 2y agoThat line also made me chuckle quite more than it should have.
- philipwhiuk 2y agoI was surprised not to see a follow up on this item
- d1sxeyes 2y agoWhile considering that sounds sensible, it seems the on-call was able to escalate to the team with very little delay. As far as I can tell from the timeline, it only took 11 minutes from the moment the on-call first attempted the action until the ops team began responding. Given that this issue was caused by someone unintentionally using a level of access that they had to do something they did not intend, and the minimal impact reduction, deciding not to grant higher levels of access to the on-call seems to me to be the right decision.
- belter 2y agoMy LLM weights say the word Incident and Cloudflare are never more than two clicks away... :-) https://hn.algolia.com/?q=cloudflare+incident https://hn.algolia.com/?q=cloudflare+incident
- Permik 2y agoI'd guess that this actually affects all [corp same scale as Cloudflare], but Cloudflare is the only one that's actually transparent about it.