SingNet Pte Ltd
NEP-SINGAPORE-SG
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 2 blocks across 2 clusters |
| Cluster ID | 207743734 |
| 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 |
|---|---|---|---|---|
| 42.61.113.56/29 | NEP-SINGAPORE-SG | APNIC | ALLOCATED NON-PORTABLE | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “NEP SINGAPORE” — 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.
- NEP-Singapore-Pte-Ltd 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.
- Permanent-Mission-of-Singapore via T-Mobile Austria GmbH sub-allocation
- singapore-msk-net sub-allocation
- Singapore Network sub-allocation
- EXPEREOSINGAPORE via NOS COMUNICACOES, S.A. sub-allocation
- Singapore Econo Devel Board via Orange S.A. sub-allocation
- Singapore-Lumileds sub-allocation
- Singapore Airlines via COLT Technology Services Group Limited sub-allocation
- Draeger Singapore Pte Ltd via COLT Technology Services Group Limited 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
AS2068-AP
MAINT-SG-SINGNET
SH9-AP
SH9-AP