MX-IX Route Servers

Data as of 2026-09-20
BGP inherited
This organisation
Netblocks20
IPv6 10 prefixes (largest 2001:df5:e880:1::251/128)
Record ID242194589
RegistryPEERINGDB
Customerssee who runs inside 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 · report an issue

IP Ranges (20)

⬇ 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.76.151/32 MX-IX Route Servers PEERINGDB ASSIGNED ● high
103.162.76.152/32 MX-IX Route Servers PEERINGDB ASSIGNED ● high
103.162.76.210/32 MX-IX Route Servers PEERINGDB ASSIGNED ● high
103.162.76.220/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
103.162.77.251/32 MX-IX Route Servers PEERINGDB ASSIGNED ● high
103.162.77.252/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
2001:df5:e880:3::251/128 MX-IX Route Servers PEERINGDB ASSIGNED ● high
2001:df5:e880:3::252/128 MX-IX Route Servers PEERINGDB ASSIGNED ● high
2001:df5:e880:4::251/128 MX-IX Route Servers PEERINGDB ASSIGNED ● high
2001:df5:e880:4::252/128 MX-IX Route Servers PEERINGDB ASSIGNED ● high
2001:df5:e880:5::210/128 MX-IX Route Servers PEERINGDB ASSIGNED ● high
2001:df5:e880:5::220/128 MX-IX Route Servers PEERINGDB ASSIGNED ● high

IPv6 ranges (10)

Footprint over time

13 weekly snapshots · JSON
20 +12 netblocks since 2026-07-05
2026-07-05 peak 20 2026-09-20

Network trust

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

NIC Handles

AS141539