IDNIC-UPAZNET-ID
Data as of 2026-07-26
BGP inherited
Limited data: only 2 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 | 2 · 512 IPv4 addresses |
| IPv6 | 1 prefix (largest 2001:df1:1ec0::/48) |
| Cluster ID | 213581107 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 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 (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.111.118.0/23 | IDNIC-UPAZNET-ID | APNIC | ALLOCATED PORTABLE | ● low |
| 2001:df1:1ec0::/48 | IDNIC-UPAZNET-ID | APNIC | ASSIGNED PORTABLE | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2001:df1:1ec0::/48 |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
RPKI-inferred operator
PT Dimensi Jaringan Bersinar
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
AM3512-AP
AM3512-AP
MNT-APJII-ID