tag:subhero.instatus.com,2005:/history SubHero Status - Incident history 2026-07-02T06:50:58.934+00:00 SubHero tag:subhero.instatus.com,2005:Incident/cmr35bcij001hr1pi1qm0yxvg 2026-07-02T06:50:58.934+00:00 2026-07-02T07:00:37.933+00:00 Website is back up Type: Incident

Affected Components: Website

Jul 2, 07:00:37 GMT+0
Resolved - Website is back up. This incident was automatically resolved by Instatus monitoring..

Jul 2, 06:51:00 GMT+0
Investigating - Website is down at the moment. This incident was automatically created by Instatus monitoring..

]]> tag:subhero.instatus.com,2005:Incident/cmpd79zmy00lto315uytvexu5 2026-05-19T22:24:12.202+00:00 2026-05-20T01:44:17.928+00:00 API is back up Type: Incident

Affected Components: API

May 20, 01:44:17 GMT+0
Resolved - API is back up. This incident was automatically resolved by Instatus monitoring..

May 20, 02:49:18 GMT+0
Postmortem - **Summary** Between May 20, 2026 06:24 UTC and 09:44 UTC (3h 20m), SubHero's API and background workers were unavailable. Translation, transcription, and any feature that talks to our backend returned errors. The Cloudflare-hosted marketing site, in-browser subtitle editor tools, and Supabase auth were unaffected. **Root cause** Our backend (FastAPI + Celery workers) is hosted on Railway, which runs on Google Cloud Platform. During this window, GCP suspended Railway's account, taking Railway's entire infrastructure offline. Every service hosted on Railway — ours included — went down with it. This was an upstream provider issue outside our control. **Resolution** Service was restored automatically once Railway's account was reinstated and their platform recovered. No data was lost; in-flight tasks resumed when workers came back online. Apologies to everyone affected. — SubHero team.

May 19, 22:24:12 GMT+0
Investigating - API is down at the moment. This incident was automatically created by Instatus monitoring..

]]>