Results from Asia Data Center

Node Asia Data CenterRegion: AsiaKind: Data centerLine: 4 Gbps Out / 40 Gbps In

Testing: A server in Asia, on a data-center 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 the last 24 hours of this node's five-minute checks, except download and upload: each is 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.

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.

ProviderStatusLocationServed From (CDN)UptimeLatency (Median)Download (Median)Upload (Median)Website
Show details for TorGuardHide details for TorGuardTorGuard websiteUp Claimed: US Los AngelesMeasured: US, Los Angeles (2/2)Netflix · Los AngelesCloudflare · Los Angeles100.0%175ms72.5Mbps 1 GB download in 2 min51.8Mbps 100 MB video sent in 20 secVisit site of TorGuard
Uptime 24 h
100.0%Answered all 286 checks
Latency median
175msAsia to the US server and back: about a fifth of a second
Down median
72.5Mbps1 GB download in 2 min
Up median
51.8Mbps100 MB video sent in 20 sec

TorGuard · US Los Angeles

Uptime and Latency · Last 24 h
286 quick checks (one every five minutes would be 288), 7 full checks
Claimed location
US Los Angeles
Measured location

United States, Los Angeles · 2 of 2 sources

  • Mullvad: United States, Los Angeles
  • ipinfo: United States, Los Angeles
Network
  • MTU: set to Not measured · found Not measured
  • Cloudflare data center: LAX (Los Angeles)
  • Netflix site: lax001 (Los Angeles)
  • From the full check of 2026-10-23 00:07 UTC
Download and Upload · Last 7 days
  • Last 7 days, median of 5 tests: download 72.5 Mbps · upload 51.8 Mbps
  • Last 3 days, median of 2 tests: download 73.1 Mbps · upload 53.7 Mbps
  • Latest test, 2026-10-22 18:00 UTC: download 69.0 Mbps · upload 51.2 Mbps
  • The node's own line, outside the tunnel (median of the same tests): download 1742 Mbps · upload 665 Mbps
Node at the last check
Load 0.12 · Free memory 3685 MB · Tunnels up 219
Last Checked
2026-10-23 03:45 UTC
Notes
None

How these are measured

Show details for Private Internet AccessHide details for Private Internet AccessPrivate Internet Access websiteUp Claimed: US Salt Lake CityMeasured: US, Salt Lake City (2/2)Netflix · PhiladelphiaCloudflare · Los Angeles100.0%246ms66.7Mbps 1 GB download in 2 min40.9Mbps 100 MB video sent in 20 secVisit site of Private Internet Access
Uptime 24 h
100.0%Answered all 286 checks
Latency median
246msAsia to the US server and back: about a quarter of a second
Down median
66.7Mbps1 GB download in 2 min
Up median
40.9Mbps100 MB video sent in 20 sec

Private Internet Access · US Salt Lake City

Uptime and Latency · Last 24 h
286 quick checks (one every five minutes would be 288), 7 full checks
Claimed location
US Salt Lake City
Measured location

United States, Salt Lake City · 2 of 2 sources

  • Mullvad: United States, Salt Lake City
  • ipinfo: United States, Salt Lake City
Network
  • MTU: set to Not measured · found Not measured
  • Cloudflare data center: LAX (Los Angeles)
  • Netflix site: phl001 (Philadelphia)
  • From the full check of 2026-10-23 00:07 UTC
Download and Upload · Last 7 days
  • Last 7 days, median of 4 tests: download 66.7 Mbps · upload 40.9 Mbps
  • Last 3 days, median of 2 tests: download 64.0 Mbps · upload 40.9 Mbps
  • Latest test, 2026-10-22 18:00 UTC: download 61.5 Mbps · upload 40.9 Mbps
  • The node's own line, outside the tunnel (median of the same tests): download 1544 Mbps · upload 505 Mbps
Node at the last check
Load 0.12 · Free memory 3685 MB · Tunnels up 219
Last Checked
2026-10-23 03:45 UTC
Notes
None

How these are measured

Show details for IPVanishHide details for IPVanishIPVanish websiteUp Claimed: US San JoseMeasured: US, San Jose (2/2)Netflix · San JoseCloudflare · San Jose85.3%233ms59.4Mbps 1 GB download in 2 min40.0Mbps 100 MB video sent in 20 secVisit site of IPVanish
Uptime 24 h
85.3%42 of 286 checks failed, about 4 hours down
Latency median
233msAsia to the US server and back: about a quarter of a second
Down median
59.4Mbps1 GB download in 2 min
Up median
40.0Mbps100 MB video sent in 20 sec

IPVanish · US San Jose

Uptime and Latency · Last 24 h
286 quick checks (one every five minutes would be 288), 7 full checks
Claimed location
US San Jose
Measured location

United States, San Jose · 2 of 2 sources

  • Mullvad: United States, San Jose
  • ipinfo: United States, San Jose
Network
  • MTU: set to Not measured · found Not measured
  • Cloudflare data center: SJC (San Jose)
  • Netflix site: sjc002 (San Jose)
  • From the full check of 2026-10-23 00:07 UTC
Download and Upload · Last 7 days
  • Last 7 days, median of 6 tests: download 59.4 Mbps · upload 40.0 Mbps
  • Last 3 days, median of 2 tests: download 57.6 Mbps · upload 32.6 Mbps
  • Latest test, 2026-10-22 18:00 UTC: download 57.9 Mbps · upload 28.0 Mbps
  • The node's own line, outside the tunnel (median of the same tests): download 1706 Mbps · upload 391 Mbps
Node at the last check
Load 0.12 · Free memory 3685 MB · Tunnels up 219
Last Checked
2026-10-23 03:45 UTC
Notes
None

How these are measured

Show details for Proton VPNHide details for Proton VPNProton VPN websiteUp Claimed: US Los AngelesMeasured: US, Los Angeles (2/2)Netflix · WASCloudflare · Los Angeles56.6%181ms66.6Mbps 1 GB download in 2 min47.8Mbps 100 MB video sent in 20 secVisit site of Proton VPN
Uptime 24 h
56.6%124 of 286 checks failed, about 10 hours down
Latency median
181msAsia to the US server and back: about a fifth of a second
Down median
66.6Mbps1 GB download in 2 min
Up median
47.8Mbps100 MB video sent in 20 sec

Proton VPN · US Los Angeles

Uptime and Latency · Last 24 h
286 quick checks (one every five minutes would be 288), 7 full checks
Claimed location
US Los Angeles
Measured location

United States, Los Angeles · 2 of 2 sources

  • Mullvad: United States, Los Angeles
  • ipinfo: United States, Los Angeles
Network
  • MTU: set to Not measured · found Not measured
  • Cloudflare data center: LAX (Los Angeles)
  • Netflix site: was001 (WAS)
  • From the full check of 2026-10-23 00:07 UTC
Download and Upload · Last 7 days
  • Last 7 days, median of 4 tests: download 66.6 Mbps · upload 47.8 Mbps
  • Last 3 days, median of 1 test: download 57.1 Mbps · upload 47.0 Mbps
  • Latest test, 2026-10-22 18:00 UTC: download 57.1 Mbps · upload 47.0 Mbps
  • The node's own line, outside the tunnel (median of the same tests): download 1690 Mbps · upload 351 Mbps
Node at the last check
Load 0.12 · Free memory 3685 MB · Tunnels up 219
Last Checked
2026-10-23 03:45 UTC
Notes
None

How these are measured

Show details for SurfsharkHide details for SurfsharkSurfshark websiteUp Claimed: US SeattleMeasured: US, Seattle (2/2)Netflix · SEACloudflare · SEA100.0%176ms82.0Mbps 1 GB download in 2 min52.6Mbps 100 MB video sent in 20 secVisit site of Surfshark
Uptime 24 h
100.0%Answered all 286 checks
Latency median
176msAsia to the US server and back: about a fifth of a second
Down median
82.0Mbps1 GB download in 2 min
Up median
52.6Mbps100 MB video sent in 20 sec

Surfshark · US Seattle

Uptime and Latency · Last 24 h
286 quick checks (one every five minutes would be 288), 7 full checks
Claimed location
US Seattle
Measured location

United States, Seattle · 2 of 2 sources

  • Mullvad: United States, Seattle
  • ipinfo: United States, Seattle
Network
  • MTU: set to Not measured · found Not measured
  • Cloudflare data center: SEA (SEA)
  • Netflix site: sea001 (SEA)
  • From the full check of 2026-10-23 00:07 UTC
Download and Upload · Last 7 days
  • Last 7 days, median of 5 tests: download 82.0 Mbps · upload 52.6 Mbps
  • Last 3 days, median of 2 tests: download 84.3 Mbps · upload 41.8 Mbps
  • Latest test, 2026-10-22 18:00 UTC: download 82.0 Mbps · upload 52.6 Mbps
  • The node's own line, outside the tunnel (median of the same tests): download 1622 Mbps · upload 390 Mbps
Node at the last check
Load 0.12 · Free memory 3685 MB · Tunnels up 219
Last Checked
2026-10-23 03:45 UTC
Notes
None

How these are measured

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
The share of the node's five-minute checks over the last 24 hours 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. Time when the node itself was not checking counts neither way; the server's details give the number of checks.
Latency (Median)
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.