ONIX Route Servers
Cluster stats
Netblocks11
All fragments 36 blocks across 10 clusters
Cluster ID192152974
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
149.112.29.1/32 ONIX Route Servers PEERINGDB ASSIGNED ● high
149.112.29.2/32 ONIX Route Servers PEERINGDB ASSIGNED ● high
149.112.50.1/32 ONIX Route Servers PEERINGDB ASSIGNED ● high
149.112.50.2/32 ONIX Route Servers PEERINGDB ASSIGNED ● high
2001:504:125:e0::1/128 ONIX Route Servers PEERINGDB ASSIGNED ● high
2001:504:125:e0::2/128 ONIX Route Servers PEERINGDB ASSIGNED ● high
2001:504:125:e1::1/128 ONIX Route Servers PEERINGDB ASSIGNED ● high
2001:504:125:e1::2/128 ONIX Route Servers PEERINGDB ASSIGNED ● high
84.204.146.112/30 ONIX-LAN RIPE ASSIGNED PA ● low
195.56.108.200/29 ONIX-HU RIPE ASSIGNED PA ● low
2a14:4900:5902::/48 ONIX-IX RIPE ASSIGNED ● low

Network trust

what's this?
RPKI hygiene: D how networks compare →
27.3% of checked blocks have valid RPKI ROA coverage (3 of 11)
Possible discrepancies (1)

These blocks are registered to ONIX Route Servers 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.

2a14:4900:5902::/48 /48 authorized for AS215958 — FENGYE NETWORKS LIMITED

NIC Handles

AS3340-MNT AS57369 DUMY-RIPE DUMY-RIPE PSTAR-MNT hk-fengyecom-1-mnt