Short, and honest
CallTrackingMetrics Status: The Short, Honest Version
We cannot report CallTrackingMetrics' status — we are a different company, and their status page is the only authoritative source. This page is deliberately short: the boundary, and the two guides that help when any call tracking service wobbles.
- Their status, their source
- The outage playbook
- The platform-vs-phone split
Status questions
Is CallTrackingMetrics up right now?
We cannot tell you — CallTrackingMetrics is a US platform and not us, and we will not mirror or guess at their uptime. Their own status page is the authoritative source, reached from their official domain.
Why not just summarise their status here?
Because status data is perishable and secondhand status is misleading by definition — a page claiming "all systems operational" on another vendor's behalf would be fiction within the hour.
Our calls are failing — where do we start?
With the layer test: ring a tracking number from a trusted phone. Calls arrive? The platform or your browser is the issue. Calls dead? The phone layer — routing, answer points, carrier — and a different helper.
A status search wants a live answer, and this page will not pretend to one: CallTrackingMetrics is a US call tracking platform, not us, and their status page is the only authoritative source for their uptime. Mirroring it would be fiction within the hour. What this short page does hold: the boundary stated once, and the two guides that genuinely help when any call tracking service wobbles.
The boundary, once
Their systems, their status, their incident timeline. We do not paraphrase, mirror or guess — the same discipline applied in our status-page literacy guide, which explains what status pages measure and how to read one during a real incident.
Guide one: the outage playbook
When the platform degrades, the sequence that protects you: confirm scope on the vendor’s status page; make sure calls still reach a human; capture call volumes manually while reports are dark; reconcile when service returns. The full playbook — and the architecture insight that calls can keep flowing while dashboards do not — is in our outage guide.
Guide two: the layer test
Most "is it down" confusion is a layer confusion: the platform (dashboards, reports), the phone network (the calls themselves), and your local setup fail independently. Ring a tracking number from a trusted phone: calls arriving means the phone layer works whatever the dashboard says; calls dead means routing, answer points or carrier — none of which the software vendor fixes. The five-minute diagnostic is in our "down" guide.
The durable answer
If outages keep finding you, the architecture is the lever: number-based tracking keeps the call path on the telephone network — routing happens network-side, so calls arrive even when reporting lags — and the records catch up when the data layer does. That is what we run: number-based call tracking from $5 a month per number, on Australian infrastructure, with per-second call records described in call detail reporting. Carrier-side questions — numbers, routing, reachability — come to us directly: contact us.
The layer we answer for
Numbers, routing and records — one roof
Number-based tracking from $5 a month per number, on Australian infrastructure, with carrier-side answers here.