This app looks to be incorrectly parsing Slack and Auth0 official status page and showing incidents as ongoing that are not
And those are just the 2 that I checked.
To be fair, accurately scraping and normalizing data from status pages is really hard to to do consistently (my company has a team of 5 engineers to do it and it's a lot of work).
Services like Cloudflare and Twilio have so many POPs globally that one or more always have an outage going on. Then there's the question of whether it's a major outage or a minor outage. Even though major status page providers like Atlassian and Incident.io have public status APIs (Cloudflare uses Atlassian), it takes more than just parsing them to determine what is "down" and at what granularity.
I run an outage detection service - and some of these issues, like parsing hundreds of - sometimes undocumented - status APIs, make for an interesting engineering problem.
With these guys you get into a weird world of "is it them, us, or upstream of both of us" all the time. I had been using Twilio's telco partner maintenance notifications as a way of figuring out if someone like Orange was responsible for a bunch of French end points independent of Twilio had network degradation.
This app looks to be incorrectly parsing Slack and Auth0 official status page and showing incidents as ongoing that are not
And those are just the 2 that I checked.
To be fair, accurately scraping and normalizing data from status pages is really hard to to do consistently (my company has a team of 5 engineers to do it and it's a lot of work).
Yea I was wondering where that data/info was coming from?
And what does it mean exactly?
Cloudflare as well
Services like Cloudflare and Twilio have so many POPs globally that one or more always have an outage going on. Then there's the question of whether it's a major outage or a minor outage. Even though major status page providers like Atlassian and Incident.io have public status APIs (Cloudflare uses Atlassian), it takes more than just parsing them to determine what is "down" and at what granularity.
I run an outage detection service - and some of these issues, like parsing hundreds of - sometimes undocumented - status APIs, make for an interesting engineering problem.
With these guys you get into a weird world of "is it them, us, or upstream of both of us" all the time. I had been using Twilio's telco partner maintenance notifications as a way of figuring out if someone like Orange was responsible for a bunch of French end points independent of Twilio had network degradation.