OutageDeck's answer

OutageDeck was built by an engineer tired of tab-cycling through a dozen vendor status pages during every incident, just to work out whether the problem was internal or upstream.

It launched in July 2026 as one live dashboard over the official status feeds of the providers teams actually depend on, and the catalog quickly grew to 168 — AWS, Cloudflare, GitHub, OpenAI, Google Cloud, Slack, Twilio, and more.

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

OutageDeck's answer

OutageDeck only reports what vendors officially publish — every status comes from the provider's own machine-readable feed, never crowd reports or scraping — and then holds vendors accountable for it:

• Independent uptime history, with honest partial/regional-impact framing
• Every incident links back to its source on the vendor's own status page
• One dashboard for 168 providers, with alerts to Slack, Discord, email, or webhooks
• A JSON API, RSS feeds, and README status badges for putting status wherever you work

OutageDeck's answer

Three reasons:

• Pricing — paid plans start at $19/mo flat with unlimited providers, while most alternatives meter by "monitors" and get expensive as your stack grows. The free tier is genuinely useful: email alerts for up to 5 providers, no card required.
• Honesty — official-sources-only means you never get paged over a rumor; statuses, uptime history, and incident timelines all trace back to the vendor's own feed.
• Developer surface — an anonymous-friendly JSON API, RSS feeds, and embeddable README status badges, no login gate.

OutageDeck's answer

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; know before your customers tell you.
• Agencies and MSPs — watch the vendor stacks of many clients from one place.

OutageDeck's answer

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