OutageDeck's answer:

• 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

OutageDeck's answer:

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:

• Independent uptime history, with honest partial and regional impact framing
• Every incident links back to its source on the vendor's own status page
• One dashboard for 172 vendors, 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

OutageDeck's answer:

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 the vendors teams actually depend on. The catalog is at 172 now: AWS, Cloudflare, GitHub, OpenAI, Google Cloud, Slack, Twilio, and a long tail of others.

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.

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

OutageDeck's answer:

Three reasons.

• Pricing. Paid plans start at $19 a month flat with unlimited vendors, 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 vendors, no card.
• 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. A JSON API you can call without an account, RSS feeds, README status badges, and an MCP server for coding agents. No login gate on any of it.