ROUTE64.ORG

Data as of 2026-08-23
Registry
Cluster stats
Netblocks79
IPv6 42 prefixes (largest 2a11:6c7:1000::/36)
Registered in United States (7) · Netherlands (6) · Switzerland (6) · France (5) · Poland (3) · United Kingdom (2)
Cluster ID226991074
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

9 weekly snapshots · JSON
79 +10 netblocks since 2026-07-05
2026-07-05 peak 79 2026-08-23

IP Ranges (79)

showing 50 of 79 — see all — ⬇ export CSV
CIDR Org name Registry Status Confidence
5.57.82.178/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
31.44.186.226/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
37.49.238.244/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
80.249.213.228/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
149.112.29.110/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
149.112.50.104/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
149.112.60.56/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
149.112.75.14/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
149.112.96.247/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
178.18.237.24/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.0.2.95/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.0.15.13/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.0.27.64/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.0.30.40/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.0.42.35/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.1.14.86/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.1.14.183/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.1.14.196/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.1.59.171/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.1.114.126/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.1.136.22/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.1.144.27/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.1.147.220/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.1.147.221/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.1.152.53/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.1.160.101/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.1.222.163/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
185.1.240.134/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
192.34.27.59/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
193.189.82.247/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
193.239.119.183/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
194.153.153.86/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
194.153.158.76/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
194.180.226.95/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
195.60.91.138/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
206.51.7.97/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
206.81.80.247/32 ROUTE64.ORG PEERINGDB ASSIGNED ● high
2001:504:16::3:3f9f/128 ROUTE64.ORG PEERINGDB ASSIGNED ● high
2001:504:16:1::3:3f9f/128 ROUTE64.ORG PEERINGDB ASSIGNED ● high
2001:504:1b:1::97/128 ROUTE64.ORG PEERINGDB ASSIGNED ● high
2001:504:125:e0::110/128 ROUTE64.ORG PEERINGDB ASSIGNED ● high
2001:504:125:e1::104/128 ROUTE64.ORG PEERINGDB ASSIGNED ● high
2001:504:125:e2::56/128 ROUTE64.ORG PEERINGDB ASSIGNED ● high
2001:7f8:1:0:a500:21:2895:1/128 ROUTE64.ORG PEERINGDB ASSIGNED ● high
2001:7f8:13::a521:2895:2/128 ROUTE64.ORG PEERINGDB ASSIGNED ● high
2001:7f8:17::3:3f9f:1/128 ROUTE64.ORG PEERINGDB ASSIGNED ● high
2001:7f8:33::a121:2895:1/128 ROUTE64.ORG PEERINGDB ASSIGNED ● high
2001:7f8:54::2:244/128 ROUTE64.ORG PEERINGDB ASSIGNED ● high
2001:7f8:54:8::27/128 ROUTE64.ORG PEERINGDB ASSIGNED ● high
2001:7f8:a9::76/128 ROUTE64.ORG PEERINGDB ASSIGNED ● high

IPv6 ranges (42)

showing the 15 largest allocations
CIDR
2a11:6c7:1000::/36
2a11:6c7:2000::/36
2a11:6c7:3000::/36
2a11:6c7:4000::/36
2a11:6c7:5000::/36
2a11:6c7::/36
2001:504:125:e0::110/128
2001:504:125:e1::104/128
2001:504:125:e2::56/128
2001:504:16:1::3:3f9f/128
2001:504:16::3:3f9f/128
2001:504:1b:1::97/128
2001:7f8:10f::3:3f9f:101/128
2001:7f8:115:1::35/128
2001:7f8:11c:1:0:21:2895:1/128

Network trust

what's this?
RPKI hygiene: C how networks compare →
60.8% of checked blocks have valid RPKI ROA coverage (48 of 79)
Possible discrepancies (6)

These blocks are registered to ROUTE64.ORG but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a11:6c7::/36 /36 authorized for AS212895 — Johannes Ernst
2a11:6c7:1000::/36 /36 authorized for AS212895 — Johannes Ernst
2a11:6c7:2000::/36 /36 authorized for AS212895 — Johannes Ernst
2a11:6c7:3000::/36 /36 authorized for AS212895 — Johannes Ernst
2a11:6c7:4000::/36 /36 authorized for AS212895 — Johannes Ernst
2a11:6c7:5000::/36 /36 authorized for AS212895 — Johannes Ernst

NIC Handles

AS212895 DUMY-RIPE DUMY-RIPE ORG-FA1162-RIPE SERVERGURUS-MNT VM-JE VM_JE lir-de-servergurus-1-MNT