NOKIA-SG3-EC-MHP-03-P
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 2 blocks across 2 clusters |
| Cluster ID | 207034362 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 27.111.235.40/30 | NOKIA-SG3-EC-MHP-03-P | APNIC | ALLOCATED NON-PORTABLE | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “NOKIA SG3 EC MHP 03” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- NOKIA-SG3-EC-MHP-03-S 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- NOKIASIEMENS-KCOM via British Telecommunications Limited sub-allocation
- NOKIA-ELEADER-SRV7 via Telia Cygate Oy sub-allocation
- Nokia Speedtest sub-allocation
- C 12265 DA Nokian Tyres via T-Mobile Czech Republic a.s. sub-allocation
- GTT-NOKIA-NETS sub-allocation
- Nokiaspzoo via TK Telekom sp. z o.o. sub-allocation
- NOKIA-NN sub-allocation
- Nokiantyres2 sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
No discrepancies found among checked blocks.
NIC Handles
AE131-AP
AG545-AP
AG545-AP
MAINT-AP-9989