NEP Connect
Cluster stats
| Netblocks | 16 |
| All fragments | 66 blocks across 10 clusters |
| Cluster ID | 192626992 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (16)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.249.210.97/32 | NEP Connect | PEERINGDB | ASSIGNED | ● high |
| 80.249.211.216/32 | NEP Connect | PEERINGDB | ASSIGNED | ● high |
| 193.239.116.180/32 | NEP Connect | PEERINGDB | ASSIGNED | ● high |
| 193.239.116.181/32 | NEP Connect | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a503:4756:1/128 | NEP Connect | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a503:4756:2/128 | NEP Connect | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:13::a503:4756:1/128 | NEP Connect | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:13::a503:4756:2/128 | NEP Connect | PEERINGDB | ASSIGNED | ● high |
| 62.216.225.12/30 | NEP_CONNECT_LTD | RIPE | ASSIGNED PA | ● low |
| 80.85.67.136/30 | NEP_CONNECT_LTD | RIPE | ASSIGNED PA | ● low |
| 85.233.200.24/30 | NEP_CONNECT_LTD | RIPE | ASSIGNED PA | ● low |
| 217.163.31.176/28 | NEP-CONNECT-LIMITED | RIPE | ASSIGNED PA | ● low |
| 2001:4d78:104:38::/64 | NEP_CONNECT_LTD | RIPE | ASSIGNED | ● low |
| 2001:4d78:104:6a::/64 | NEP_CONNECT_LTD | RIPE | ASSIGNED | ● low |
| 2001:4d78:630:1f::/64 | NEP_CONNECT_LTD | RIPE | ASSIGNED | ● low |
| 2a07:aa00:84::/48 | NEP-CONNECT-LIMITED | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
87.5%
of checked blocks have valid RPKI ROA coverage
(14 of 16)
No discrepancies found among checked blocks.
NIC Handles
AB34802-RIPE
AS34756
DUMY-RIPE
DUMY-RIPE
EQUINIX-FULFIL-MNT
EQUINIX-MNT
LEVEL3-MNT
QUZAUK