Hacker Newsnew | past | comments | ask | show | jobs | submit | talonx's commentslogin

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.


With these guys you get into a weird world of "is it them, us, or upstream of both of us" all the time. I had been using Twilio's telco partner maintenance notifications as a way of figuring out if someone like Orange was responsible for a bunch of French end points independent of Twilio had network degradation.

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.


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.


Hello! Really appreciate the feedback.

1. Social login is almost done - decided to ship without it to get feedback faster, but it'll be added soon.

2. Yes! Automated health checks are there - check out step 4 on the tour page (https://upty.dev/tour). They automatically update component status when thresholds are crossed. Auto-creating incidents from health checks isn't ready yet, but you can use the API to create incidents programmatically in the meantime.

3. Good catch on the post-signup flow - I'll fix that.

4. Noted on the dashboard navigation, makes sense.

Thanks for the kind words about the privacy policy! Let me know if you hit any other issues.


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.


Agree, it's unintuitive, and I'll fix that. No problem, thanks for finding time to write the feedback. I really appreciate it.


You're welcome.


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


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: