Hi Product Hunt 👋 I'm Kerolos, a solo developer. Every time something broke, I'd end up with a dozen status-page tabs open trying to answer one question: is it us, or is it a vendor? OutageDeck is that question, answered. It reads the official status feeds of 172 cloud and SaaS vendors, AWS, Cloudflare, GitHub, OpenAI, Google Cloud, Slack, Twilio, Vercel, and so on, every 10 minutes, and turns them into: - one live board for your stack. Pick your vendors, or paste a package.json and it finds them, and get one answer you can share as a link: https://outagedeck.com/stack?p=a... - outage alerts to email, Slack, Teams, Discord, or webhook - an independent, timestamped record of what each vendor acknowledged and when - a free JSON API with no account and no key - a status wall you can paste into a README: https://outagedeck.com/embed - an MCP server, so your coding agent checks whether the vendor is down before it starts rewriting your code: https://outagedeck.com/developer... Two things I decided early that shaped everything else. Official feeds only. No crowd reports, no page scraping, no synthetic probes. Everything traces back to the vendor's own machine-readable source. The tradeoff is honest: a smaller catalog than aggregators that scrape or crowdsource, and no "users are reporting" early warning. What you get instead is zero false positives and provenance on every data point. And because a fixed catalog can never cover everyone, paid accounts can point OutageDeck at any Statuspage or Instatus page it doesn't already track. That vendor then joins your account privately, with the same alerts and the same history as anything in the catalog. A few things I learned from reading 172 status feeds: - In the last 30 days, the catalog logged 1,429 incidents across 150 of the 172 providers, and 369 of them were rated major or critical by the vendor itself. - The longest incident currently open on a tracked vendor's own status page has been open for 694 hours. Vendors forget to close them, so I label that "stayed open" rather than "downtime", because those are different claims. - Stripe's public status JSON has been frozen since February 2024. It still answers 200 and still says everything is fine, so I refuse to list them rather than serve a fossil. - No consumer carrier, Vodafone, AT&T, Verizon, publishes an official machine-readable status feed at all. - AWS's feed is UTF-16 with a byte-order mark. The dashboard, API, badges, and RSS are free with no account. Email alerts for up to 5 providers are free with an account, about a minute to set up, no card. Paid plans from $19 add Slack, Teams, Discord, and webhook, remove the provider cap, and add your own custom feeds. It's bootstrapped and runs on about $55 a month of infrastructure. I'd love feedback, especially on which vendors you'd want tracked next. If it runs on Statuspage, I can usually have it live the same day, and if you're on a paid plan, you don't have to wait for me.

Forum Threads

p/outagedeck

•

2d ago

Official status or synthetic probes: which signal do you trust first?

I'm building OutageDeck around official provider status feeds, but I do not think an official feed should be the only production signal. Providers can acknowledge incidents late, while synthetic checks can fail because of your own credentials, DNS, region, or deployment.

My current triage model is:

- provider incident + probe failure: strong upstream evidence

- provider operational + probe failure: unclassified failure, investigate our stack and keep watching the feed

View all

OutageDeck

One status page for every service your stack depends on

One status page for every service your stack depends on

Forum Threads

Official status or synthetic probes: which signal do you trust first?

Forum Threads

Official status or synthetic probes: which signal do you trust first?