StreamYard Outage History
2 incidents recorded over the last 365 days, 2 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 StreamYard Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| May 11, 2026 | Studio Access and Going Live OutageBetween 22:27 UTC and 23:29 UTC, StreamYard experienced an outage that prevented users from entering their studio and/or going live. The issue was caused by limited machine availability from the cloud provider we rely… | 0 min | Resolved |
| May 10, 2026 | Studio Access and Going Live OutageBetween 13:41 UTC and 19:26 UTC, StreamYard experienced an outage that prevented users from entering their studio and/or going live. The issue was caused by limited machine availability from the cloud provider we rely… | 0 min | 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 StreamYard 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 StreamYard 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 StreamYard 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 StreamYard outage in this window ran 0 min, against a mean recovery of 0 min. If you depend on StreamYard 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.