Your public IP address
Checking IPv4 and IPv6…
The address websites see. A VPN or proxy can change it.
Your public IP address
Checking IPv4 and IPv6…
The address websites see. A VPN or proxy can change it.
Testing your connection
Running about a dozen checks. This takes a few seconds.
Waiting for measurements.
Waiting for measurements.
Waiting for measurements.
Waiting for measurements.
Waiting for measurements.
Your next step will appear after the checks finish.
Rivalry banter—not live diagnostics.
Select a provider from the available feeds. This filters the diagnosis; it does not send a report anywhere.
Bandwidth test
Measure latency, download, and upload against an ipblame test server. This transfers real data and is separate from the lightweight diagnostic checks above.
The home-lab endpoint will appear here once its public URL is added to config.js.
Configure an HTTPS test endpoint to enable the bandwidth test.
Default test size: 25 MB down and 10 MB up. Results can vary with Wi-Fi, browser load, server capacity, routing, and other traffic.
HTTP measurements to our test server. Distance, server load, and your connection can all affect these results.
Round trip to each location. Differences can reflect distance, routing, or endpoint load; they do not isolate the cause on their own.
Published by each provider. Feed freshness is shown below.
Loading status feeds.
Not every provider publishes a supported feed. A normal public status page does not rule out a local or account-specific problem.
1. Label this run and save a baseline. 2. Change one thing. 3. Run again.
No baseline saved. Results stay in this tab only.
Review and copy a report for your support ticket. Nothing is sent automatically.
This is the address the rest of the internet sees. Your device's own address is usually different.
Routing data from RIPEstat. Non-commercial use.
Nothing yet.