IVPN
ivpn.net · 2 records in Egress and tunnels, IP and proxies · JSON
Records 2
- paidIVPN (exit addresses)
IP and proxiesidentity anonymousno cardevidence measuredstale on 2026-12-05
- fails: egressIVPN (pro)
Egress and tunnelsno free tieridentity emailno cardlimit write-gatedevidence documentedstale on 2026-12-05
IVPN (exit addresses)
IP and proxies- Free allowance
- No free tier. The pricing page lists three plans, Standard, Plus and Pro, and a 1 Week term at $2; no monthly or yearly rate was read from the captured text.
- Verdict
- paidno free allowance; listed for its price
- Cost
- no price stated
- Identity
- anonymousno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- measured5 sources; a live request was made and its output kept
- Freshness
- stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
| Free tier | No free tier. The pricing page lists three plans, Standard, Plus and Pro, and a 1 Week term at $2; no monthly or yearly rate was read from the captured text. unit none; metered on none; The price is the vendor's plan rate for the subscription whose exits are classified here; the exit-address measurement itself has no price. |
|---|---|
| Price | none stated |
| Limits |
|
| Binding | none No limit kind binds the record: it measures exit addresses and states no byte quota or request rate. What matters is list membership: 81 of 89 sampled exits are on a datacenter list. |
| Identity | anonymous The pricing page states no email is required for signup, with cash, Monero and Bitcoin accepted. |
| Egress | unverified: no traffic allowance or per-GB price appears in the captured pages; metered is recorded false because no metered charge was read. free allowance: none published |
| Retention | not applicable: an address, not an object |
| Interface | unknown The server list at https://api.ivpn.net/v5/servers.json is the source of the exit addresses classified here. The schema interface enum has no token for a VPN tunnel, so the tunnel protocols are not recorded as an interface. endpoint: https://api.ivpn.net/v5/servers.json |
| Tooling | The exit addresses are read from https://api.ivpn.net/v5/servers.json and classified with an IP-class detector; the service itself is reached with the vendor's own client or a WireGuard or OpenVPN configuration. |
| Composes with | A Worker or a free compute node dials the tunnel and the traffic leaves at one of these exit addresses, so the upstream sees an address in the ASNs listed here and not the caller's network. |
| Reliability | 81 of 89 sampled exit addresses are on a datacenter list and 89 of 89 on a VPN list, so a site that blocks those lists blocks most of this fleet; 1 of 89 are also on an abuse list. |
| Notes | List membership of 89 exit addresses (detector index version 20261103T163900Z-00d117b2, 2026-11-03): datacenter 81, VPN 89, abuse 1, none of the three 0. VPN list: 89 of 89, of which 23 are in the x4b VPN list and the rest are in the vendor's own server list as ingested by the detector, so the VPN count includes the vendor feed. Definitions: datacenter is an address inside a range the x4b datacenter list publishes; VPN is inside the x4b VPN list or a per-provider server list; abuse is on at least one independent abuse family; none of the three states list membership, not physical siting. |
| Evidence note | measured The list membership, ASN spread and counts are measured: each address was answered by the detector at the stated index version. The plan price and the identity class are documented from the vendor's captured pages; where a page did not state them they are unverified. The sample is the addresses the vendor endpoint returned, not proof that every address a user is handed is in it. |
| Parsed numbers |
|
Evidence 5
| date | source | what it proved |
|---|---|---|
| 2026-11-03 | probe: https://api.ivpn.net/v5/servers.json | The vendor endpoint https://api.ivpn.net/v5/servers.json gave 89 IPv4 exit addresses, each answered by the address-class detector at index version 20261103T163900Z-00d117b2 on 2026-11-03. Datacenter list: 81 of 89; VPN list: 89 of 89 (23 in the x4b VPN list); abuse list: 1 of 89; on none of the three: 0 of 89. 22 distinct ASNs and 85 distinct /24s; largest ASN AS60068 CDN77 Datacamp Limited with 28 addresses. |
| 2026-11-03 | probe: https://api.ivpn.net/v5/servers.json | Detector index version 20261103T163900Z-00d117b2 was the one every one of the 89 answers carries. |
| 2026-11-04 | www.ivpn.net/pricing/ | the pricing page lists a 1 Week term at $2 in USD |
| 2026-11-04 | www.ivpn.net/pricing/ | signup needs no email; payment by cash, Monero or Bitcoin is accepted |
| 2026-11-04 | www.ivpn.net/pricing/ | the Standard plan row lists 5 devices |
More fields 4
| rung | 4 |
|---|---|
| rung note | Addresses came from the vendor's own server list and each was classified; no exit was connected to, so the address a user is handed at connect time was not observed. |
| list membership | {"measured_on": "2026-11-03","n": 89,"datacenter": 81,"vpn": 89,"vpn_in_x4b": 23,"abuse": 1,"none_of_the_three": 0,"detector_index_version": "20261103T163900Z-00d117b2","probed_at": "2026-11-03T17:20:51Z","endpoint": "https://api.ivpn.net/v5/servers.json"} |
| asn diversity | {"measured_on": "2026-11-03","addresses": 89,"subnets_24": 85,"asns": 22,"largest_asn": "AS60068 CDN77 Datacamp Limited","largest_asn_addresses": 28,"largest_asn_share": "31%"} |
Unknown values 2
- interface: the access interface was not established
- per object cap stated: the field does not apply to this kind of offer
IVPN (pro)
Egress and tunnels- Free allowance
- No free tier, and no port forwarding since 2023: we have made the decision to gradually phase out the port forwarding feature from the IVPN Pro plan.
- Verdict
- fails: egressdata cannot be read back out at a usable rate or price
- Cost
- no price statedsee Price below
- Identity
- emailno card, no phone
- Binding limit
- write-gatedport forwarding removed from the Pro plan from 2023-06-29 onward
- Evidence
- documented6 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
| Free tier | No free tier, and no port forwarding since 2023: we have made the decision to gradually phase out the port forwarding feature from the IVPN Pro plan. unit none; metered on none |
|---|---|
| Price | unverified; pricing page shows a 1 Week plan at USD 2 and three tiers without byte or price detail in the extracted text |
| Limits |
|
| Binding | write-gated The feature does not exist, so nothing about volume is reachable: the constraint that fails first is that there is no inbound path at all. |
| Identity | email The pricing page states No email required for signup, with cash, Monero and Bitcoin accepted and a 30-day refund window. |
| Egress | unverified: the pricing page read lists tiers, device counts and a 1 Week plan at $2, but no byte allowance.; ingress: none free allowance: none published |
| Interface | cli Account area for configs; no port API. |
| Tooling | wg-quick with account-generated configs; no port facility. Protocols: WireGuard, OpenVPN and IPSec. Obfuscation: V2Ray (VMess over QUIC or TCP) on every platform, and obfs4 for OpenVPN on desktop. A SOCKS5 proxy service is listed among the features. BitTorrent rule and UDP: unverified: no page read states them. |
| Composes with | Useful only as a client-side tunnel; it cannot publish a service. |
| Reliability | No inbound path exists, so there is no throttle or drop to record. |
| Notes | The 2023 announcement says gradually, so the open question was whether any tier retained it; the 2026 pricing page lists no port forwarding on any tier, which closes that question for the product as sold. IVPN remains a credible WireGuard provider with anonymous signup, which is why the record names what it lost rather than dismissing it. |
| Evidence note | documented The removal is documented from the vendor blog, read, and dated 2023-06-29. Measured is impossible because there is no feature to measure; a 2026 support-page read confirming the removal still stands would be the next check. |
| Parsed numbers |
|
Evidence 6
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | www.ivpn.net/blog/gradual-removal-of-port-forwarding/ | Port forwarding was phased out of IVPN Pro, posted 2023-06-29, with the reason given as abuse, law enforcement inquiries and data centre relationships. |
| 2026-10-23 | www.ivpn.net/pricing/ | Three tiers, Standard, Plus and Pro, with no port forwarding listed anywhere in the plan text, and no email required for signup. |
| 2026-11-03 | www.ivpn.net/en/ | part of the text of Tooling, above |
| 2026-11-03 | www.ivpn.net/en/ | part of the text of Tooling, above |
| 2026-11-03 | www.ivpn.net/pricing/ | SOCKS5 proxy service is a listed feature |
| 2026-11-03 | www.ivpn.net/pricing/ | part of the text of Free tier, above |
More fields 6
| wg path | native-conf |
|---|---|
| wg detail | WireGuard is a supported protocol and configs are generated in the account area; this does not help, because there is no port to forward. |
| ingress | none |
| volume stated | unverified: the pricing page read lists tiers, device counts and a 1 Week plan at $2, but no byte allowance. |
| bytes transit | yes |
| transit note | Traffic crosses IVPN servers outbound only, from a user's point of view. |
Unknown values 2
- per object cap stated: the field does not apply to this kind of offer
- retention stated: the field does not apply to this kind of offer