Home / Egress and tunnels
NatP2P
natp2p.cn/UDP port forwardegress/natp2pJSONcomparereport an errorprovider JSON
- Free allowance
- Reverse proxy makes an intranet public; hole punching supports TCP and UDP direct connection; aggregated links let one tunnel span several nodes. [translated]
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- anonymousno card, no phone
- Binding limit
- per-ip-shapingrelay mode quota for free users, amount unpublished
- Evidence
- documented1 source; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | Reverse proxy makes an intranet public; hole punching supports TCP and UDP direct connection; aggregated links let one tunnel span several nodes. [translated] unit mixed; metered on unstated |
|---|
| Price | USD 0 |
|---|
| Limits | - per-ip-shaping (binding) relay mode quota for free users, amount unpublished source
- request-rate P2P requires both ends in the same room source
|
|---|
| Binding | per-ip-shaping No byte figure is published, so the relay quota is the only metered thing and its size is unknown; P2P mode avoids the relay but cannot serve an arbitrary public client, so it does not answer the ingress test. |
|---|
| Identity | anonymous A downloadable client and a QQ group for support; no registration flow is described on the page read. |
|---|
| Egress | The page title advertises daily free traffic without check-in, but no byte figure appears on the page body; the FAQ says relay-mode free users have a quota and P2P mode is unlimited in speed.; ingress: udp free allowance: none published |
|---|
| Interface | cli Green-build Windows client download; no API or Linux client is described on the page. |
|---|
| Tooling | vendor Windows client |
|---|
| Composes with | A UDP-capable reverse proxy for a WG listener, with P2P as the fast path between a user's own devices. |
|---|
| Reliability | P2P fails on symmetric NAT and falls back to the metered relay; the vendor recommends the proxy when the room join fails. |
|---|
| Notes | The only provider in the sweep that pairs hole punching with a public reverse proxy, which matters because hole punching alone never gives a stranger a port. Closed source and supported through a QQ group, so durability is unproven. |
|---|
| Evidence note | documented The UDP hole punching and the relay quota statement are on the vendor page today; the daily traffic figure in the page title has no number behind it. |
|---|
| Parsed numbers | - has-free-tier 1
- price USD 0
|
|---|
Evidence 1
| date | source | what it proved |
|---|
| 2026-10-23 | natp2p.cn/ | TCP and UDP hole punching, reverse proxy, aggregated links; FAQ says P2P is not speed-limited and relay has a free quota |
More fields 6
| wg path | inside-udp |
|---|
| wg detail | The FAQ says P2P mode is not speed-limited and relay mode gives free users a quota; a WG datagram can be carried on a UDP tunnel, but P2P direct connection reaches only peers that joined the same room, not arbitrary internet clients. |
|---|
| ingress | udp |
|---|
| volume stated | The page title advertises daily free traffic without check-in, but no byte figure appears on the page body; the FAQ says relay-mode free users have a quota and P2P mode is unlimited in speed. |
|---|
| bytes transit | yes |
|---|
| transit note | Relay nodes carry proxied traffic; direct P2P carries its own. |
|---|
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