MX-IX Route Servers
Data as of 2026-08-23
BGP inherited
Cluster stats
| Netblocks | 16 |
| IPv6 | 8 prefixes (largest 2001:df5:e880:1::251/128) |
| Cluster ID | 229180781 |
| Registry | PEERINGDB |
| Customers | find 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 · report an issue | |
Footprint over time
9 weekly snapshots · JSON
16
+8 netblocks since 2026-07-05
2026-07-05
peak 16
2026-08-23
IP Ranges (16)
⬇ 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.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 |
IPv6 ranges (8)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(8 of 16)
No discrepancies found among checked blocks.
NIC Handles
AS141539