NETWAVE.TODAYEstonia · Tallinn
Waiting for data
Response time—
Uptime—
EarlierNow
Connection checks
Server status
See which servers are available, how quickly they respond and whether there have been interruptions.
Finland · Helsinki
Waiting for data
Response time—
Uptime—
EarlierNow
Poland · Warsaw
Waiting for data
Response time—
Uptime—
EarlierNow
Sweden · Stockholm
Waiting for data
Response time—
Uptime—
EarlierNow
Germany · Frankfurt
Waiting for data
Response time—
Uptime—
EarlierNow
Netherlands · Amsterdam
Waiting for data
Response time—
Uptime—
EarlierNow
Italy · Milan
Waiting for data
Response time—
Uptime—
EarlierNow
Spain · Madrid
Waiting for data
Response time—
Uptime—
EarlierNow
UAE · Dubai
No response
Response time—
Uptime—
EarlierNow
South Korea · Seoul
Waiting for data
Response time—
Uptime—
EarlierNow
China · Hong Kong
Waiting for data
Response time—
Uptime—
EarlierNow
Japan · Tokyo
Waiting for data
Response time—
Uptime—
EarlierNow
Canada · Toronto
Waiting for data
Response time—
Uptime—
EarlierNow
USA · New York
Waiting for data
Response time—
Uptime—
EarlierNow
Allowlist bypass
Waiting for data
Response time—
Uptime—
EarlierNow
How to read the metrics
Start with the server status, then compare response time and history. Together they show whether the server responded and how consistent recent checks have been.
Online or not responding
Online means the server accepted a connection during the check. No response means the connection failed. No data means a result is missing, not a confirmed outage.
Response time
Connection time from the monitoring location to the server, in milliseconds. Lower is faster. This is neither download speed nor latency from your device: your route may differ.
Uptime
The percentage of successful server responses in the saved monitoring history. Values closer to 100% indicate more stable availability. This reflects the available measurements, not daily or monthly uptime; missing data is excluded.
Check history
Marks run from oldest on the left to newest on the right: green means the server responded, red means no response, and grey means no data. The chart shows the latest 61 checks, about three hours at a 180-second interval. Six hours of history are retained and used for uptime calculation. On mobile, tap a mark or slide your finger along the row to select a check.
Automatic updates
Results come from the existing monitoring system. The page reads a report every 180 seconds without reloading. The report creation time is shown above the cards. A warning appears if data is outdated or cannot be fetched.
Choosing a server
Choose a server with a recent Online result, low response time and no recent failed checks. Then try the connection on your own device: your provider, distance and route also affect performance.
