How to Check 3CX Status: Server, Services, Trunks & Live Calls

When someone asks "is 3CX down?" they usually mean one of five very different things. Sorting out which one saves hours of guesswork. This guide walks through each layer of 3CX status you can check — from the hosted service page all the way down to a single stuck call — and shows what the built-in tools cover well and where operators typically need more.

1. Is the hosted 3CX service itself up?

If your PBX is 3CX-hosted (StartUP or a 3CX-managed instance), check the official 3CX status page first:

• status.3cx.com — component-level status for the 3CX website, licensing, StartUP hosting, SBC, push service and update servers.

If that page shows a red or amber incident, the problem isn't your server — wait for the incident to clear and don't restart anything on your end.

2. Is your own 3CX server reachable?

For self-hosted PBXs (Debian or Windows), the fastest check is:

1. Open the 3CX Management Console URL from a browser outside your office network (or from a phone on mobile data).
2. If the console loads and you can log in → the PBX process, the web server and your firewall/NAT are all healthy.
3. If it times out → check the server itself (VM up? disk full? CPU pinned?) before touching 3CX.

3. Are the 3CX services running?

3CX runs as a set of OS services. When "3CX is down" really means "one service crashed," these are the checks:

On Debian (recommended):

sudo systemctl status 3CXPhoneSystem
sudo systemctl status nginx
journalctl -u 3CXPhoneSystem --since "1 hour ago"

On Windows: Open services.msc and confirm every service prefixed with 3CX is Running. The critical ones are 3CXPhoneSystem, 3CX Media Server, 3CX Nginx Server and 3CX Queue Manager.

If a service is stopped, start it and re-check the console. If it stops again within minutes, the fix is in the logs — not another restart.

4. Are your SIP trunks registered?

A perfectly healthy PBX with a de-registered trunk still can't make or receive external calls. In the 3CX Management Console:

• SIP Trunks → each trunk row shows a green/amber/red status dot.
• Red = registration failed (wrong credentials, IP not whitelisted with the carrier, or the carrier itself is down).
• Amber = registered but with warnings (e.g. no outbound rule bound).

Also worth checking: Activity Log for repeated SIP/2.0 403 or 408 responses from the carrier — those point at the carrier side, not 3CX.

5. What's actually happening on live calls right now?

This is the layer the built-in tools cover least well. 3CX shows you:

• Aggregate queue counters (waiting, answered, abandoned) on the built-in Wallboard.
• The Call Log after the fact.

What it doesn't show in one place: which agent is stuck on a 40-minute call, which DID hasn't rung in two hours, whether "abandoned" calls were actually picked up by the next queue in a cascade, or whether internal extension-to-extension chatter is masking a real drop in customer conversations.

This is where a status layer like VoIPSetu's real-time wallboard fills the gap — per-agent, per-queue, per-DID drill-down with SLA colouring, cascade-aware abandoned tracking, and a separate view for internal vs external calls. It runs on your existing 3CX server (no extra Windows box) and if the VoIPSetu agent stops, 3CX keeps running.

A simple status checklist

Bookmark this order for every "is 3CX broken?" ticket:

1. status.3cx.com — hosted 3CX components.
2. Management Console reachability — from outside your LAN.
3. OS services — systemctl status 3CXPhoneSystem or Windows Services.
4. SIP trunk status dots — Management Console → SIP Trunks.
5. Live call view — built-in Wallboard for aggregate, VoIPSetu Wallboard or Smart Reports for per-agent and per-caller detail.

Nine times out of ten, the answer to "is 3CX down?" is at step 3 or 4 — not step 1.

Related reading

• 3CX call reports & analytics — Smart Report Engine
• 3CX V20 Update 9 — the partner's guide
• Pricing — VoIPSetu tiers by SC