4 ms·
Why did it take so long for a status page to be published I wonder? From the timeline in the blog post the issue with Atlanta was fixed between 21:39 to 21:47
by itsjloh 6y ago
Why did it take so long for a status page to be published I wonder?
From the timeline in the blog post the issue with Atlanta was fixed between 21:39 to 21:47 but a status page wasn't published until 21:37. Everything had been broken for over 20 minutes at that stage with lots of people already posting about it or other status pages reflecting issues. See https://twitter.com/OhNoItsFusl/status/1284239769548005376 https://twitter.com/OhNoItsFusl/status/1284239769548005376 or https://twitter.com/npmstatus/status/1284235702540984321 https://twitter.com/npmstatus/status/1284235702540984321
Without an accurate status page it leaves businesses pointing the finger everywhere wondering whether its their hosting provider having issues, their CDN, DNS provider etc etc.
- eastdakota 6y agoBecause of the way we securely connect to StatusPage.io from most locations where our team is based. The traffic got blackholed in ATL, keeping us from updating it. An employee in our Austin office was finally able to use his Google Fi phone and connect through a PoP that wasn’t connected to our backbone so didn’t have traffic blackholed. Something we’ll address going forward.
- itsjloh 6y agoDamn that sucks, sounds like a stressful Friday evening for all involved. Thanks for taking the time to answer.