A terminal that's switched on tells you almost nothing. It can sit there, green light showing, autotrading enabled, broker connected — and not fire a single trade because the EA has silently stopped. System Health is the page that separates a running terminal from a working one, across every account at once.
The three cards
At the top, three summary cards read the whole fleet in one look:
- Fleet uptime — your 30-day average across every terminal, one percentage.
- Online now — how many terminals are reporting in this moment.
- Incidents — the count of problems flagged in the last 30 days.
Together they answer "is the fleet healthy?" before you look at any single account.
The terminals table
Below the cards, one row per terminal:
- Status — OK, Review or Attention. Sort by this and the problems rise to the top.
- Account — which account the terminal is signed into.
- Terminal — online, or not.
- Autotrading — Enabled or Disabled. Disabled is flagged Attention, because a terminal with autotrading off will never trade, however healthy the rest of the row looks.
- Broker link — Connected, or not.
- Heartbeat — how long since the terminal last reported, e.g. 6s ago.
- Uptime — a 30-day sparkline and percentage, so you see the shape of the downtime, not only the total.
- Strategies — what the EAs are doing, e.g. "1 active" or "1 quiet".
Running isn't the same as working
The trap is assuming a live terminal means a live strategy. It doesn't. A terminal can be online, autotrading on, broker connected — and the EA still not firing, because it has crashed, been removed from the chart, or gone quiet waiting for a signal a bug means it will never take.
System Health is built to catch the failures that make no noise:
- a terminal that's dropped offline,
- autotrading switched off,
- the broker link disconnected,
- a strategy that's gone quiet when it should be trading.
Any of these can cost you days of missed trades while your balance sits perfectly still and nothing on the surface looks wrong.
How uptime is measured
Uptime is calculated from the gap between heartbeats, not from what the terminal claims about itself. That matters more than it first sounds.
An offline terminal can't report its own downtime. A machine that fell over at 2am and came back at 6am would, if you asked it, say nothing about the four hours it was gone — and silence looks like 100%. Karnek measures the gap between heartbeats instead: the time between the last one and the next is the outage, whether the terminal was awake to admit it or not. So the percentage counts the downtime you actually had.
The Karnek note
Karnek watches your terminals read-only, through the heartbeat each one sends. It can tell you a terminal is offline or a strategy has gone quiet — but it can't reach in and restart anything, and it can never place a trade. The page tells you where to look; the fix stays in your hands.
Written and reviewed by the Karnek Research team. Last updated August 2026.
Educational content only - not financial advice. Past performance does not predict future results. Trading carries significant risk.