The IsUpMap lets you check the status of over 100 major sites at once
Posted by mikelgan 5 days ago
Comments
Comment by ashfn 5 days ago
Comment by marcosdumay 4 days ago
But then, the home page can be cached, and bots can be batched and nobody would ever notice the difference.
Comment by throrork 4 days ago
Comment by colinbartlett 4 days ago
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.
Comment by pc86 4 days ago
Comment by colinbartlett 4 days ago
Comment by iFred 4 days ago
Comment by 0123456789ABCDE 5 days ago
Comment by zenoprax 5 days ago
There is still a tendency within some parts of aviation (safety auditing) to look for root causes and use tools like "fish bone diagrams" despite the more holistic approach used after an actual crash or incident.
Comment by kortilla 4 days ago
Comment by rcxdude 4 days ago
Comment by kortilla 3 days ago
My toaster and the dam 1000 miles away are on the same electrical grid. Calling my toaster part of the electrical generation system because it consumes from it doesn’t make sense.
Coming back to the dashboard example, almost none of those work together to provide some kind of combined outcome you would expect from complex systems analysis (e.g. electrical generation, healthcare, etc).
If all of the boxes were ISPs instead, it would be a great example. Because they all work together to provide IP connectivity to the world and many can be down while the overall internet continues to function.
Comment by rcxdude 3 days ago
Comment by 0123456789ABCDE 4 days ago
you're it does not.
> Most of these have no relation to each other other than the high level services on the cloud providers.
so, some of them are related to each other? some of them even share underlying infrastructure? perhaps multiple of these are considered infrastructure for some teams?
what is the point you're trying to make?
Comment by sammy2255 4 days ago
Comment by politelemon 5 days ago
Comment by colinbartlett 4 days 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).
Comment by somewhatgoated 4 days ago
And what does it mean exactly?
Comment by xiphias2 5 days ago
Comment by talonx 4 days ago
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.
Comment by iFred 4 days ago
Comment by smelbe 2 days ago
Comment by ninju 4 days ago
Does the size indicate anything?
Comment by dvh 5 days ago
Comment by tristor 4 days ago
If you're drawing the data from a public resource like downdetector or using the sites status pages, then you may not be reflecting reality, but it should be clear what the provenance of the data is.
Comment by xyst 5 days ago
Comment by TeMPOraL 5 days ago
Comment by 1e1a 4 days ago
Comment by zamadatix 4 days ago
Comment by huhtenberg 4 days ago
Comment by chedoku 4 days ago
Comment by chedoku 4 days ago
Comment by cednore 4 days ago
Comment by talonx 4 days ago
Comment by hulitu 4 days ago
Comment by Crunchified 4 days ago
Comment by fosron 4 days ago
Comment by b3lvedere 5 days ago
Comment by cleansy 5 days ago
Comment by tcumulus 5 days ago
Comment by haktan 5 days ago
Comment by progbits 5 days ago
Comment by gegtik 4 days ago
Comment by aetch 4 days ago
Comment by UrbanNorminal 5 days ago
Comment by wakeless 5 days ago
``` if(github) return false ```
Comment by chaidhat 5 days ago
Comment by TheGrassyKnoll 4 days ago