NO-NEANETT-ACCESS
Handle
Cluster stats
| Netblocks | 4 |
| All fragments | 16,960 blocks across 6,608 clusters |
| Cluster ID | 193711208 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 31.186.90.96/27 | NO-NEANETT-ACCESS | RIPE | ASSIGNED PA | ● low |
| 31.186.90.128/25 | NO-NEANETT-ACCESS | RIPE | ASSIGNED PA | ● low |
| 31.186.91.0/24 | NO-NEANETT-ACCESS | RIPE | ASSIGNED PA | ● low |
| 31.186.92.0/22 | NO-NEANETT-ACCESS | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (2)
These blocks are registered to NO-NEANETT-ACCESS but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 31.186.92.0/22 /22 | authorized for AS31020 — NTE TELEKOM AS |
| 31.186.91.0/24 /24 | authorized for AS31020 — NTE TELEKOM AS |
NIC Handles
DUMY-RIPE
DUMY-RIPE
NEANETT-LIR