3 ms·
Or just a bad global configuration change. We used to take down Netflix globally with config changes until we changed the system to have config changes scoped
by jedberg 5y ago
Or just a bad global configuration change. We used to take down Netflix globally with config changes until we changed the system to have config changes scoped to single regions.
And even then sometimes the failure wouldn't show up until multiple regions got the config change.
- mrkurt 5y agoAlways bet on a config change. Or DNS.
- pgporada 5y agoNeither of these apply to this situation though. We're working on it.
- mrkurt 5y agoI lose many of my bets.
- terom 5y agoIt sounds like it was a hardware issue [1]. First rule of electronics applies: thou shalt check voltages. > [Update] We're conducting follow-up maintenance to address power supply issues from our earlier service disruption. All production API services may be down for up to 30 minutes. [1] https://letsencrypt.status.io/pages/maintenance/55957a99e800baa4470002da/60f5f2460451310998105e7f https://letsencrypt.status.io/pages/maintenance/55957a99e800...