APULS

BGP inherited
Cluster stats
Netblocks7 · 1,785 IPv4 addresses
Cluster ID212104586
RegistryAPNIC
Customersfind 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

Footprint over time

5 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.113.104.0/24 APULS APNIC ALLOCATED NON-PORTABLE ● low
45.113.105.0/24 APULS APNIC ALLOCATED NON-PORTABLE ● low
45.113.107.0/24 APULS APNIC ALLOCATED NON-PORTABLE ● low
103.238.12.0/24 APULS APNIC ALLOCATED NON-PORTABLE ● low
103.238.13.0/24 APULS APNIC ALLOCATED NON-PORTABLE ● low
103.238.14.0/24 APULS APNIC ALLOCATED NON-PORTABLE ● low
103.238.15.0/24 APULS 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.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
RPKI-inferred operator Ishan's Network
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

IA180-AP IT137-AP MAINT-IN-IRINN