Five minutes, three checks
Is CallTrackingMetrics Down? Ask These Three Checks
We are not CallTrackingMetrics and cannot see their systems — their status page is the source. What this page adds is the sequence that answers "is it down" for any platform: one status check, one test call, one browser swap.
- Their status, not ours to claim
- Three checks, five minutes
- Platform vs phone, 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, reached from their official domain. If it shows green and problems persist, the fault is likely local or phone-side, not platform.
The dashboard will not load — is that an outage?
Maybe, or maybe just your session. The browser test settles it: another device, another network. If the dashboard fails everywhere for multiple users while calls still flow, it is a reporting-layer incident — annoying, not fatal.
Calls are not arriving at all — who do I call?
The carrier that hosts the numbers, not the software vendor. Routing, answer points and reachability live on the phone side. If your numbers are Australian and hosted with us, that conversation starts on our contact page.
"Is it down?" deserves a five-minute answer, not a refresh loop. We are an Australian number provider, not CallTrackingMetrics — their platform status is theirs to publish, on their status page. What this page adds is the sequence that answers the underlying question for any platform: is it the platform, the phone layer, or just you? Three checks, in order.
Check one: the status page
The vendor'"'"'s own status page, reached from their official domain. Green with problems persisting means look elsewhere; an incident banner means you have your answer and can stop refreshing. Either way, this check takes sixty seconds and should come first.
Check two: the test call
Ring one of your tracking numbers from a phone you trust. This is the load-bearing check, because it splits the world in two:
- The call connects and rings through. The phone layer works — whatever looks broken is reporting or dashboard, an inconvenience rather than a catastrophe. Capture manual notes and read the outage playbook.
- The call fails. The phone layer is down — routing, answer points or carrier. The software vendor cannot fix this; the number host can. If your numbers are Australian and hosted with us, that conversation starts at contact us.
Check three: the browser swap
Dashboard will not load? Another browser, another device, another network. Fixed? It was local — cache, extension, VPN — and no vendor was ever involved. Still broken everywhere for multiple users? Back to check one with better evidence.
The pattern behind the checks
Most "down" calls are layer confusion: the dashboard and the phone network fail independently, and people assume they fail together. Number-based tracking is built to keep the layers separate — calls route on the network regardless of reporting health, and records catch up when the data layer does. That resilience is what we run: number-based call tracking from $5 a month per number, with call records described in call detail reporting and rates on the pricing page.
The phone-side desk
One provider for numbers and tracking
Number-based tracking from $5 a month per number — calls route on the network, records return when the data does.