SubHero Status - Incident history https://subhero.instatus.com SubHero Thu, 2 Jul 2026 06:50:58 +0000 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. Type: Incident

Affected Components:

<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>07:00:37</var> GMT+0</small><br><strong>Resolved</strong> - Website is back up. This incident was automatically resolved by Instatus monitoring..</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>06:51:00</var> GMT+0</small><br><strong>Investigating</strong> - Website is down at the moment. This incident was automatically created by Instatus monitoring..</p> ]]> Thu, 2 Jul 2026 06:50:58 +0000 https://subhero.instatus.com/incident/cmr35bcij001hr1pi1qm0yxvg https://subhero.instatus.com/incident/cmr35bcij001hr1pi1qm0yxvg 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. Type: Incident

Affected Components:

<p><small>May <var data-var='date'> 20</var>, <var data-var='time'>01:44:17</var> GMT+0</small><br><strong>Resolved</strong> - API is back up. This incident was automatically resolved by Instatus monitoring..</p> <p><small>May <var data-var='date'> 20</var>, <var data-var='time'>02:49:18</var> GMT+0</small><br><strong>Postmortem</strong> - **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.</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>22:24:12</var> GMT+0</small><br><strong>Investigating</strong> - API is down at the moment. This incident was automatically created by Instatus monitoring..</p> ]]> Tue, 19 May 2026 22:24:12 +0000 https://subhero.instatus.com/incident/cmpd79zmy00lto315uytvexu5 https://subhero.instatus.com/incident/cmpd79zmy00lto315uytvexu5