Status, honestly separated
CallTrackingMetrics Status Page: Where It Lives and How to Read It
We are not CallTrackingMetrics, so we cannot report their uptime or link you to their live status — their own status page is the authoritative source. What we can do is make you a fluent status-page reader, because that skill works during every outage.
- Not their status feed
- How to read a status page
- What statuses actually mean
Status questions
Is this the CallTrackingMetrics status page?
No. Simple 1300 Numbers is a separate Australian company. Any status information about CallTrackingMetrics belongs on their own status page or support channels — we will not mirror or paraphrase their uptime, because we cannot verify it.
What does each status level mean?
Status pages typically grade from fully operational through degraded performance, partial outage and major outage. The useful detail is usually in the incident history: which component failed, when mitigation started, and how long past incidents lasted.
My calls are failing — is it the platform or my numbers?
Check the vendor's status page first; if it shows all systems operational, the fault is more likely in your routing, your answer-point phones, or the numbers themselves. Those are carrier questions, which is a different desk than the software vendor's.
A status-page search is usually an incident in progress: calls are failing somewhere and you need to know whose fault it is. If the platform is CallTrackingMetrics, a US call tracking vendor — and not us — their own status page is the only authoritative source for their uptime, and we will not mirror it. What this page can give you is the reading skill: what status pages measure, how to interpret each level, and how to tell a platform problem from a phone-number problem.
What a status page actually reports
Status pages report the vendor's software and infrastructure: dashboards, APIs, number-provisioning services, recording storage. They do not report the telephone network between the caller and the platform, your office internet, or the handset on your desk — which is why "all systems operational" can coexist with your calls still failing. The status vocabulary is roughly standard across vendors: operational, degraded, partial outage, major outage, plus maintenance windows announced in advance.
Reading it during an incident
Three habits separate a useful status check from a refresh loop:
- Read the incident history, not just the banner. The component named in the incident tells you what is actually broken — an API failure means your integrations misbehave while calls keep flowing; a telephony component failure is the reverse.
- Check timestamps against your symptoms. If incidents began after your calls started failing, the platform may not be your problem yet.
- Subscribe if you depend on it. Every status page worth reading offers notifications; depending on a platform without subscribing is choosing to learn about outages from angry customers.
The other diagnosis path: your numbers
When the platform shows green but calls fail, the fault lives in the phone layer: routing rules pointed at a dead answer point, a surrendered or out-of-service number, or carrier-side trouble. That layer is not the software vendor's to diagnose — it belongs to whoever hosts your numbers. Number-based tracking on Australian infrastructure, where numbers, routing and reporting sit with one provider, is described on our call tracking page, with its measurement philosophy in what call tracking software is and the carrier-side cost model — $5 a month per number, call data billed per second — on the pricing page.
The carrier-side desk
Questions about numbers? That is us
Routing, numbers and call reporting on Australian infrastructure — described plainly, priced from $5 a month per tracking number.