YOUR CONNECTION, MADE
VISIBLE
Online ping test
& internet stability monitor.
Monitor latency, jitter, lag spikes, and connection interruptions to better understand how your connection behaves.
Run a ping test
INTERNET STABILITY
MONITOR
Check your ping stability
Browser-to-region WebSocket
round-trip
Test setup
Choose how long to monitor
TEST DURATION
Ready to test01:00
Measurements0
ⓘOne WebSocket round-trip per second. Keep this tab visible for the most reliable results.
Ping over time
READYRound-trip time · milliseconds
⌁Your connection story starts hereStart a test to see latency measurements
Latency Lag spike Failed request
—/ 10
Connection quality
Ready to testRun a test to get a simple rating for ping, fluctuation, and measurement reliability.
This score describes measurements to PingWatch endpoints, not every internet destination.The 1–10 score combines median ping (45%), mean change between successful pings (35%), and successful-probe percentage (20%). A cap prevents a weak category from being hidden by stronger ones. It becomes available after 5 successful measurements. Lower ping and fluctuation, plus more successful probes, improve the score. This is a guide—not a standardized grade or prediction of performance on other services.
Connection events
Lag spikes and periods of possible interruption
✓
No lag spikes detectedDetected events will appear here during your
test.
ADVERTISEMENT
TEST COMPLETE
Your connection report
Here’s a summary of your monitoring session.
Recent test summaries are saved only in this browser.
Measurement note: WebSocket Ping measures browser-to-selected-PingWatch-region round-trip time using a persistent WebSocket echo. HTTP Ping measures the browser's HTTP round trip to PingWatch. Neither mode measures ICMP ping or latency to every website or service. Failed probes are not confirmed packet loss.
BUILT FOR CLARITY
Useful signals.
Honest measurements.
Measure over time
PingWatch sends approximately one probe per second during your selected 1-, 5-, or 10-minute test. WebSocket Ping times replies over a persistent connection to a PingWatch region. HTTP Ping times an HTTP request to PingWatch. Measurements are sequential; the browser's monotonic clock is used to time each round trip.
Spot sudden spikes
Readings are compared with a rolling median baseline. Consecutive elevated readings are grouped as one incident.
Understand stability
Review successful and failed probes, ping variation, and latency statistics. A failed probe can have several causes and does not by itself prove packet loss.
GOOD TO KNOW
Frequently
asked questions
Clear answers about what PingWatch measures—and what it doesn't.
How do WebSocket, HTTP, and ICMP ping differ?+
WebSocket Ping measures the round-trip time for an echo over a persistent WebSocket connection. HTTP Ping measures the time for an HTTP request and response. ICMP ping uses a different network protocol; PingWatch does not perform ICMP measurements.
What destination does PingWatch measure?+
PingWatch measures round-trip latency between your browser and its own selected endpoint. It does not measure every website, application, or destination on the internet.
Why can latency differ between services?+
Latency can vary with server location, network routing, transport protocol, and server conditions. Results to a PingWatch endpoint may therefore differ from measurements to other services.
What is jitter, and how do you calculate it?+
Estimated jitter is the mean absolute difference between each pair of consecutive successful latency readings, in milliseconds. It is a simple indicator of variation, not a diagnosis.
What does the 1–10 connection score mean?+
It combines median latency, average change between successful measurements, and successful-probe percentage into a simple guide. It needs at least five successful measurements and describes results to the selected PingWatch endpoint only.
Does a failed request mean packet loss?+
No. A failed WebSocket or HTTP probe may result from your device, local network, internet route, PingWatch server, browser, or a timeout. Unsuccessful probes do not necessarily indicate packet loss and cannot identify the exact cause of an interruption.
Will the test keep running in another tab?+
Browsers may throttle background tabs. PingWatch warns you if the page is hidden or if scheduling is delayed; keep the tab visible for the most representative results.