Show HN: I built an alternative status page for public clouds(cloudlooking.glass)
cloudlooking.glass
Show HN: I built an alternative status page for public clouds
https://cloudlooking.glass/#show=median
4 comments
Looks neat. When you detect anomalies, how can you tell whether it's the cloud provider or the public internet or a transient peer tho?
For data and control plane I can determine the issue from the API request/response logs (i.e., network timeout, 5xx, etc.). Network tests are trickier and we don't have a great way to validate failure cause each of those events (i.e., we don't capture a traceroute on failure), other than to evaluate results from multiple endpoint combinations (e.g., AWS us-east-1 to us-west-1 fails while us-east-2 to us-west-1 succeeds).
For networking, the site only reports uptime % for zonal, regional, cross-region or cross-cloud tests. It excludes last mile network tests as those fail frequently due to many hops and endpoint unreliability (we use Ripe Atlas and Globalping.io endpoints which are not always reliable even with redundant probes per test).
Happy to answer any questions also.
I modeled it as a time series problem: all tests are repeated every 5 minutes from three unrelated cloud accounts per platform (currently ~1,000 tests/min). The system provides full data plane, control plane, and networking coverage for AWS us-east-1, plus network testing across 25 other providers. Full coverage for GCP and Azure is coming soon.
It also has a cloud looking glass for real-time zonal, regional, cross-region, cross-cloud, and last-mile network testing (ping, tcping, traceroute, MTR, etc.).
Would love feedback, suggestions, or advice.
https://cloudlooking.glass#show=uptime