Back to feed
Dev.to
Dev.to
7/18/2026
There's no standard status page, and other lessons from tracking 96 providers

There's no standard status page, and other lessons from tracking 96 providers

Short summary

The author built OutageDeck to aggregate status pages from 96 cloud/SaaS providers and discovered there is no standard status format. Atlassian Statuspage is the closest to common, but the long tail includes bespoke APIs, RSS feeds, and even UTF-16-encoded AWS event feeds. Key lessons: provider timestamps are unreliable for uptime calculation, some feeds are stale or frozen, and a lean Postgres + Next.js backend at $55/month suffices if you stop trusting upstream time and roll your own observation timestamps.

  • No standard status page format exists across 96 providers; six adapters needed
  • Provider timestamps lag by days, so uptime must be computed from your own check time
  • Lean architecture: one Next.js app + Postgres, no queue, ~$55/month

Generated with AI, which can make mistakes.

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more