Is StreamYard Down?
- StreamYard's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 456 ms
Right now
The verdict is the worse of these two. How we decide
StreamYard's status page
status.streamyard.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Studio settings and features | Operational |
| Dashboard settings and features | Operational |
| Webinars and On-Air | Operational |
| Library | Operational |
| Cloud recordings | Operational |
| Local recordings | Operational |
| Login and sign-up | Operational |
| Guest invitations | Operational |
| Other issues | Operational |
FlareWarden checks
streamyard.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 456 ms
- Checked
By region
- Ashburn reachable, 499 ms
- Chicago reachable, 292 ms
- Johannesburg reachable, 653 ms
- London reachable, 361 ms
- Los Angeles reachable, 348 ms
- San Jose reachable, 373 ms
- Singapore reachable, 676 ms
- Tokyo reachable, 446 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 56 ms | 1 ms | 9 ms | 484 ms |
| Chicago | 38 ms | 2 ms | 6 ms | 235 ms |
| Johannesburg | 180 ms | 2 ms | 10 ms | 588 ms |
| London | 45 ms | 2 ms | 8 ms | 328 ms |
| Los Angeles | 153 ms | 2 ms | 7 ms | 326 ms |
| San Jose | 202 ms | 2 ms | 8 ms | 352 ms |
| Singapore | 141 ms | 1 ms | 18 ms | 522 ms |
| Tokyo | 74 ms | 1 ms | 8 ms | 386 ms |
History
Incidents StreamYard reported
Since Oct 22, 2 days · from status.streamyard.com
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
StreamYard website availability
Measured by FlareWarden · streamyard.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 526ms
Last 30 days
32-day clean streakMeasured by FlareWarden's own checks of streamyard.com from multiple regions every 6 hours. StreamYard's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 32 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What StreamYard does
StreamYard is a live streaming and recording studio that runs in the browser. Hosts bring guests on screen, add branding, and stream live to platforms such as YouTube and Facebook or record for later, and it also runs webinars and On-Air events. Recordings are kept in a cloud library. Because it is used for scheduled broadcasts, an outage usually meets an audience that is already waiting.
What an outage looks like
The studio will not open, guests cannot join through their invitation link, or going live fails and the stream never starts. Broadcasts may cut out on the destination platform. Cloud recordings can be missing from the library after a session, and local recordings may fail to save. Sign-in and sign-up can fail on their own while studio sessions already in progress continue.
What to do about it
Check status.streamyard.com, which groups its rows into Studio, On-Air and Dashboard, Library and recordings, and Login, sign-up and guests. If a broadcast is due and the studio is down, go live on your main platform with its own tools and tell viewers where to find you. After recovery, look in the Library for the session before deciding to record it again.
Is it down for everyone, or just you?
If this page says StreamYard is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
StreamYard outage FAQ
My guest cannot join the StreamYard studio. Is it down?
Where is my recording after the outage?
Is it StreamYard or YouTube that is down?
Is StreamYard down for everyone or just me?
How we measure this
- We request StreamYard's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where StreamYard publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of StreamYard itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when StreamYard goes down
We check StreamYard every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring