route

BGP inherited
Cluster stats
Netblocks7
Registered in Israel (5) · China (1) · Finland (1)
All fragments 78 blocks across 20 clusters
Cluster ID209394220
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
222.66.54.156/30 ROUTE-CO APNIC ASSIGNED NON-PORTABLE ● high
192.194.30.128/27 ROUTE-NET RIPE ASSIGNED PA ● low
212.150.173.240/29 route RIPE ASSIGNED PA ● low
212.150.185.20/30 Route RIPE ASSIGNED PA ● low
212.235.57.104/29 route RIPE ASSIGNED PA ● low
212.235.69.128/29 route RIPE ASSIGNED PA ● low
212.235.93.8/30 route RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “route” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Combined view of all 20 name-family clusters →
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

DATANET-NOC DUMY-RIPE DUMY-RIPE MAINT-CHINANET-SH NV-MNT-RIPE YXW6-AP YXW6-AP