fshy

Home / IP and proxies

VPN Gate

www.vpngate.net/Volunteer VPN relayip-proxy/vpn-gate-sstpJSONcomparereport an errorprovider JSON

Free allowance
Free with no registration: the relay nodes are volunteered by their operators, and a client connects to one from a published list without creating an account.
Verdict
caveatusable, with a named limit or an unprobed read path
Cost
free tier
Identity
anonymousno card, no phone
Binding limit
per-ip-shaping16 MiB in 918 s, about 17.8 KiB/s (about 146 kbit/s) for one client against one relay; the slowest path measured on the dash.vpn slate
Evidence
documented11 sources; a first-party page was read and the sentence quoted
Freshness
stale on 2026-12-04checked 2026-11-03 (live); stale on 2026-12-04
Free tierFree with no registration: the relay nodes are volunteered by their operators, and a client connects to one from a published list without creating an account.
unit unlimited; metered on unstated; No byte allowance is published on the front page, so unlimited here records that no quota is stated, not that none exists. The measurement puts the ceiling on throughput per client rather than on a byte count.
PriceUSD 0: free, no registration, no allowance published
Limits
  • per-ip-shaping (binding) 16 MiB in 918 s, about 17.8 KiB/s (about 146 kbit/s) for one client against one relay; the slowest path measured on the dash.vpn slate
  • volume-quota none published: free with no registration, and no byte allowance stated on the front page source
The ceiling that was measured is a rate, not a byte cap, so it is filed under per-ip-shaping. The volume-quota entry records that no allowance was found, not that a generous one exists.
Bindingper-ip-shaping The roughly 599,000 requests are small and are never the binding quantity.
Identityanonymous No registration: the node list is public and a client connects straight to a volunteer's relay, so no email, phone, card or account is collected at any point.
EgressNo traffic allowance in either direction is published. The offer is free with no registration, and the far end is a volunteer's own machine. The measured position is a rate rather than a cap: 16 MiB crossed in 918 s.
free allowance: none published
Per-object capnot applicable: a tunnel and an exit address, not an object
Interfacecli SSTP carries the tunnel inside TLS. A user supplies a relay's address from the published node list and connects with an SSTP client; this record measures the SSTP path only.
ToolingAn SSTP client inside a free or rented host with a full TCP stack, driven by hand from the published node list, plus a way to pick and re-pick a node as volunteers drop out. No rclone backend covers SSTP, so a wrapper would have to be written; that is a tooling note, not a verdict.
Composes withA free outbound exit for fetches the gateway would otherwise make from a datacentre address, held as a fallback rather than a primary path because 16 MiB took 918 s.
ReliabilityThe transit TLS terminates at a volunteer's own machine rather than at an audited endpoint, and a volunteer's node can disappear or change its exit address at any time; the measured path was the slowest on the dash.vpn slate.
NotesWhy per-ip-shaping and not volume-quota: nothing on the vendor page states an allowance, so there is no byte ceiling to hit, while the one thing that was measured is a rate. The 45 GB arithmetic above is derived from the measured 16 MiB in 918 s, not a second measurement: 16,777,216 bytes over 918 s is about 18,275 bytes a second, which is 17.8 KiB/s. Only one transfer was measured, through one relay at one time, so 918 s is a sample and not a distribution. That sample cannot separate three candidate causes for the slowness: (1) the volunteer's own uplink, (2) deliberate per-IP shaping on the relay, (3) SSTP-in-TLS overhead on the path. Ruling them out needs the same payload repeated against several relays at different hours with the bytes-per-second compared; until that runs, the per-ip-shaping label follows the handoff's own reading rather than a measurement that distinguishes the three. Rung 5 rather than 2 because lane 4's 35 distinct exit ASNs characterise the exit identity by the registration class of the carriers behind the relays, with Korea Telecom, SoftBank, KDDI and LG Powercomm leading that set, and the single measured exit AS8369 INTERSVYAZ is one member of it. That count is why this is the strongest free source of carrier-registered exits found so far, and it is also why one address going bad does not condemn the source.
Evidence notedocumented The free-and-no-registration fact the verdict also rests on is the vendor's own page, so the weakest rung among the fields the verdict depends on is documented. It moves to measured when the anonymous path is exercised end to end from a client that records the signup state itself, so the vendor page stops being the only support for it.
Parsed numbers
  • has-free-tier 1
  • per-ip-shaping 16 MiB
  • price USD 0
Evidence 11
datesourcewhat it proved
2026-10-10source not publishedA 16 MiB payload crossed the SSTP relay in 918 s and exited at AS8369 INTERSVYAZ; this is the slowest path measured on the dash.vpn slate.
2026-10-24www.vpngate.net/The relay is free and needs no registration, and its nodes are volunteered by their operators rather than run by the site.
2026-10-24probe: vpngate-exit-asn-sweepLane 4 counted 35 distinct exit ASNs across the relays, led by Korea Telecom, SoftBank, KDDI and LG Powercomm. The sweep's own run date was not carried in the handoff, so this row is dated to the record rather than to the run.
2026-11-03probe: rdap.db.ripe.net/autnum/8369The registrant organisation ORG-IJ7-RIPE of RIPE aut-num AS8369 (as-name INTERSVYAZ-AS) is Intersvyaz-2 JSC.
2026-11-03probe: rdap.db.ripe.net/autnum/8369RIPE aut-num AS8369 has as-name INTERSVYAZ-AS.
2026-11-03probe: rdap.arin.net/registry/ip/121.186.118.191121.186.118.191 lies in KORNET-KR, 121.160.0.0-121.191.255.255, type ALLOCATED PORTABLE, source KRNIC.
2026-11-03probe: rdap.arin.net/registry/ip/126.12.172.212126.12.172.212 lies in BBTEC, 126.0.0.0-126.31.255.255, type ALLOCATED PORTABLE, source APNIC.
2026-11-03probe: rdap.arin.net/registry/ip/59.86.200.24459.86.200.244 lies in LG-HELLOVISION-KR, 59.86.192.0-59.86.255.255, type ALLOCATED PORTABLE, source KRNIC.
2026-11-03probe: rdap.arin.net/registry/ip/114.16.18.46114.16.18.46 lies in KDDI-NET, 114.16.18.0-114.16.18.255, source JPNIC; the object carries no type field.
2026-11-03probe: rdap.arin.net/registry/ip/219.100.37.212219.100.37.212 lies in SoftEther-CIDR-BLK-JP, 219.100.36.0-219.100.39.255, source JPNIC; the object carries no type field.
2026-11-03probe: rdap.db.ripe.net/autnum/8369RIPE aut-num AS8369 has as-name INTERSVYAZ-AS
More fields 17
rung5
rung noteThe exit identity is characterised at the registration class of the carrier ASNs behind the relays, not at one address: lane 4 counted 35 distinct exit ASNs led by consumer carriers, and the measured transfer exited one of them.
measured exit asnAS8369
measured exit asn nameINTERSVYAZ-AS
payload mib16
elapsed seconds918
derived throughput16 MiB / 918 s = about 17.8 KiB/s, about 146 kbit/s
distinct exit asns35
leading asns["Korea Telecom","SoftBank","KDDI","LG Powercomm"]
slowest on slatedash.vpn
transport tls terminates atthe volunteer relay operator
measured exit asn registrationRIPE aut-num AS8369, as-name INTERSVYAZ-AS, status active, registrant organisation Intersvyaz-2 JSC (ORG-IJ7-RIPE), Russian Federation. RIPE carries no IP-type field, so the carrier class is read from the holder, not from a registry class.
registry lookup kornetAPNIC RDAP: 121.186.118.191 is in KORNET-KR, 121.160.0.0-121.191.255.255, type ALLOCATED PORTABLE (source KRNIC)
registry lookup bbtecAPNIC RDAP: 126.12.172.212 is in BBTEC, 126.0.0.0-126.31.255.255, type ALLOCATED PORTABLE
registry lookup lg hellovisionAPNIC RDAP: 59.86.200.244 is in LG-HELLOVISION-KR, 59.86.192.0-59.86.255.255, type ALLOCATED PORTABLE (source KRNIC)
registry lookup kddi netAPNIC RDAP: 114.16.18.46 is in KDDI-NET, 114.16.18.0-114.16.18.255 (source JPNIC); the object carries no type field
registry lookup softetherAPNIC RDAP: 219.100.37.212 is in SoftEther-CIDR-BLK-JP, 219.100.36.0-219.100.39.255 (source JPNIC); the object carries no type field
Unknown values 1
  • retention stated: the field does not apply to this kind of offer