trending
•

1mo ago

One user, 11 alerts, and the first real lesson from launch day

Today one person signed up from the launch page and created a five-provider email alert. Then GitHub, Cloudflare, and Anthropic all had real incident changes before the afternoon was over.

The subscription received 11 lifecycle emails. GitHub moved from incident to recovery. Cloudflare moved through a partial outage and resolution. Anthropic moved from degraded models back to operational.

Every delivery completed on the first attempt. That is the part I am proud of.

The less flattering lesson is that correct can still become noisy. Eleven messages in roughly two hours is useful evidence for an operator, but it may be too much for a normal inbox.

•

2mo 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

•

2mo ago

OutageDeck - One status page for every service your stack depends on

OutageDeck tracks 172 cloud and SaaS vendors from official feeds, with alerts, history, a free JSON API, and an MCP server your agents can query. Paid accounts can add private Statuspage or Instatus providers, including their own products: no crowdsourcing or scraping.