Every status page, one wall. Live status, 90-day history and incident timelines for the AI, cloud and SaaS services your product depends on, with your own stack, region-aware relevance, and honest data: a source Statuswall cannot read is shown as unverified, never as healthy.
Live: https://statuswall.vercel.app (560+ services)
This repository is a showcase of Statuswall. It runs end to end with a demo catalog of 19 well-known services read through the two generic readers (Atlassian Statuspage and RSS/Atom). The full service catalog, the vendor-specific readers, alert delivery, CVE matching and the curated incident write-ups run only in the hosted service and are not included.
- The site (Next.js App Router, React, Tailwind): home wall, service directory with search and filters, per-service pages with 90-day history, incident pages, outages, security and CVE views, light and dark themes, built for keyboard and screen-reader use.
- Status semantics that the UI is built on:
src/lib/freshness.ts: freshness from the last successful read; stale is not healthy.src/lib/mix.ts: headline counts in disjoint buckets that always add up.src/lib/regions.ts: conservative incident scope (structured vendor fields first, explicit region codes in titles as an inferred fallback, unknown otherwise; never assumed global).src/lib/match.ts: is a vendor incident relevant to your stack and regions? Returns relevant / scope unknown / out of scope / planned, each with a plain reason.src/lib/uptime.ts: "reported uptime" from published incidents, with coverage shown.src/lib/incident-events.ts: changes Statuswall observes, kept apart from vendor times.
- Your stack without an account: saved in the browser and the link
(
?stack=aws:us-east-1,openai), with export/import, undo and region picking. - Two readers (
src/adapters/statuspage.ts,src/adapters/feed.ts) and theAdapterinterface (src/lib/types.ts) for adding more. - Tests: 68 unit tests (Vitest) for the rules above, plus a route smoke test.
npm install
cp .env.example .env.local # set DATABASE_URL to any Postgres
npm run dev # http://localhost:3000
npm run ingest -- --history # in a second terminal: read the demo servicesThe schema creates itself on first use. Checks:
npm run typecheck && npm run lint && npm test && npm run build
npm run smoke # routes and API contract against the running serverImplement fetchCurrent(v) and fetchHistory(v) from Adapter in src/lib/types.ts,
register it in src/adapters/index.ts, and add services that use it to
src/vendors/catalog.generated.json. Rules the product depends on: map the vendor's own words to
severity, throw on anything you cannot read (never return "operational" for unreadable data), and
never invent start, end or region.
docs/ holds the data contracts (severity, freshness, scope, matching, timestamps), the
decisions log and the test matrix.
Statuswall shows what each vendor publishes on its own public status page. It is independent, not affiliated with any company listed, and not a measure of anyone's actual availability.