talonx

AI slop-code has exacerbated the problem and GitHub is not able to keep up. If you look at the last 12 month's outage reports from GitHub's own status page, many of them mention capacity issues as an underlying cause.

They don't have straightforward status pages or APIs to detect outages - I think that's the reason they are not listed.

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.

Oh thank you! I sorely miss the original HS website.

And worse - when I open Google News all the news under Technology is about the latest mobile phones and "gadgets".

I remember Firefox used to have this cool feature where you could detect any RSS feeds on the page you have open.

Now if I don't see it on a page I check the page source - some blogs don't advertise the feed but it's there.

BetterStack did report issues with some of their services, but they were not very informative.

- What I'm working on right now - https://incidenthub.cloud - It monitors cloud/SaaS status pages. I'm working on some white-labeling features.

- New ideas - Easier way for new users to try out the product. It's currently a few steps, but I want to optimize it for specific user personas.

You're welcome.

Ah, to be honest I did not look at the tour.

Thanks for explaining #2 - but the text "Auto" might be a bit non-intuitive for a user.

Congrats on launching this.

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.

They published a detailed incident report - https://webflow.com/blog/july-28-webflow-incident-report

What I find disturbing here is the number of people who are supporting him saying that he is a victim of the system.

Irrespective of his skills or how broken the system is, dishonesty can never be condoned.

I'm building Incidenthub.cloud - a B2B SaaS that monitors public status pages of third-party dependencies.

It was born out of a personal need in past roles and teams. I launched it last year.