NGF
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 5 blocks across 2 clusters |
| Cluster ID | 191888032 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.95.12.128/30 | NGF-NET | RIPE | ASSIGNED PA | ● low |
| 93.117.202.187/32 | NGF | RIPE | ASSIGNED PA | ● low |
| 193.89.240.0/24 | NGF | RIPE | ASSIGNED PA | ● low |
| 212.243.37.80/29 | NGF-NET | 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 (1)
These blocks are registered to NGF 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.
| 193.89.240.0/24 /24 | authorized for AS3292 — TDC Holding A/S |
NIC Handles
CH-UNISOURCE-MNT
DK-NIC
DUMY-RIPE
DUMY-RIPE
TDC-SE-MNT
TNF-MNT