EdgeIX Route Servers
Cluster stats
| Netblocks | 30 |
| All fragments | 70 blocks across 2 clusters |
| Cluster ID | 193385909 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 | |
IP Ranges (30)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.136.100.1/32 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 103.136.100.2/32 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 103.136.100.129/32 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 103.136.101.1/32 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 103.136.101.126/32 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 103.136.102.1/32 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 103.136.102.2/32 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 103.136.103.1/32 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 103.136.103.2/32 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 103.180.190.1/32 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 103.180.190.2/32 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 202.77.88.1/32 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 202.77.88.2/32 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 202.77.90.1/32 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 202.77.90.2/32 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680::1/128 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680::2/128 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:1::1/128 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:2::1/128 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:2::2/128 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:3::1/128 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:3::2/128 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:4::1/128 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:4::2/128 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:5::1/128 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:5::2/128 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:6::1/128 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:6::2/128 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:11::1/128 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:11::2/128 | EdgeIX Route Servers | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
20.0%
of checked blocks have valid RPKI ROA coverage
(6 of 30)
No discrepancies found among checked blocks.
NIC Handles
AS24224