GNM-IX Route Servers
Cluster stats
| Netblocks | 16 |
| All fragments | 96 blocks across 3 clusters |
| Cluster ID | 193387180 |
| 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 (16)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 178.18.226.131/32 | GNM-IX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 178.18.226.133/32 | GNM-IX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 178.18.230.90/32 | GNM-IX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 178.18.230.91/32 | GNM-IX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 178.18.233.1/32 | GNM-IX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 178.18.233.6/32 | GNM-IX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 178.18.237.29/32 | GNM-IX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 178.18.237.30/32 | GNM-IX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::226:131/128 | GNM-IX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::226:133/128 | GNM-IX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4:1::233:1/128 | GNM-IX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4:1::233:6/128 | GNM-IX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4:2::237:29/128 | GNM-IX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4:2::237:30/128 | GNM-IX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:7::230:90/128 | GNM-IX Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:7::230:91/128 | GNM-IX Route Servers | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
37.5%
of checked blocks have valid RPKI ROA coverage
(6 of 16)
No discrepancies found among checked blocks.
NIC Handles
AS50952