How to Check Your Livestream’s Complete Health Status & Bitrate on StreamKite

“Is it live?” is the wrong question once you’re running 24/7 pre-recorded streams. A stream can technically be live and still be in trouble — a bitrate quietly dropping, a slot one crash away from going dark, a platform about to flag the feed for being unstable. Checking real health means looking past the green dot and into the numbers underneath it. StreamKite puts all of that in one place, and this walkthrough covers exactly where to look and what each reading actually means.

Where to find it: the Health tab

Open the Power panel (the lightning-bolt icon on your dashboard) and click the heartbeat icon — that’s the Health tab. This is the one screen built specifically to answer “how are my streams doing right now,” as opposed to historical totals, which live under Analytics instead.

Live count and stability — the two headline numbers

At the top of the Health tab you’ll see two figures side by side:

• Live now — a simple count of how many of your slots are currently streaming. Colored green when it’s above zero, muted gray when nothing’s running.
• Stability — a percentage worked out from how many of your total slots are currently crash-free. If you’ve got ten slots and one is crashed, stability sits at 90%. It’s color-coded too: green at 90% and above, yellow between 70–89%, red below that. This single number is often the fastest way to know if something across your whole setup needs attention before you even look at individual streams.

A stability score that’s dropping over time — even slowly — is usually worth investigating before it becomes an outage. It’s the kind of thing that’s easy to ignore day-to-day but obvious once you’re specifically looking for it, which is exactly why it’s surfaced as its own number instead of buried in a status list.

Reading live bitrate correctly

Below the headline numbers, every currently-running slot gets its own bitrate card showing a live kbps reading with a small progress bar underneath. The color tells you what to do with the number:

• Green (roughly 3200+ kbps) — healthy. No action needed.
• Yellow (roughly 2900–3199 kbps) — borderline. Not broken, but worth keeping an eye on, especially if it’s trending downward.
• Red (below ~2900 kbps) — this is where platforms start degrading stream quality or flagging instability. If a slot is consistently sitting in red, check the source file’s bitrate and re-export it closer to the 3000–4000 kbps range that most platforms expect.

Bitrate is one of the clearest early warning signs you have. A platform doesn’t usually kill a stream outright the moment bitrate dips — it degrades the viewer’s experience first, which means by the time someone complains about quality, the bitrate card has probably been sitting in yellow or red for a while already.

The slot status overview — every stream, one glance

Scroll down and you’ll find a full list of every slot with a colored status dot next to it:

• Green dot, LIVE — streaming normally.
• Red dot, CRASH — the stream has stopped unexpectedly and needs attention.
• Gray dot, OFF — intentionally stopped, nothing wrong.

This is the fastest way to scan a large number of slots without opening your full streams grid — especially useful if you’re managing streams across multiple niches or clients and just need a quick “is anything broken” check.

Checking uptime on an individual stream

If you want to know how long a specific stream has been continuously live in its current run, that’s shown directly on the slot card next to its LIVE badge, updating in real time. You don’t need to dig through the Health tab for this — it’s visible the moment you glance at the stream itself.

What a crash actually looks like, and what to do about it

When a slot crashes, three things happen at once: its dot turns red in the slot overview, your stability percentage drops slightly to reflect it, and — if it’s set up — an alert fires in the Alerts tab with a timestamp. From there, you can restart it manually with a click, or set up auto-recovery in the Power panel’s Automation tab so it retries on its own a set number of times before giving up and asking for manual attention.

A practical health-check routine

1. Open the Health tab and check the stability percentage first — this tells you in one number whether anything’s currently wrong.
2. If it’s below 100%, scroll to the slot overview and find the crashed one(s).
3. For live streams, scan the bitrate cards for anything sitting in yellow or red.
4. Check the Alerts tab for context on when and how often a problem has been recurring.

Done regularly, this takes less than a minute and catches most problems well before a viewer would notice something’s off.

Frequently asked questions

Why does my bitrate fluctuate slightly even when nothing’s wrong?
Small fluctuation is completely normal for RTMP streaming — network conditions vary slightly moment to moment. What matters is the general range it sits in, not tiny second-to-second movement.

Does a yellow bitrate reading mean my stream will get flagged?
Not immediately — yellow is a “keep an eye on it” zone, not a failure state. Red sustained over time is the one worth acting on.

Can I see bitrate for a stream that isn’t currently live?
No — bitrate is a live reading, so it only shows for slots that are actively streaming. Stopped or crashed slots show a status only.

Does the stability score include addon slots?
Yes, addon slots are counted in the same stability calculation and status overview as your main plan slots — there’s no separate health view for them.

The short version

Health status is more than a green dot next to your stream name. Between the stability score, live bitrate readings, and the full slot status overview, StreamKite gives you enough detail to catch a struggling stream before it becomes a dead one — and it’s all sitting in one tab, no digging required.