isitmyispDocs

Frequently asked questions

Will it slow my connection down?

No. It sends small pings every 2 seconds to a few destinations, about 1.3 GB a month. The only thing that really uses bandwidth is the speed test, which is off unless you turn it on.

Can I connect it over Wi-Fi?

You can, but you shouldn't. With the probe on Wi-Fi, a Wi-Fi problem gets mixed up with an ISP one. Wire it to the router; the dashboard tells you when it's on Wi-Fi.

Does it work with any ISP?

Yes. It needs nothing from the ISP: it measures from your side. It identifies the ISP by its autonomous system (AS) number, also behind CGNAT or double NAT.

Do I have to leave a computer on?

Something has to be on all the time, but it can be a Raspberry Pi, which uses about as much power as a phone charger. See the Raspberry Pi guide.

The dashboard has said "Measuring…" or "Checking…" for a while

  • Just installed: the first windows take a minute or two.
  • All the time: the monitor isn't running. Check its state with docker ps and its log with docker logs isitmyisp.
  • On one service: no check of that service has completed yet. It should clear within 30 seconds.

The router "loses" pings but the internet works

That's normal for many routers and business firewalls: they deprioritise pings addressed to themselves. isitmyisp detects it and doesn't count it as a problem. See how the verdict works.

Why is the speed test below my plan?

It can be the ISP or something on your side: other devices using the internet at that moment, or the Wi-Fi of the machine measuring. The result warns when your Wi-Fi seems to be the limit. If you connected the router over SNMP, it also shows everything the WAN carried during the test.

Cloudflare alone can't say whether the slow part is your access or the ISP's exit to the rest of the internet. With an iperf3 server of your own inside your ISP and another outside, the result says where the bottleneck is. See Inside and outside your ISP.

Alerts don't arrive

Press Send test in Settings → Alerts → Alerts and look at each channel's result. See Alerts.

I forgot my password

docker exec -it isitmyisp isitmyisp admin reset-password <user>

How do I update?

Run the installer again. The data is kept.

How do I uninstall it?

curl -fsSL https://isitmyisp.enzo-meneghini.com/install.sh | sh -s -- --uninstall

The measurements stay in the isitmyisp volume. To delete them too: docker volume rm isitmyisp.

How is it different from Uptime Kuma, SmokePing or PingPlotter?

What it tells you
Uptime Kuma Whether a site or service answers. It doesn't know if the fault is your network, your ISP or the service.
SmokePing / PingPlotter Latency and loss graphs to each destination. Reading them and deciding who's failing is up to you, and "loss" on middle hops is usually noise.
isitmyisp Whose fault it is, in one sentence: your Wi-Fi or router, your ISP's network, one service, or your DNS. It separates real loss from ICMP noise, catches intermittent drops and the backup link, tells you whether you filled your own link (with the router connected over SNMP), and builds the report your ISP can't brush off.

They work together: plenty of people run Uptime Kuma for their services and isitmyisp for the connection.

How does it know it's my ISP and not my network?

It measures your router, the ISP's first router and several internet destinations at the same time, over ICMP and TCP. If everything outside fails while your router is fine, it's the ISP. If your router fails too, it's your network. If only one destination fails, it isn't your ISP.

So that a single lost packet doesn't blame anyone, loss has to be statistically significant (a 95 % Wilson interval), latency is compared with what's normal for each destination, and an incident needs two bad windows in a row. Loss at a hop in the middle that doesn't carry through to the destination doesn't count: that's the router deprioritising pings, not an outage.

Can it be wrong? Yes. Without the router over SNMP, for example, it can't rule out that your own link was full, and the report says so. The details are in how it decides.

Why does it need --net=host and NET_RAW?

--net=host is so it measures your real network. Without it the container sees Docker's internal network, and "your router" becomes the Docker bridge. NET_RAW is the permission to ping. It doesn't use --privileged. From the host it only mounts its data volume and, read-only, /run/systemd/resolve, to learn which DNS you use.

Do I have to trust a curl | sh?

You don't. The installer prints every Docker command before running it and asks first. With --dry-run it only prints them. And if you'd rather skip it, it's a single docker run, in Install.

Did you build it with AI?

Yes, I wrote it with Claude Code and I'm not hiding it: it's on every commit. The design, what it measures and how it decides are mine, and they come from years of network support hearing "is it our network or the provider?". Every change goes through tests before it lands, and I run it on my own network every day. If you find something odd, open an issue, or privately if it's about security.

How do I back it up, or move it to another machine?

Everything is in the isitmyisp Docker volume: settings, users and measurements. To save it to a file:

docker stop isitmyisp
docker run --rm --entrypoint tar -v isitmyisp:/data -v "$PWD":/backup 21enzo03/isitmyisp czf /backup/isitmyisp-backup.tgz -C /data .
docker start isitmyisp

On the new machine, install it with the installer, stop it and restore the file:

docker stop isitmyisp
docker run --rm --entrypoint tar -v isitmyisp:/data -v "$PWD":/backup 21enzo03/isitmyisp xzf /backup/isitmyisp-backup.tgz -C /data
docker start isitmyisp

The monitor won't start, or doesn't see my network

  • "Operation not permitted" when pinging: the container lacks the permission to ping. Run the installer again or add --cap-add=NET_RAW.
  • It sees one odd address instead of your router: --net=host is missing. Without it, it measures Docker's internal network, not yours.
  • On Docker Desktop (Mac or Windows): --net=host doesn't see the machine's real network, so the path and the router come out wrong. Run it on Linux: a Raspberry Pi, a mini PC or a server.
  • It measures a DNS server that isn't yours (100.100.100.100, 127.0.0.53): those are local forwarders from Tailscale or systemd-resolved, and isitmyisp no longer uses them; if it finds nothing else, it measures your router. If your devices use another DNS, such as AdGuard Home or Pi-hole, set it in Settings → Measurement → DNS servers (for example 192.168.1.22, or 127.0.0.1 if it runs on the same machine).
  • The dashboard doesn't open from another device: if you installed with --local, it only answers on that machine. Run the installer again without that option.

How much does it cost?

The software is free (MIT). If you'd like it installed and looked after for you, it's available as a service.

I found a bug or want to suggest something

Open an issue on GitHub.

Edit this page