Studycase
Status
Real component state from the LAUNCH-5 uptime workflow's own probes — not a marketing "all systems operational" banner. See the honesty note at the bottom for exactly how fresh this is.
Components
- Web (studycase-staging.vercel.app)Operational
- Gateway (/readyz)Operational
- ASR (demo tier)Operational
"ASR (demo tier)" is the synthetic demo-session websocket probe — it exercises the mock ASR pipeline through the gateway (there is no separately deployed ASR-only health endpoint today), so a failure here can mean either the ASR pipeline or the gateway it rides on.
Incident history
- ResolvedLAUNCH-5: uptime check failure #5
Opened 2026-07-08 21:33:59.000 UTC · resolved 2026-07-08 22:41:17.000 UTC · issue #5 (private repo — link resolves for repo collaborators)
- ResolvedLAUNCH-5: uptime check failure #4
Opened 2026-07-08 03:50:24.000 UTC · resolved 2026-07-08 06:23:54.000 UTC · issue #4 (private repo — link resolves for repo collaborators)
- ResolvedLAUNCH-5: uptime check failure #3
Opened 2026-07-07 11:25:38.000 UTC · resolved 2026-07-08 01:50:51.000 UTC · issue #3 (private repo — link resolves for repo collaborators)
- ResolvedLAUNCH-5: uptime check failure #2
Opened 2026-07-07 08:26:17.000 UTC · resolved 2026-07-07 08:28:18.000 UTC · issue #2 (private repo — link resolves for repo collaborators)
Acceptance record: issue #2 above is LAUNCH-5's own real induced-outage drill — opened, pinned, and closed automatically the same night this page was built (2026-07-07) — this is the "one test incident posted and resolved" this page's ticket (LAUNCH-10) required, not a fabricated example. Issue #3 is a real, currently-open incident from the same workflow, shown here because a status page that hid it to look better would be the exact fabrication this project refuses to ship.
How this data is sourced (read before trusting the banner)
Component states and incident history are generated by the LAUNCH-5 GitHub Actions uptime workflow (.github/workflows/launch-5-uptime.yml) from real probes run on a */5 schedule, and committed to this file by CI. The page you're viewing reflects this data as of studycase-staging's last deploy: deploys here are manual/prebuilt, not git-triggered (docs/LAUNCH-2-STAGING.md), so generated_at can lag the live workflow — the automation itself is real either way; the workflow's own run history is the ground truth.
Data generated at 2026-07-08 23:51:00.000 UTC. Source run: https://github.com/lawlessz/studycase/actions/runs/28983748448 (private repo — resolves for repo collaborators). Runbook: docs/LAUNCH-5-RUNBOOK.md.