MX-IX Route Servers
BGP inherited
Cluster stats
Netblocks8
All fragments 109 blocks across 49 clusters
Cluster ID193387956
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-06

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.162.76.120/32 MX-IX Route Servers PEERINGDB ASSIGNED ● high
103.162.76.121/32 MX-IX Route Servers PEERINGDB ASSIGNED ● high
103.162.77.120/32 MX-IX Route Servers PEERINGDB ASSIGNED ● high
103.162.77.121/32 MX-IX Route Servers PEERINGDB ASSIGNED ● high
2001:df5:e880:1::251/128 MX-IX Route Servers PEERINGDB ASSIGNED ● high
2001:df5:e880:1::252/128 MX-IX Route Servers PEERINGDB ASSIGNED ● high
2001:df5:e880:2::251/128 MX-IX Route Servers PEERINGDB ASSIGNED ● high
2001:df5:e880:2::252/128 MX-IX Route Servers PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (4 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS141539