Crowdcast Outage History
11 incidents recorded over the last 365 days, 11 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Crowdcast Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 4, 2026 | Live streaming disruptionOn November 4, between approximately **15:02 and 15:13 UTC (10:02–10:13 a.m. EST),** a network outage at our infrastructure provider, Hetzner, disrupted Crowdcast’s live streaming service for approximately 11… | -3 min | Resolved |
| Aug 13, 2026 | We're experiencing an issue with the Crowdcast mobile app.We’ve identified the issue and have deployed a fix. Event functionality on the mobile app is now working again. Thank you for your patience and understanding. | 14h 24m | Resolved |
| Aug 3, 2026 | We experienced an issue with the platformCrowdcast experienced an issue where hosts appeared live and recording, but attendees could not view the broadcast. Engineers quickly identified the cause as an overloaded database. To restore service, they switched… | -173 min | Resolved |
| May 6, 2026 | We're experiencing an issue with the platformWe identified and resolved an issue that prevented events from loading correctly on the initial page load. As a result, some users needed to refresh the page before the livestream would appear. This has now been fixed… | 1h 35m | Resolved |
| Apr 29, 2026 | Increased buffering issueOur updates remain stable, and we are continuing to implement additional improvements to help ensure that issues at Cloudflare have a reduced impact on our services. | 24h 9m | Resolved |
| Apr 23, 2026 | Issues Going LiveWe experienced an issue that temporarily prevented some sessions from going live due to a brief compute disruption within our recording infrastructure. The problem was limited in duration, and we are actively… | -58 min | Resolved |
| Mar 17, 2026 | We're experiencing an issue with the platformWe’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… | 2h 37m | Resolved |
| Mar 11, 2026 | Live streaming playback disruptionAt **8:54 AM ET**, we experienced a **9-minute service disruption** in our livestreaming infrastructure that impacted **real-time audience playback**. During this window, viewers may have seen interruptions or inability… | -87 min | Resolved |
| Mar 5, 2026 | We're experiencing an issue with the platform**All systems remain stable.** We have identified the root cause of the cascading issues that occurred under high load and are deploying an update today to prevent this from happening again. Thank you for your continued… | 4h 3m | Resolved |
| Feb 13, 2026 | We're experiencing an issue with the platform**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… | 1h 43m | Resolved |
| Nov 18, 2025 | We're experiencing an issue with the platformThings look stable now—Crowdcast is back to normal. We’ll keep monitoring to make sure we’re fully in the clear. | 1h 58m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Crowdcast incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Crowdcast Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Crowdcast acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Crowdcast outage in this window ran 1d, against a mean recovery of 7h 13m. If you depend on Crowdcast in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.