Skip to main content
Riverside logo

Is Riverside Down?

No — Riverside is up

Reachable from all 8 checked regions

Average response time: 182ms

Last checked · checks run every 6 hours

Official status page: https://status.riverside.fm

Riverside uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
203ms
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 12: no data
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, 16 checks
Sep 23: 100.00% uptime, 31 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, 31 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
Sep 12 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
187ms
DNS 62ms TCP 9ms TLS 12ms TTFB 156ms
arn
136ms
DNS 49ms TCP 4ms TLS 6ms TTFB 123ms
nrt
144ms
DNS 82ms TCP 1ms TLS 4ms TTFB 139ms
ord
106ms
DNS 29ms TCP 1ms TLS 3ms TTFB 99ms
sin
165ms
DNS 86ms TCP 1ms TLS 6ms TTFB 142ms
sjc
155ms
DNS 70ms TCP 1ms TLS 4ms TTFB 145ms
syd
390ms
DNS 144ms TCP 1ms TLS 3ms TTFB 385ms
yyz
175ms
DNS 46ms TCP 12ms TLS 14ms TTFB 127ms

What Riverside does

Riverside is an online studio for recording podcasts and video interviews. A host invites guests into a browser studio, the session is recorded, and the files upload to Riverside for editing, clips and publishing. It also runs live streams and webinars. Because sessions are usually booked in advance with guests, an outage tends to arrive with people already waiting in the studio.

What an outage looks like

Hosts or guests cannot enter the studio, or it loads without camera or audio. Recordings finish but sit uploading or processing for a long time, or are not available afterward. The editor may fail to open, and live streams or webinars do not start. A guest who cannot join while the host can is a common shape, because the two are tracked as separate components.

What to do about it

Check status.riverside.fm, which lists Studio Access for Hosts and for Guests separately, along with Recording upload and processing, Recording accessibility, the Editor, Live streaming and Webinars, Payments and Mobile. If a recording is uploading, leave the studio tab open until it finishes. If studio access is down, reschedule with guests or record a backup with another tool so the conversation is not lost.

Is it down for everyone, or just you?

If this page says Riverside 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

Riverside outage FAQ

My recording is stuck processing. Is it lost?
Not necessarily. Riverside reports Recording upload and processing and Recording accessibility as their own rows, separate from the studio, so a delay there usually means the files are waiting rather than gone. Check those rows, wait for the incident to resolve, then look for the recording again before arranging to re-record anything.
Why can I get into the studio but my guest cannot?
Riverside tracks Studio Access for Hosts and Studio Access for Guests as separate components, so one can fail while the other works. Check the guest row on the status page. If it is green, the guest's browser permissions, extensions or network are the likely cause, and trying another browser or device is the quickest test.
Is riverside.fm the same as riverside.com?
Yes. riverside.fm now redirects to riverside.com, while the status page stays at status.riverside.fm. This page measures riverside.com, which is where the site lives today, so a failure measured here and an incident posted on the status page describe the same service and the same company.
Is Riverside down for everyone or just me?
Compare the status page with this page's measurements from several regions. If both show Riverside healthy, the likely causes are local: browser permissions for the camera and microphone, an extension, or your own upload speed. Failures seen from several regions at once point to Riverside itself.

How we measure this

  • We request Riverside'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 Riverside 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 Riverside 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