Skip to main content
StreamYard logo

Is StreamYard Down?

No — StreamYard is up

Reachable from all 8 checked regions

Average response time: 406ms

Last checked · checks run every 6 hours

Official status page: https://status.streamyard.com

StreamYard uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
539ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 20 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

20-day clean streak
Sep 13: no data
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: 100.00% uptime, 24 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 30 checks
Oct 1: 100.00% uptime, 29 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: no data
Sep 13 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
370ms
DNS 20ms TCP 2ms TLS 9ms TTFB 319ms
arn
402ms
DNS 50ms TCP 1ms TLS 7ms TTFB 314ms
cdg
461ms
DNS 120ms TCP 2ms TLS 8ms TTFB 401ms
ord
298ms
DNS 58ms TCP 2ms TLS 9ms TTFB 280ms
sin
583ms
DNS 75ms TCP 1ms TLS 7ms TTFB 430ms
sjc
261ms
DNS 69ms TCP 2ms TLS 10ms TTFB 239ms
syd
596ms
DNS 8ms TCP 0ms TLS 7ms TTFB 310ms
yyz
284ms
DNS 46ms TCP 1ms TLS 7ms TTFB 270ms

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.

Test it yourself

Related services

Restream
Restream
Riverside
Riverside
T
Twitch
Zoom
Zoom

StreamYard outage FAQ

My guest cannot join the StreamYard studio. Is it down?
Check the Login, sign-up and guests group. Guest invitations are a separate row there, so guests can be locked out while the host's studio works. If that row is green, the cause is usually on the guest's side: blocked camera or microphone permissions, an unsupported browser, or a company network that filters video traffic.
Where is my recording after the outage?
Look in the Library once service returns. StreamYard reports Library, Cloud recordings and Local recordings as separate rows, so a recording problem can be limited to one of them. Check the relevant row, and if it shows an incident, contact StreamYard support about that session before recording it again.
Is it StreamYard or YouTube that is down?
If StreamYard's studio rows are green and the stream reaches every platform except one, the problem is almost certainly that platform or its connection in your StreamYard account. If the Webinars and On-Air row or the studio rows show an incident, StreamYard is the cause and every destination is affected.
Is StreamYard down for everyone or just me?
Compare the status page with this page's measurements from several regions. If both show StreamYard healthy, the likely causes are local: browser permissions, an extension, or limited upload bandwidth. Failures seen from several regions at once point to StreamYard itself.

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.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when StreamYard goes down

This page refreshes every 6 hours. 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
Free plan available No credit card required