NEC-SG
Data as of 2026-07-26
BGP inherited
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 · 4,120 IPv4 addresses |
| Cluster ID | 213265655 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 118.201.43.208/29 | NEC-SG | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 203.127.240.0/20 | NEC-SG | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 116.12.238.176/28 | NEC-SG | APNIC | ALLOCATED NON-PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (1)
These blocks are registered to NEC-SG 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.
| 203.127.240.0/20 /20 | authorized for AS3758 — SingNet Pte Ltd |
NIC Handles
AS2068-AP
FF225-AP
KL1271-AP
MAINT-SG-SINGNET
SH9-AP
SH9-AP