The Monitoring page is your server's health dashboard: a single health score that tells you at a glance whether things are fine, a performance timeline of CPU, memory, disk, and network, and a crash history that records every time the server went down and why. It's a premium feature — free servers see the score as an upgrade prompt — but the charts and crash reports are the fastest way to answer "is my server actually healthy?" Open Monitoring from your server menu.
| At a glance | |
|---|---|
| You need | A premium server (free servers get an upgrade prompt for the health score) |
| Plan | Premium |
| Time | Five minutes to read your dashboard |
The health score
At the top sits a Server Health banner that grades your server out of the things that actually matter. Each component gets its own score, and the banner rolls them into one verdict: All systems healthy, Needs attention, or Critical issues, calling out which parts are struggling.
| Component | What it watches |
|---|---|
| CPU | How hard the processor is working over time |
| Memory | RAM headroom against your limit |
| Stability | How often the server has crashed |
| Uptime | How consistently it stays running |
| Players | Player activity (Minecraft servers only) |
On a non-Minecraft server the Players component simply isn't shown. Each component is colour-graded — healthy, needs attention, or critical — so a red Memory or Stability tile points you straight at the problem.
🎯 Good to know: On a free server the banner appears but the live score is replaced with an Upgrade prompt. The rest of your server works exactly the same — monitoring is about insight, not about keeping the server running.
The performance timeline
Below the score is a chart of your server over time. Switch between CPU, Memory, Disk, and Network, or view them combined with per-line toggles. Pick a window — 15 minutes, 1 hour, 6 hours, 24 hours, 3 days, or 7 days — and the chart auto-refreshes about every two minutes, so you can leave it open and watch load in near-real-time.
This is where you catch slow problems the console won't show you: a memory line that keeps climbing until a restart (a leak), CPU pinned at 100% during peak hours (you've outgrown the plan or a plugin is heavy), or a disk that's quietly filling up.
Crash history — the "why did it go down?" log
The crash section is the part you'll come back to. It records every time the server stopped and turns each event into a readable report.
- Filter by All, Crashes only, or Clean exits (a script that finished on purpose is a clean exit, not a crash).
- Choose a period: 24 hours, 3 days, 7 days, or 30 days.
- Summary cards up top: Total Crashes, Last 24h, OOM kills, and Average Uptime.
Each crash card tells you:
| Shows | Meaning |
|---|---|
| Type badge | OOM kill (ran out of memory), Clean exit (stopped normally), or Error exit (crashed with an error code) |
| Restart badge | Whether the server was automatically restarted afterwards |
| Uptime | How long it had been running before it fell over |
| Memory | RAM used vs your limit at the moment of the crash |
| CPU | Processor load at the crash |
Open Details for the exit code, previous state, and any error message, or Logs to read the console output from around the crash — with a Download button to save it.
💡 Tip: A run of OOM kill badges means the same thing every time: your server needs more RAM than it has. Work through Out of memory — the fix is usually trimming what you run or moving up a plan, not a code bug.
Reading it: three common patterns
- Memory climbs, then an OOM kill, then a restart, on repeat — a memory leak or an under-sized plan. The timeline shows the climb; the crash log confirms the OOM.
- Stability red, lots of Error exits — the app is crashing on an error. Open a crash's Logs and read from the top; pair with My app won't start.
- CPU pinned during peak, everything else fine — you're CPU-bound at busy times. For Minecraft, profile with spark; otherwise it's a heavier-plan conversation.
Get told without watching
You don't have to keep this page open. If crash notifications aren't on, the page nudges you to enable them in your account settings — turn them on and Falix emails you when this server crashes (you set the preference per server on the Settings page). Pair that with an auto-restart schedule and a crash becomes a blip instead of an outage.
Troubleshooting
- The health score shows an Upgrade button — that server is on the free plan; the live score is a premium feature.
- The chart is empty — the server hasn't run long enough to gather data, or was offline for the whole window. Pick a longer range or let it run.
- A "crash" was really me stopping it — filter to Crashes only; clean exits (including a script that finished) aren't failures.
- The page won't open for a teammate — it needs the monitoring/console permission; grant it on Sub-users.