Skip to main content
Restream logo

Is Restream Down?

No — Restream is up
Restream's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 192 ms

Right now

The verdict is the worse of these two. How we decide

Restream's status page

status.restream.io · read

Operational
Restream's components, as its status page reports them
ComponentStatus
WebsiteOperational
Restream PlayerOperational
StudioOperational
AnalyticsOperational
ChatOperational
APIOperational
Streaming: AmericasOperational
Streaming: EuropeOperational
Streaming: Asia/PacificOperational
18 locations All operational

FlareWarden checks

restream.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
192 ms
Checked

By region

  • Ashburn reachable, 116 ms
  • Dallas reachable, 47 ms
  • Frankfurt reachable, 158 ms
  • Johannesburg reachable, 744 ms
  • Newark reachable, 166 ms
  • Paris reachable, 61 ms
  • Stockholm reachable, 200 ms
  • São Paulo reachable, 47 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Ashburn99 ms1 ms4 ms109 ms
Dallas35 ms1 ms3 ms43 ms
Frankfurt143 ms2 ms4 ms155 ms
Johannesburg296 ms0 ms3 ms473 ms
Newark146 ms2 ms7 ms160 ms
Paris43 ms3 ms5 ms57 ms
Stockholm176 ms1 ms5 ms196 ms
São Paulo30 ms1 ms6 ms43 ms
We check that restream.io loads, not every feature behind it. Test it yourself

History

Incidents Restream reported

from status.restream.io

We don't have Restream's incident history yet.

Restream website availability

Measured by FlareWarden · restream.io

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

Last 30 days

33-day clean streak
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, 32 checks
Oct 1: 100.00% uptime, 30 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: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 32 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 29 checks
Oct 18: 100.00% uptime, 32 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 24 checks
Sep 25 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of restream.io from multiple regions every 6 hours. Restream's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 33 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Restream does

Restream is a live video platform built around multistreaming: a creator or company goes live once and Restream sends the stream to several channels at the same time. It includes a browser Studio for producing streams, a chat that gathers messages from the connected channels, analytics, an API and the Restream Player. Outages usually land mid-broadcast, with an audience already watching.

What an outage looks like

The Studio will not load or drops guests, a stream starts but never appears on some or all destination channels, or it stutters and disconnects. Chat from the connected platforms stops arriving in one place, and analytics go blank. Streaming is tracked by region, so a broadcast from one region can fail while another creator elsewhere streams normally.

What to do about it

Check status.restream.io, which lists the Website, Restream Player, Studio, Analytics, Chat and API, and Streaming separately for the Americas, Europe and Asia/Pacific. Read the streaming row for the region you broadcast from. If Restream itself is down, go live directly on your most important channel and tell the audience on the others where to find you.

Is it down for everyone, or just you?

If this page says Restream 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 outage FAQ

My stream is live on some channels but not others. Is Restream down?
Not always. If Restream's Streaming rows are green, a single missing channel usually points to that platform or to its connection in your Restream account, which may need to be re-authorised. If the streaming row for your region shows an incident, the delivery problem is Restream's, and every destination can be affected.
Can I stream if the Restream Studio is down?
Often yes. The status page reports the Studio separately from Streaming, so a stream sent from your own encoding software can keep working while the browser Studio is unavailable. If the Streaming row is affected too, go live on your main channel directly and post links on the others.
Why is chat not showing in Restream?
Chat is its own component on the status page, so it can fail while the stream itself is fine. The broadcast is still reaching viewers even though their messages are not reaching you. Keep the native chat of your main channel open in another window until the row recovers.
Is Restream down for everyone or just me?
Compare the status page with this page's measurements from several regions. If both show Restream healthy, the likely causes are local: upload bandwidth, the encoder's connection settings, or an expired channel connection. Failures seen from several regions at once point to Restream itself.

How we measure this

  • We request Restream'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 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. 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 Restream 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 Restream 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. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Restream goes down

We check Restream 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
Free plan available No credit card required