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).
The Apple status pages (both of them) are some of the worst of the big league offenders, perhaps second only to Microsoft.
Full disclosure, I operate a product that compares official outage acknowledgment to actual outage impact times. (Which I won't mention to avoid self-promotion.)
For this specific incident, I saw the alert come across my Slack at 19:02 UTC. We received over 100 reports of this outage before the official acknowledgement was posted by Apple on their status page at 21:37 UTC.
Shortly after their acknowledgment, the reports fizzled out and then Apple marked the incident as resolved about 20 minute later.
The whole outage lasted about 4 hours from first report to last and wasn't acknowledged by Apple until 3.5 hours into it.
I thought so, too. I randomly found this on Reddit and it struck a chord with me, especially as an urban dweller that absolutely despises litter and litterers.
They do back a lot of companies. Is there any evidence that they are pushing unethical or illegal business practices on their portfolio companies at a rate higher than non-YC start ups?
GitHub published a postmortem for yesterday's outage already, and the cause surprised me: They blame scrapers, or rather ONE specific scraper, for taking down GitHub for 7 hours.