colinbartlett
Joined 14 years ago
Joined 14 years ago
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).
I've been building something like this for 12 years now.
One major difference is mine does not only rely on the "official" status page but also receive millions of reports from users about outages.
So your single pane of glass can show not just known outages but emerging ones that haven't been acknowledged yet by providers.
Also supports more than 8,000 services.
This isn't the first outage and won't be the last but it's one of the most disruptive in recent memory.
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 wasn't a Mac user at home, but school had them and I absolutely loved what I could create with HyperCard, there was nothing like it on Windows.
I also recall switching to SuperCard simply for the COLOR support, what a time.
Also run: https://vimtricks.com and https://trackssl.com
Corporate site: https://nimbleindustries.io
Personal site: https://colinabartlett.com
my public key: https://keybase.io/cbartlett; my proof: https://keybase.io/cbartlett/sigs/NVWkHww8PUhCwgi4NeNE5ZPnno_HwJi9Z0beRohHR-0