SIDNET-ID
Data as of 2026-07-26
BGP inherited
Limited data: only 1 range 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 | 1 |
| IPv6 | 1 prefix (largest 2001:df2:ffc0::/48) |
| Cluster ID | 213860246 |
| 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 (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2001:df2:ffc0::/48 | SIDNET-ID | APNIC | ASSIGNED PORTABLE | ● medium |
IPv6 ranges (1)
| CIDR |
|---|
| 2001:df2:ffc0::/48 |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
Possible discrepancies (1)
These blocks are registered to SIDNET TELECOM 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.
| 2001:df2:ffc0::/48 /48 | authorized for AS150923 — PT Sistem Interkoneksi Data |
NIC Handles
MARP1-AP
MARP1-AP
MNT-APJII-ID