JUPITER-ID
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 · 2,558 IPv4 addresses |
| Cluster ID | 213553322 |
| 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 | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.155.186.0/23 | JUPITER-ID | APNIC | ALLOCATED PORTABLE | ● low |
| 202.93.240.0/21 | JUPITER-ID | APNIC | ALLOCATED PORTABLE | ● low |
| 2402:b240::/32 | JUPITER-ID | APNIC | ALLOCATED PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
33.3%
of checked blocks have valid RPKI ROA coverage
(1 of 3)
Possible discrepancies (1)
These blocks are registered to Jupiter 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.
| 103.155.186.0/23 /23 | authorized for AS24198 — PT. Dutakom Wibawa Putra |
NIC Handles
DWP88-ID
DWP88-ID
MNT-APJII-ID