Down, or just not loading?
CallTrackingMetrics Down: The Five-Minute Diagnostic
We are not CallTrackingMetrics, so we cannot see their systems — their status page can. What this page adds is the diagnostic: is the platform down, are your calls failing, or is it just your session? Three different problems, three different fixes.
- Three failures, separated
- A five-minute check order
- Calls vs dashboard, split
Down questions
Is CallTrackingMetrics down right now?
We cannot see their systems and will not guess. Their own status page is the authoritative source — check it first, because "the dashboard will not load" and "calls are failing" are different incidents with different owners.
My call reports stopped updating — is that an outage?
Possibly, but check the phone layer first: are calls still arriving and being answered? On number-based setups calls flow on the network even when reporting lags. If calls flow and reports stall, it is a data-layer incident.
Who do I contact about my numbers failing?
Whoever hosts the numbers — a different desk from the software vendor. If your numbers are Australian and hosted with us, our contact page is the direct path; the carrier owns routing and reachability, not the tracking platform.
"Is it down?" has three possible subjects, and searches rarely specify which: the platform's dashboard, the calls themselves, or the browser session in front of you. We are an Australian number provider, not CallTrackingMetrics — their system status belongs on their status page. What we can publish is the diagnostic that separates the three failures, because each has a different owner and a different fix.
The three failures
Failure 1: the session. The dashboard will not load, but a colleague's does, or your phone's browser does. Cause: local — cache, network, VPN, browser extension. Fix: reload, incognito, another device. No vendor involvement.
Failure 2: the platform. Status page shows an incident, or multiple independent users report the same failure. Cause: vendor infrastructure. Fix: their incident process — subscribe to status updates and run the manual-capture playbook in our outage guide rather than refreshing.
Failure 3: the phone layer. Calls themselves are not arriving, ringing out, or misrouting — while the dashboard may be perfectly green. Cause: routing configuration, answer-point hardware, or the carrier. Fix: the number host's support desk, not the software vendor's.
The five-minute check order
- Status page first — theirs, for their platform. It settles Failure 2 in seconds if an incident is live.
- Test a call. Ring one of the tracking numbers from a phone you trust. Calls arriving? The phone layer works, whatever else is broken.
- Cross-check the session. Another browser or device on the dashboard. Distinguishes Failure 1 from Failure 2.
- Check recency. CDR-style records can lag slightly; data "missing" for two minutes is not an outage.
The architecture takeaway
If outages like this recur, the durable answer is architectural: number-based tracking keeps the call path on the telephone network — calls route even when dashboards do not — and the reporting returns when the data does. That model is what we run: number-based call tracking from $5 a month per number, with call records behind the reports described in call tracking metrics software. If the failing layer is your Australian numbers themselves, that desk is ours: contact us.
The carrier-side desk
Australian numbers, answered here
Number-based tracking where calls route on the network and reports come from CDRs — from $5 a month per number.