Results from Asia Residential
Node Asia ResidentialRegion: AsiaKind: ResidentialLine: 1 Gbps Down / 500 Mbps Up
Testing: A computer in Asia, on an ordinary home internet line, holds a tunnel open to every VPN provider and checks them every 5 minutes.
These results come from this node only, and are not comparable with another node's. Why vantages differ.
Servers
These figures summarise this node's five-minute checks: uptime over the last 30 days, latency over the last 24 hours of them. Download and upload are each the median of the speed tests in the last 7 days, about one test a day for each server, and the measured location is the country most sources agree on, from the latest full check. Open a row to see uptime over 24 hours, 7 days and 30 days, each with its number of checks.
Until each provider's own wording for its servers is recorded, the locations are our labels for them.
Shuffled daily, not a ranking. Sort by anything below.
| Provider | Status | Location | Served From (CDN) | Uptime (30 days) | Latency (Median · 24 h) | Download (Median) | Upload (Median) | Website |
|---|---|---|---|---|---|---|---|---|
| Show details for IPVanishHide details for IPVanish | Down | Claimed: US Los AngelesMeasured: Not measured | Not measured | 9.6% | Not measured | Not measured | Not measured | Visit site of IPVanish |
IPVanish · US Los Angeles
| ||||||||
| Show details for TorGuardHide details for TorGuard | Up | Claimed: US Los AngelesMeasured: US, Los Angeles (2/2) | Netflix · Los AngelesCloudflare · Los Angeles | 99.9% | 216ms | 68.1Mbps 1 GB download in 2 min | 41.4Mbps 100 MB video sent in 20 sec | Visit site of TorGuard |
TorGuard · US Los Angeles
| ||||||||
| Show details for Proton VPNHide details for Proton VPN | Up | Claimed: US Los AngelesMeasured: US, Los Angeles (2/2) | Netflix · WASCloudflare · Los Angeles | 99.7% | 212ms | 67.6Mbps 1 GB download in 2 min | 26.4Mbps 100 MB video sent in 30 sec | Visit site of Proton VPN |
Proton VPN · US Los Angeles
| ||||||||
| Show details for SurfsharkHide details for Surfshark | Up | Claimed: US Los AngelesMeasured: US, Los Angeles (2/2) | Netflix · NewarkCloudflare · Los Angeles | 97.0% | 213ms | 67.5Mbps 1 GB download in 2 min | 36.9Mbps 100 MB video sent in 20 sec | Visit site of Surfshark |
Surfshark · US Los Angeles
| ||||||||
| Show details for Private Internet AccessHide details for Private Internet Access | Down | Claimed: US CaliforniaMeasured: Not measured | Not measured | 2.3% | Not measured | Not measured | Not measured | Visit site of Private Internet Access |
Private Internet Access · US California
| ||||||||
Speed bars scale: 0 to 100 Mbps What each column means
What the columns mean
- Provider
- The VPN service's logo (and the provider's own label for the server under it, when it differs from the location). Its "Visit site" link is the last column.
- Location
- Two lines. Claimed is where the provider's server list says the server is, quoted exactly. Measured is the country most of the node's geolocation sources (Mullvad and ipinfo) place the server's exit address in, as its two-letter code, then how many of the sources that answered agree: "(2/2)" is both, "(1/1)" is the one source that answered, and the server's details write it out. A city is added only when at least two of the agreeing sources name the same one. If no country has more than half of the answers (the two sources differ) the line says "Sources disagree". Many location databases copy each other, so the count matters more than the word; the server's details list every source's own answer.
- Served From (CDN)
- Where two content delivery networks (CDNs) say they served the tunnel from, from the latest full check, one line each: the Netflix site, then Cloudflare's data center. It is where that network served the tunnel from, not necessarily where the server is: each steers by its own rules, and it is not counted in the Measured line. The server's details give the codes as sent. On a phone it is left out of the row; open the row for it.
- The plain lines
- What a figure means in everyday terms, worked out from the figure itself the same way for every provider. It explains, it never judges. Point at a Download or Upload figure to see its line; open a row (the arrow before the logo) to see all four. Uptime counts a failed check as about five minutes down (the checks are five minutes apart). Latency gives the round trip from the node's region to the server's country in fractions of a second. Download gives how long a 1 GB file (8,000 megabits) takes at that speed; Upload, a 100 MB video (800 megabits). The speed bars all use one scale per table, given under it. On a phone the lines show when a row is opened.
- Uptime (30 days)
- The share of the node's five-minute checks over the last 30 days in which the server's tunnel passed traffic: no error, a WireGuard handshake in the last three minutes, and at least one ping answered through the tunnel. 30 days rather than 24 hours because one bad afternoon and a server that is often down look the same over a day. Time when the node itself was not checking counts neither way, so a node with less history than the window shows how many of those days it was checking; the server's details give uptime over 24 hours, 7 days and 30 days, each with its number of checks.
- Latency (Median · 24 h)
- The middle of the average round-trip times through the tunnel, in milliseconds, over the checks in the last 24 hours that passed traffic. Lower means quicker to respond.
- Download (Median) and Upload (Median)
- Speed through the tunnel in megabits per second: the median of the speed tests in the last 7 days. The node tests each server about once a day, so that is up to seven tests; the server's details give how many, the latest test, the 3-day median, and the node's own line measured just before each test. No figure can exceed the node's own line, shown above the table.
- Status
- Up if the most recent check passed traffic, Down if it did not. Degraded is not used yet: a line between working well and working badly needs the full check's speed figures, or weeks of checks showing what is normal for each server, and we will not invent one. If the last check is more than 30 minutes old the table says "No recent check" instead: the node being offline is not the provider being down.
- Website
- A "Visit site" button to the provider's own website: the same words and the same place for every provider. The logo goes to the same site.
- Last checked
- Point at the status to see how long ago the server was last checked ("4 min ago"). The exact UTC time is in the details.
- Not measured
- There is no measurement for this value yet. A missing value is never shown as zero.