One question, two very different afternoons. We measure your line and tell you which side the fault sits on.
Signalyzr mobile app launching soon — advanced diagnostics for radio signal and deeper cellular insight.
Outage boards tell you whether strangers are complaining, which is a different question from whether YOUR line is faulty — a dead access point and a regional failure look identical from your sofa. Signalyzr measures your own connection across six signals and reports which side of your front door the evidence points to, or says plainly when the evidence is inconclusive.
There are only three places this can go wrong, and they need three completely different responses. Inside your home — the access point, the band you latched onto, the distance and walls between you and it, or a device quietly saturating the line. At your provider — the link from your building to them, congestion at the exchange, or a fault upstream. Or beyond both of you — the route to one particular service, which is why a single app can misbehave while everything else is untroubled.
Guessing wrong is expensive in the most irritating way. Reboot the router when the exchange is congested and you achieve nothing but a two-minute outage you caused yourself. Ring your provider when the real culprit is a microwave oven sharing a channel with your 2.4 GHz band, and you will be walked through a script you have already tried, then told to wait.
What we do not do is count complaints. Crowd-sourced outage maps answer a genuinely different question — whether other people are unhappy — and their silence proves nothing about your line. A fault affecting one building generates no chatter at all.
Being able to say 'my line drops eleven percent of packets under load, here are the numbers' changes the conversation with a support desk entirely. It moves you past the restart-your-router script, because you have already done the triage their first tier exists to perform. It works in the other direction too: if the fault turns out to be a saturated 2.4 GHz band in your own kitchen, you have saved yourself forty minutes on hold to be told exactly that.
No, and this is the most common misreading of those sites. They aggregate complaints, so they surface faults big enough for many people to notice and post about. A failure affecting one street, one building or one line produces no complaints and therefore no graph — while being completely real for you. A quiet outage board only tells you that a large regional failure is unlikely.
Honestly, no — and be sceptical of any tool that claims otherwise from a single test. Deliberate throttling and ordinary congestion look nearly identical in a one-off measurement. What we can show is the shape of the degradation: when it appears, whether it survives a change of network, and whether it tracks the hours when everyone in your area is streaming. That pattern is evidence worth taking to a provider; a single number is not.
That points inside your home rather than at your provider, since both devices share the same line to the outside world. Usually it is the band, the distance, or the laptop's own adapter. Run the test on each device and compare the local-hop figures — if the phone's are clean and the laptop's are not, the line is not the problem.
Take readings at two or three different times, ideally including a busy evening. Intermittent faults are the ones support desks are most sceptical about, and a single reading is easy to dismiss as a bad moment. Three readings at different hours showing the same pattern are considerably harder to wave away.
Neither. It runs in the browser, there is no account, and we do not look at what you browse — we time our own probes and read the network's response to them.
Signalyzr is a free, privacy-first network diagnostic tool made in India. Loading the diagnostic app…