StatusTruth

Real outage signals for clouds and fintechs, beyond the all-green status page

Problem

When GCP europe-west2 went down, people resorted to asking each other whether it was just them. Worse, Revolut had global ATM withdrawals and transfers failing for nearly an hour while its status page stayed all green, with the issue only acknowledged in Twitter replies. Users and small teams can't quickly tell whether it's their problem or the vendor's.

Solution

Ingest official status APIs plus public social/community chatter, merge signals with simple rules and LLM scoring into a confidence-weighted live outage board that is faster and more honest than vendor status pages. Users subscribe to the services they depend on, get alerts via webhook/email/IM, and see official-vs-community discrepancies side by side.

Users

Indie developers and small SaaS ops teams depending on multiple clouds and fintech APIs; cross-border merchants and remote workers

MVP

Official status APIs for 5-10 major cloud and payment services; keyword feeds from X/Reddit/HN for signal merging; a per-service official vs community diff page; email/webhook alert subscriptions; outage history timeline

Revenue

Monthly subscription tiered by number of monitored services; free tier capped at 3 services; team plan with multi-recipient alerts and SLA reports

Why now

Infrastructure is increasingly concentrated so single outages hit more people, while trust in official status pages is dropping; the scraping and merging stack is light enough for one developer to ship in weeks