We're experiencing an issue with the platform

Update timeline

1. investigating Mar 17, 2026, 05:17 PM UTC

   Status: Investigating The team is actively investigating an issue affecting our service. We'll update you as soon as we can. Affected components Recording Servers (Partial outage) Streaming Servers (Partial outage)

2. identified Mar 17, 2026, 05:33 PM UTC

   Status: Identified We’re currently experiencing a capacity shortage with our cloud provider (Hetzner). Hetzner has run out of available capacity in the region(s) we use, which is limiting our ability to provision additional resources and may impact scaling and recovery actions. • Current status: Investigating / Mitigating • Impact: Potential service degradation due to constrained scaling capacity (e.g., slower provisioning, delayed failover, or limited ability to add nodes). • What we’re doing: Actively working to secure additional capacity, including requesting more allocation from Hetzner and evaluating alternative capacity options. • Next update: We’ll share another update as soon as additional capacity is confirmed or our mitigation plan changes. Affected components Recording Servers (Partial outage) Streaming Servers (Partial outage)

3. identified Mar 17, 2026, 05:51 PM UTC

   Status: Identified We’ve identified an issue affecting our services where some hosts may experience difficulty going live. Our team is actively investigating, and we’ll share an update as soon as more information is available. Affected components Streaming Servers (Degraded performance) Recording Servers (Degraded performance)

4. identified Mar 17, 2026, 05:52 PM UTC

   Status: Identified Identified We’re currently experiencing a capacity shortage with our cloud provider (Hetzner). Hetzner has run out of available capacity in the region(s) we use, which is limiting our ability to provision additional resources and may impact scaling and recovery actions. • Current status: Investigating / Mitigating • Impact: Potential service degradation due to constrained scaling capacity (e.g., slower provisioning, delayed failover, or limited ability to add nodes). • What we’re doing: Actively working to secure additional capacity, including requesting more allocation from Hetzner and evaluating alternative capacity options. • Next update: We’ll share another update as soon as additional capacity is confirmed or our mitigation plan changes. Affected components Streaming Servers (Degraded performance) Recording Servers (Degraded performance)

5. monitoring Mar 17, 2026, 07:39 PM UTC

   Status: Monitoring We’ve secured additional compute capacity, and the platform is currently stable. We’re continuing to monitor key signals (capacity headroom, provisioning queues, and error rates) to ensure stability remains sustained. • Current status: Monitoring • Impact: No current impact; capacity constraints have been mitigated for now. • What we’re doing: Ongoing monitoring and readiness to scale further if demand or capacity conditions change. • Next update: We’ll provide another update if conditions change or once we confirm sustained stability. Affected components Streaming Servers (Operational) Recording Servers (Operational)

6. resolved Mar 17, 2026, 07:55 PM UTC

   Status: Resolved We’ve confirmed the scaled-up resources are holding under current load, and service remains stable. The immediate capacity constraints are resolved for now. • Current status: Resolved • Impact: No current impact; services are operating normally. • What we’re doing next: We’re investigating and designing a multi-cloud capacity strategy to reduce dependence on a single provider’s regional availability and enable provisioning across multiple cloud providers concurrently. Affected components Streaming Servers (Operational) Recording Servers (Operational)