Route64
route64.org · 3 records in Compute, Egress and tunnels, IP and proxies · JSON
Records 3
- ★ qualifiesRoute64 (org)
Egress and tunnelsfree tieridentity emailno cardevidence documentedstale on 2026-11-23
- caveatROUTE64 (AS212895)
Computefree tieridentity emailno cardlimit per-ip-shapingevidence documentedstale on 2026-11-24
- caveatRoute64 (ipv4 blocks)
IP and proxiesidentity emailno cardevidence documentedstale on 2026-11-24
Route64 (org)
Egress and tunnels- Free allowance
- Route64 provides IPv6 tunnels with a routed /56 subnet, delivered through multiple tunnel protocols (WireGuard, GRE, IP6IP, etc.) to your endpoint.
- Verdict
- ★ qualifiesusable as stated; the read path was probed
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- documented2 sources; 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 | Route64 provides IPv6 tunnels with a routed /56 subnet, delivered through multiple tunnel protocols (WireGuard, GRE, IP6IP, etc.) to your endpoint. unit unlimited; metered on none |
|---|---|
| Price | USD 0 |
| Limits |
|
| Binding | none Nothing in the vocabulary fails at 1 TiB/month. There is no byte counter on the tunnelbroker, and the conditions page reserves throttling without naming a threshold. |
| Identity | email An account in the manager portal is required: the pricing block says 'Just created an account in our manager'. The sign-in page at manager.route64.org returned a login wall to the reader, so the exact fields a new account must supply were not readable. Email is the minimum such a portal implies and is not confirmed. |
| Egress | Traffic is not metered and it is possible to get more transit if 200M is not enough. (transit text) The IPv6 tunnelbroker page publishes no byte allowance at all; the conditions page says 'This is a free best effort service.'; ingress: tcp+udp free allowance: none published |
| Interface | cli self-service web portal generates the tunnel configuration; wg-quick applies it |
| Tooling | wg-quick plus the vendor portal; GRE/SIT/L2TPv3/VXLAN also offered |
| Composes with | a routed /56 over WireGuard gives a free VM with no public address 2^72 inbound IPv6 addresses; the VM supplies the CPU and a user supplies only a WireGuard handshake |
| Reliability | conditions: reject, cancel, throttle or nullroute at any time without warning; 200M best effort; flow-spec analysis; multiple accounts cause suspension of all. |
| Notes | The routed /56 is IPv6 only, so the inbound address is public but reachable only by clients that have IPv6. The /56 is routed to the tunnel endpoint, so the endpoint is what a user must already own: this composes with a free VM, it is not a substitute for one. UDP is carried because the prefix is routed IP, not a port forward; that is inferred from 'Subnet is route to your tunnel endpoint', not from a UDP sentence. |
| Evidence note | documented A live request from a client endpoint through a WireGuard tunnel to a service on the routed /56 would raise this to measured. Two things were read (home page, conditions page) and neither was probed. |
| Parsed numbers |
|
Evidence 2
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | route64.org/en | free /56 over WireGuard, the protocol table, 'Pricing? No!', and the config-sample sentence |
| 2026-10-23 | route64.org/en/tos | 'Our service is designed to deliver up to 200M throughput often more.', 'We can throttle your bandwidth at any time.', and the no-warning cancellation clauses |
More fields 6
| wg path | extractable |
|---|---|
| wg detail | No downloadable .conf is published. The self-service portal is the registration and the generator: 'Our system also generated configuration samples for tunnel config based on your information.' WireGuard is one of six offered protocols ('Wireguard yes yes' in the IPv4 and IPv6 endpoint table). |
| ingress | tcp+udp |
| volume stated | Traffic is not metered and it is possible to get more transit if 200M is not enough. (transit text) The IPv6 tunnelbroker page publishes no byte allowance at all; the conditions page says 'This is a free best effort service.' |
| bytes transit | yes |
| transit note | Route64's routers carry the tunnel traffic to and from its upstreams and peers |
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
ROUTE64 (AS212895)
Compute- Free allowance
- Free IPv6 tunnel with a routed /56 subnet over WireGuard, GRE, IP6IP, SIT, GRETAP, VXLAN or L2TPv3, self-service
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- per-ip-shapingup to 200 Mbit/s on the free transit
- Evidence
- documented4 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-24checked 2026-10-24 (live); stale on 2026-11-24
| Free tier | free IPv6 tunnel with a routed /56 subnet over WireGuard, GRE, IP6IP, SIT, GRETAP, VXLAN or L2TPv3, self-service unit unlimited; metered on none |
|---|---|
| Price | none stated |
| Limits | |
| Binding | per-ip-shaping 200 Mbit/s is the only published ceiling; there is no traffic meter, so throughput is the constraint and volume is not. |
| Identity | email the portal is described as self-service and fully automated; the registration form was not read, so whether an email address alone suffices is unverified. |
| Egress | free transit up to 200 Mbit/s, traffic not metered, more available on request or by donation free allowance: unmetered at up to 200 Mbit/s |
| Per-object cap | a routed /56 per tunnel endpoint, stated on the home page as 'IPv6 tunnels with a routed /56 subnet' |
| Retention | static IP allocations are stated to remain permanently assigned to the account; the portal was not opened, so what inactivity does to an allocation was not established |
| Interface | rest a self-service web portal that issues tunnel configs; not a machine, so there is no shell of its own |
| Tooling | the portal generates WireGuard configuration; any client can terminate the other end |
| Composes with | an IPv6 address space and a WireGuard peer for a machine that has no IPv6 of its own, which is a routing service and not a host |
| Reliability | no SLA is stated on the home page; the service is donation-funded |
| Notes | This is not a machine and cannot be one: it gives an address and a peer, and a user still needs something to terminate the tunnel on. It is recorded because it is the way an IPv6-only or CGNAT machine acquires a routable prefix. The egress topic owns the tunnel; this record covers only the address space. |
| Evidence note | documented the /56, the protocol list and the 200 Mbit/s cap are quoted from the home page read |
| Parsed numbers |
|
Evidence 4
| date | source | what it proved |
|---|---|---|
| 2026-10-24 | route64.org/en | quoted: 'Route64 provides IPv6 tunnels with a routed /56 subnet, delivered through multiple tunnel protocols (WireGuard, GRE, IP6IP, etc.) to your endpoint.' |
| 2026-10-24 | route64.org/en | quoted: 'Get free IPv4 / IPv6 transit for your network to bring your IP prefixes to the DFZ with up to 200M. Traffic is not metered' |
| 2026-10-24 | route64.org/en | quoted: 'Static IP allocations that remain permanently assigned to your account.' |
| 2026-10-24 | forsale.godaddy.com/forsale/route64.com | route64.com is a parked domain listed for sale; a request for route64.com redirected to the GoDaddy for-sale page, so the provider is route64.org and the .com is not it |
More fields 12
| shape | {"vcpu": null,"ram_gib": null,"disk_gib": null,"gpu_class": null,"gpu_count": null} |
|---|---|
| billing model | free, donation-funded |
| term | no term |
| m10h usd | 0 |
| m24h usd | 0 |
| price arithmetic | USD 0: the service is stated free of charge |
| free tier kind | free service |
| network out | {"allow_outbound": true,"allow_inbound_listen": true,"ports": "all on the routed prefix","static_ip": true,"ipv6": true,"per_session_bytes": null} |
| session cap | {"wall_clock_min": null,"idle_reap_s": null,"restart_required": false,"note": "not a machine"} |
| ipv6 prefix | /56 routed |
| renewal usd | USD 0 |
| renewal note | free service, donation-funded; no renewal step |
Route64 (ipv4 blocks)
IP and proxies- Free allowance
- Route64 provides the following services to you completely free of charge.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- not statedsee Price below
- Identity
- emailno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- documented8 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-24checked 2026-10-24 (live); stale on 2026-11-24
| Free tier | Route64 provides the following services to you completely free of charge. Static IPs: 'Need dedicated IPv4 and IPv6 addresses for your services? Route64 offers static IP allocations that remain permanently assigned to your account. Whether you need IPs for web hosting, mail servers, DNS infrastructure, or any other service, our static IPs are geographically flexible and can be deployed across multiple locations. All IP management is handled through our self-service portal.' The pricing block reads 'Pricing? No!' and 'Just created an account in our manager'. unit none; metered on none; The offer is denominated in addresses, a unit this enum does not carry, so the token is none rather than a byte or request unit. The vendor publishes neither a price nor a count of static IPs per account, and no page read on 2026-10-24 states how many addresses one account may hold. |
|---|---|
| Price | USD 0: the allocation and its traffic are both free, and no per-byte price exists at any tier |
| Limits |
No vocabulary kind fits the pool itself. AS212895 announces five IPv4 /24s, which is 1,280 addresses for the whole service, and the vendor's own page claims only '3 IPv4 /24 blocks'. No per-account count of static IPs is published at any tier. |
| Binding | none The ceiling that arrives first is structural and unclassified: 1,280 addresses in one ASN and one registration class. |
| Identity | email An account in the self-service manager portal is required: 'Just created an account in our manager.' The sign-in page at manager.route64.org returned a login wall to the reader, so the exact fields a new account must supply were not read; email is the minimum such a portal implies and is not confirmed. |
| Egress | No byte allowance and no traffic price is published for the static-IP product. free allowance: none published |
| Retention | not applicable: a static address, not stored bytes |
| Interface | unknown The reachable surface is the self-service web portal at manager.route64.org: 'All IP management is handled through our self-service portal.' No public API or CLI is documented, and manager.route64.org returned a login wall when read. |
| Tooling | An account in the self-service manager portal is the only published route to an allocation. No proxy wrapper, API client, downloadable configuration or test address is published for the static-IP product, so the announcing AS and the registration class cannot be checked before signing up. A missing wrapper is not a reason to reject this provider: what is missing here is the protocol and the test address, not the wrapper. |
| Composes with | It adds address count and one ASN, not registration-class diversity, because every address in the five blocks is IPXO-registered. |
| Reliability | Best effort with no SLA ('This is a free best effort service. You have no service levels or guarantees.'); all five blocks are one IPXO registration class and one announcing AS, so a prefix-level blocklist entry or a nullroute removes all 1,280 addresses together. |
| Notes | Route64 makes no class claim at all, so the class is settled entirely by the registry, and the registry does not support one: four blocks read IPXO or IPXO-LEASED as SUB-ALLOCATED PA or ASSIGNED PA, country EU, registrant ORG-PC1552-RIPE, with PC21176-RIPE 'Private Customer' as admin, tech and abuse contact and the remark 'End User Organization'. A sub-allocation of a lease broker's PA space is a broker's pool, not an eyeball broadband network, so rung 5 is not cleared. (2) That the announcement and the registration disagree, which is the topic's warning stated as a claim. Confirmed, and precisely: the announcement is Route64's own, since RIPE autnum 212895 is registered as ROUTE64_ORG and all five /24s are originated there and visible to 268 or 269 of 269 RIS peers, while the registration belongs to IPXO on four blocks and to an ARIN 'Private Customer' assignment on the fifth. Two parties, neither of them an ISP. That is a rung-5 failure, and it is not a rung-3 or rung-4 failure: the addresses are in five different /24s and in an ASN that is not AS13335, so both of those rungs are cleared by the measured announcement. (3) That the vendor's own block count can be relied on. Refuted: the page says 'Our address portfolio includes 3 IPv4 /24 blocks' and RIPEstat returned five, so the pool a user would draw from is 1,280 addresses rather than 768. That changes the size of the caveat, not its direction. A fourth finding belongs in the record rather than the notes: the vendor publishes a geofeed that carves single /24s into per-country fragments, a /28 in Stockholm, a /29 in London, /31s in Paris, Zurich and Frankfurt. A geofeed-aware upstream will read the declared country while RDAP still says EU, so the declared location is a vendor artifact and neither a registry fact nor a class. Every fact about the network rests on one read, on 2026-10-24: one announced-prefixes query, five routing-status queries, five RDAP queries, one geofeed fetch and two vendor pages. Nothing was delivered and nothing was echoed, and the instruction that matters for this record is that one delivered address must be measured before the class is relied on. That measurement is not here: it needs an account, an allocation, an echo service and a control request from a Cloudflare address in the same minute, and without it this record reports what the registry says rather than what an address does. This record does not duplicate egress/route64-org, which owns the free IPv6 /56 WireGuard tunnel and was read on 2026-10-23; this record owns the IPv4 static allocation only. Nothing in that record is corrected here, and the 200 Mbit/s design point and the provider sentences appear in both because they bind both products, each citing the provider directly. |
| Evidence note | documented The weakest link is the offer, not the registry. The five /24s, their announcing AS and their RDAP registration were measured with RIPEstat and RDAP on 2026-10-24, while the free allocation, the portal account and the absence of a byte quota are read from the vendor's own pages, and no address was delivered. |
Evidence 8
| date | source | what it proved |
|---|---|---|
| 2026-10-24 | route64.org/en | The static-IP offer ('Route64 offers static IP allocations that remain permanently assigned to your account', 'our static IPs are geographically flexible'), the free-of-charge sentence, 'Pricing? No!', the portal account requirement, and the vendor's own count: 'Our address portfolio includes 3 IPv4 /24 blocks and 78 IPv6 /48 blocks.' |
| 2026-10-24 | stat.ripe.net/data/announced-prefixes/data.json?resource=AS2 | AS212895 announces exactly five IPv4 /24s, 81.168.111.0/24, 192.208.1.0/24, 87.229.23.0/24, 81.18.58.0/24 and 79.175.70.0/24, alongside 96 IPv6 prefixes, so the page's '3 IPv4 /24 blocks' is not the current count. |
| 2026-10-24 | stat.ripe.net/data/routing-status/data.json?resource=81.18.5 | 81.18.58.0/24 is originated by AS212895 and seen by 268 of 269 RIS peers; the same query on the same run returned origin 212895 and 268 or 269 peers for 81.168.111.0/24, 192.208.1.0/24, 87.229.23.0/24 and 79.175.70.0/24, so all five are in the DFZ rather than merely registered. |
| 2026-10-24 | rdap.db.ripe.net/autnum/212895 | The announcing AS is Route64's own: AS212895 is registered as ROUTE64_ORG, status active, with an individual in Stuttgart, Germany, as registrant. The announcement is therefore not a leased transit AS, which is what separates this case from a transit-only prefix lease. |
| 2026-10-24 | rdap.org/ip/81.18.58.0 | The registration is not Route64's and is not an ISP's: name IPXO, type SUB-ALLOCATED PA, country EU, registrant ORG-PC1552-RIPE, administrative, technical and abuse contact PC21176-RIPE 'Private Customer', remark 'End User Organization'. The same query returned IPXO-LEASED-81-168-111-0-24 for 81.168.111.0/24, HGC-Global-Communications-Limited with IPXO details for 87.229.23.0/24, and IPXO with type ASSIGNED PA for 79.175.70.0/24. |
| 2026-10-24 | rdap.arin.net/registry/ip/192.208.1.0 | The fifth block is registered in a different registry and reads differently: ARIN handle NET-192-208-1-0-4, type ASSIGNMENT, parent NET-192-208-1-0-3, registrant C11060843 'Private Customer', with a remark pointing at the vendor's geofeed. No IPXO name appears on it, so the five blocks are not one uniform registration. |
| 2026-10-24 | manager.route64.org/data/geofeed.csv | The vendor declares location per sub-block inside single /24s: a /28 in Stockholm, a /29 in London, /31s in Paris, Zurich and Frankfurt, all inside 79.175.70.0/24. The country an address appears in is vendor-published, not a registry fact, and RDAP still reads EU for that block. |
| 2026-10-24 | route64.org/en/tos | The published ceilings and the reliability position: 'Our service is designed to deliver up to 200M throughput often more.', 'We can throttle your bandwidth at any time.', 'We can cancel any service at any time without any warning.', 'We can nullroute your advertised prefixes at any time without any warning.', 'This is a free best effort service. You have no service levels or guarantees.', 'Multiple accounts are not allowed and will cause the suspension of all accounts.' |
More fields 14
| rung | 4 |
|---|---|
| rung note | Five /24s originated by AS212895 clear rung 3, an address in a different /24, and rung 4, a network that is not AS13335; rung 5 is not cleared, because all five blocks are IPXO sub-allocations reading 'Private Customer'. |
| announced v4 blocks | ["81.168.111.0/24","192.208.1.0/24","87.229.23.0/24","81.18.58.0/24","79.175.70.0/24"] |
| address count | 1280 |
| announcing asn | AS212895 |
| announcing asn name | ROUTE64_ORG |
| vendor claimed v4 blocks | 3 IPv4 /24 blocks (page text, 2026-10-24), against five announced |
| registration | IPXO or IPXO-LEASED on four blocks, SUB-ALLOCATED PA or ASSIGNED PA, country EU, ORG-PC1552-RIPE, contact PC21176-RIPE 'Private Customer', remark 'End User Organization'; ARIN ASSIGNMENT NET-192-208-1-0-4 to C11060843 'Private Customer' on the fifth |
| geofeed url | https://manager.route64.org/data/geofeed.csv |
| geofeed note | single /24s are carved into per-country fragments, so the declared country is vendor-published and not a registry fact |
| transit cap | 200 Mbit/s design point, throttle at any time |
| derivation | 1,280 addresses is 5 x 256, arithmetic on the five /24s RIPEstat returned; 0.14 Mbit/s is 45 GB over 30 days; 2.16 TB/day is 200 Mbit/s. None of the three is a measurement. |
| verification gap | no address was delivered, so whether a delivered static IP is one of these five blocks, and whether it egresses from AS212895 as a usable exit, is unmeasured |
| duplicate of | egress/route64-org owns the IPv6 /56 tunnel product; this record owns IPv4 static allocation only |
Unknown values 2
- interface: the access interface was not established
- per object cap stated: the field does not apply to this kind of offer