Your home dashboard

The home dashboard is your command center: before the stream it guides you with the Your first stream checklist, during the stream it tells you whether everything is up — and where the chain breaks if something fails — and afterwards it keeps the history of what you streamed.

The broadcast chain

At the top sits the Broadcast chain, four links that follow your stream end to end:

Link	What it checks
Signal	Your encoder is reaching the stream key (with Cloud OBS, the one whose scene is on air or, if none, the Cloud OBS key)
Reading	Something is reading that signal (your Cloud OBS or your own OBS)
OBS	Your Cloud OBS is streaming, and not the no-signal scene
Destination	What it streams reaches an output channel you set up

Each link lights up while it’s active. If something breaks mid-stream, no guessing needed: the first dark link after a lit one is where the chain snaps, and it links straight to the guide for that exact step (for example My feed isn’t arriving or the playback URL). If your signal is reaching another key, or your Cloud OBS is streaming the no-signal scene, the flagged link tells you so.

With your Cloud OBS off, the chain has a Turn on button (or Turn it back on if it was released), so you don’t have to go looking for the server. Right below sit Live signal and your Cloud OBS, with the On-air scene and the Start stream or Stop stream button.

Your signal health

In Live signal, next to your Current bitrate, SRT and SRTLA keys show two more numbers: RTT (latency) and packet loss, with a traffic light:

Color	What it means
Green — Stable signal	Loss under 1% and RTT under 150 ms
Amber	One of the two is creeping up. Keep an eye on it
Red	Loss at 5% or more, or RTT at 400 ms or more. Your image is feeling it

When it’s red, don’t raise the bitrate: lower it and follow The bitrate keeps bouncing or the picture stutters.

When your signal isn’t arriving

With no signal, the Live signal card doesn’t always say the same thing: it tells you what happened, because ending it yourself, a drop, nothing arriving and arriving-but-rejected are not the same.

What you see	What happened	What to do
Ended · Broadcast ended	Your app closed the broadcast: either you stopped it or it closed on its own (from here we can’t always tell)	If you didn’t stop it yourself, start the broadcast again
Your signal dropped	Your signal stopped arriving without your app closing the broadcast. It’s almost always coverage or your phone’s network	If you’re still live, your app should reconnect on its own; if not, start the broadcast again. With SRTLA, use at least two connections
Your signal stopped	It stopped arriving and we have no data on how	If you didn’t stop it yourself, check your app’s connection
Rejected · Your stream key does not match	A broadcast reaches us with a stream key that is almost, but not exactly, yours, so we reject it	Copy the publish URL again (or scan the QR code) and paste it into your app without editing it
Rejected · You are using an inactive stream key	Your app is still broadcasting with a stream key that is no longer active	Copy the publish URL of the key on the card and paste it into your app
Rejected · Your subscription is not active	The signal arrives, but that key’s subscription is not active	Click Go to Billing
No signal yet	Nothing is reaching us with your stream key	Check the publish URL and the protocol: My feed isn’t arriving

What you’ve already achieved doesn’t get unticked: if you stop broadcasting, the Your first stream checklist keeps the steps you’d already completed.

Failover, in plain sight

If you have a failover channel, its card shows on the dashboard with its live status. During a drop you’ll see the grace window counting down (Offline screen up · x min of grace left) and when the last splice happened. Every state is explained in Grace window and states.

Your history

Once you’ve streamed at least once, the dashboard shows Your last stream (duration, average bitrate, quality, drops, how many automatic scene switching covered, and whether you ended it, Ended … ago, or it dropped, Dropped … ago; what each figure means: Your stream recap) and four monthly counters: Hours streamed, Data uploaded, Streams and Drops. The full history of each key, with its latest streams, lives in that key’s detail page under Stream history.

Note

A coverage blip of under a minute doesn’t split your stream in two: it counts as one drop inside the same stream. If you stay offline for a good while, the next connection opens a new stream. And if you stop it yourself, the stream ends there, even if you go live again right away: that isn’t a drop.

Bell notifications

The dashboard bell warns you when your signal drops mid-stream and doesn’t come back within a minute (never when you stop it yourself), when a broadcast reaches us with your stream key and we reject it (key copied wrong, inactive, or without an active subscription), and when failover puts up your offline screen. It also brings the good news: your first broadcast, only once, and the recap of every stream of at least 5 minutes. Every signal alert comes with What to check, which opens the guide for that case. Together with the Cloud OBS inactivity warning, those are the alerts worth never ignoring while live. What each one means: Index of dashboard messages.

Your Cloud OBS notices come with buttons too: Keep it on before it switches off, and Turn on if it’s stopped or released, without leaving the bell (It turns off on its own). The bell shows your most recent notices; See all opens Notifications, with your whole history: every notice in full, with its date and its buttons, and Show older to go further back.

Language

The language button in the top bar, near the bell, changes the dashboard’s language (Español, English or Français). We save it to your account, so it’s also the language of your emails, your bell notifications, the sign-in screen and your Cloud OBS overlays. If you change it, those overlays switch right away, even mid-stream.

Next step

• Your first stream: the dashboard checklist, step by step.
• My feed isn’t arriving: when the first link won’t light up.