ASAHI-SG
BGP inherited
Cluster stats
| Netblocks | 5 |
| Cluster ID | 211848983 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 58.185.193.112/28 | ASAHI-SG | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 116.12.190.192/28 | ASAHI-SG | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 203.125.4.0/29 | ASAHI-SG | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 203.126.85.80/29 | ASAHI-SG | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 203.125.10.8/29 | ASAHI-SG | APNIC | ALLOCATED NON-PORTABLE | ● low |
Possibly related to this organisation
what's this?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.
- SINGAPOREASAHI-SG via M1 NET LTD sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(5 of 5)
No discrepancies found among checked blocks.
NIC Handles
AS2068-AP
CYS19-AP
FC985-AP
LJJ136-AP
MAINT-SG-SINGNET
SH9-AP
SH9-AP
TM824-AP