Crowdcast incident
We're experiencing an issue with the platform
Crowdcast experienced a minor incident on February 13, 2026 affecting Recording Servers and Web App and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 13, 2026, 01:27 AM UTC
Status: Investigating The team is actively investigating an issue affecting our service. We'll update you as soon as we can. Affected components Streaming Servers (Partial outage) Web App (Partial outage) Recording Servers (Partial outage)
- identified Feb 13, 2026, 01:51 AM UTC
Status: Identified We’re hitting scale limits on our real-time chat and interaction services due to a large event. We’re increasing capacity now and will restore full service as quickly as possible. Affected components Streaming Servers (Partial outage) Web App (Partial outage) Recording Servers (Partial outage)
- monitoring Feb 13, 2026, 02:53 AM UTC
Status: Monitoring Services are coming back online, and we’re monitoring performance. Affected components Streaming Servers (Operational) Web App (Degraded performance) Recording Servers (Operational)
- resolved Feb 13, 2026, 03:10 AM UTC
Status: Resolved Impact: Some real-time updates were delayed for a portion of users. No data was lost. Timeline: Started at 7pm, peaked at 7:10pm, and resolved by 9:30pm ET. Cause: A sudden traffic spike from a high-scale event pushed past our autoscaling limits. What we did: Added capacity and tuned autoscaling. Now: Everything is stable and performing normally. What’s next: Stronger scaling safeguards, smarter rate limiting, and improved monitoring. Affected components Streaming Servers (Operational) Web App (Operational) Recording Servers (Operational)