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.
I understand this is an initial launch, so not trying to nitpick, but these are what felt like would add immediate value:
- Adding a social login like Google would allow faster signups.
- Maybe I missed it - but I could not find any options for automatic monitoring which would update the status page. There are manual options for adding an incident.
- Post-signup, it takes me to a login page. Why ask to enter the company name instead of user/pass directly?
- If I could click on "Components" on my dashboard (/admin) and go directly to the Components page, that would be nice.
I like it that you took the time to write a privacy policy that is both readable and precise, especially as to the list of third-party services.
Working on my SaaS that monitors third-party status pages - https://incidenthub.cloud/ It's a one-person project I started last year.
My biggest technical challenge remains dealing with the immense number of different APIs (and not-APIs) in the different status pages out there. Marketing remains my biggest overall challenge as my background is engineering, but I've learnt quite a bit since I launched this.
It's technically the "Bengali–Assamese script". There is a difference of 3 letters between the written forms of these two languages, including the one you pointed out.
Google translate added Assamese recently, that might explain the gaffes.
Building incidenthub.cloud