Observed Signal · Jul 18, 2026 · Product Launch · Source: DEV Community · Impact: 2/5 · Sentiment: Neutral
OutageDeck: Lessons from Tracking 96 Providers
The author built OutageDeck, a service that aggregates official status feeds from 96 cloud and SaaS providers. The project revealed there is no standard status format (most use Statuspage-style JSON but many are bespoke), provider timestamps can be stale so uptime must be measured by the poller's check time, and some official endpoints are unusable or overly granular. The backend is intentionally minimal — a Next.js app with Postgres and overlapping schedulers — costing about $55/month. OutageDeck exposes a public JSON API, embeddable badges, RSS per provider, and email alerts, while being open about data gaps and limitations of upstream feeds.
Consolidates official provider status and documents operational pitfalls (nonstandard formats, stale timestamps, encoding issues) that matter for reliability engineering; useful for operations but not industry-shifting.
Track Slack Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- OutageDeck reads official status sources for 96 cloud and SaaS providers and aggregates them into one place.
- Around 89 of the 96 providers expose a Statuspage-style summary.json and incidents.json that can be parsed by a single adapter.
- Some providers publish bespoke formats (Google, Slack, Heroku) or unusual encodings (AWS event feed in UTF-16 with a byte-order mark).
- Provider-reported timestamps often lag (sometimes by days), so the author stamps each observation with the poller's check time and records gaps over 30 minutes as 'no data'.
- The backend is a single Next.js app with a Postgres database, overlapping 10- and 30-minute schedulers, and runs for about $55/month.
Connected Companies & Entities
9 Entities mapped“Your Slack won't load. ... You open Slack's status page and it's green....”
“Google publishes an incidents.json in its own format (shared across Cloud, Workspace, and Firebase)....”
“Azure only offers RSS....”
“AWS ships an event feed encoded in UTF-16 with a byte-order mark, which silently breaks any parser that assumes UTF-8....”
“Atlassian Statuspage is the closest thing to a common language....”
“…so Notion and Linear parse with the exact same code....”
“Salesforce's status API models nearly 3,900 separate instances, so 'is Salesforce up?' depends entirely on which pod your org sits on....”
“…so Notion and Linear parse with the exact same code....”
“Stripe's legacy status JSON has been effectively frozen since 2024; it will cheerfully report that everything is fine, forever....”
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Monitor Third‑Party Outages Using Two Signals
The article explains a two-signal approach to detect and triage third‑party provider outages: (1) the provider's official status feed and (2) synthetic checks that emulate user requests. The author, Kerolos, founder of OutageDeck, describes the strengths and blind spots of each signal, how to correlate them for more accurate incident triage, example curl commands for OutageDeck's keyless API and synthetic probes, and a practical alerting policy mapping signal combinations to on‑call actions. The post also recommends recording timestamps, regions, response codes, and incident identifiers to improve post‑incident reviews.
Open-source self-hosted status page and monitor
BetterStatusPage is an open-source, self-hosted status page and monitoring platform announced by Bartlomiej Komendarczuk. It is an MVP that runs as a single Node.js 22 process with SQLite persistence and is deployable via Docker Compose. The project supports HTTP/HTTPS checks, ICMP ping, TCP port checks, DNS monitoring, SQL Server queries, and passive webhook monitoring. Notifications can be sent via email, webhooks, Discord, Slack, and Microsoft Teams with automatic retries. The public status page includes a drag-and-drop grid editor, incident management, maintenance windows, monitor dependencies, Server-Sent Events for real-time updates, and an AES-256-GCM encrypted secrets vault. The code is hosted on GitHub under an MIT license and the author is seeking testers and feedback. Publication date: 2026-07-12.
Observability Reveals Why Sites 'Go Down'
The author built a fake exam-results site as a hackathon project to intentionally inject outages and observe them with the open-source observability tool SigNoz. By triggering four failure modes—database latency, cache (Redis) failure, a bad deploy that throws 500s, and traffic spikes—the author demonstrates that “server down” is not a single failure but distinct fingerprints visible in traces and metrics (fat slow spans, flatlined cache-hit rates, error-rate cliffs, rising RPS with latency). The project includes a Mission Control panel with toggles to inject incidents and a load generator, plus instructions to install SigNoz via a Foundry installer. The piece argues that pre-wired telemetry and alerts produce fast, specific diagnoses during incidents rather than vague “try later” responses.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.