OutageDeck Reviews and Details

Questions & Answers

1. Which are the primary technologies used for building OutageDeck?

   • Frontend / app: Next.js 16 (App Router), React 19, TypeScript, Tailwind CSS
   • Data: Supabase Postgres. Every upstream feed is validated with Zod, so provider format drift fails loudly instead of corrupting data
   • Ingestion: each vendor's official feed polled every 10 minutes, with per-provider failure isolation, so one broken feed never blocks the rest
   • Alerting: a delivery ledger with exactly-once claims, so overlapping runs never double-page anyone

2. What's the story behind OutageDeck?

   I got tired of opening a dozen vendor status pages during every incident, just to work out whether the problem was mine or somebody else's. So I built the thing I wanted.

   It launched in July 2026 as one live board over the official status feeds of cloud and SaaS vendors teams depend on. The catalog changes as official sources are added or removed.

   The rule from day one: official machine-readable sources only. No crowd reports, no scraping. If a status can't be traced back to the vendor's own feed, it doesn't get published.

3. How would you describe the primary audience of OutageDeck?

   Anyone whose incident channel regularly starts with "is AWS down, or is it just us?":

   • DevOps, SRE, and platform engineers. Answer "is it us or them?" in seconds during an incident.
   • Small SaaS teams. Your uptime depends on other people's clouds, so see whether a vendor has acknowledged a problem before changing your own stack.
   • Agencies and MSPs. Watch the vendor stacks of many clients from one place.

4. Why should a person choose OutageDeck over its competitors?

   Choose it when your problem is third-party vendor status, not when you need synthetic monitoring of your own application.

   • Fast triage. One stack view normalizes current status, affected services, source timestamps, and incident history across the cloud and SaaS vendors your product depends on. You can use it without an account.
   • Traceable, limited claims. Every record links to the vendor's official source. Providers can acknowledge incidents late, so OutageDeck should be a second signal beside direct provider checks and probes from your own regions. Its own health endpoint is checked from a separate GitHub-hosted workflow with public run history.
   • Useful exits. Free accounts add email alerts for five providers. Paid plans add Slack, Teams, Discord, webhooks, and private Statuspage or Instatus feeds. Developers can use the keyless JSON API, RSS, badges, CLI, MCP server, GitHub Action, or Open WebUI tool.

5. What makes OutageDeck unique?

   OutageDeck only reports what vendors officially publish. Every status comes from the provider's own machine-readable feed, never crowd reports and never scraping. Then it holds vendors to what they said:

   • Observed uptime history from archived vendor-published status, with honest partial and regional impact framing
   • Every incident links back to its source on the vendor's own status page
   • One dashboard for the cloud and SaaS vendors your product depends on, with alerts to Slack, Teams, Discord, email, or webhooks
   • Bring your own feed on paid plans: point it at any Statuspage or Instatus page it does not track yet
   • A JSON API, RSS feeds, README badges, and an MCP server so a coding agent can check the vendor before it blames your code