Pacific Networks

Data as of 2026-09-06
BGP inherited
This organisation
Netblocks8 · 514 IPv4 addresses
IPv6 4 prefixes (largest 2001:df5:6d40::/44)
Record ID236970914
RegistryAPNIC
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.25.228.21/32 Pacific Networks PEERINGDB ASSIGNED ● high
103.25.228.22/32 Pacific Networks PEERINGDB ASSIGNED ● high
103.101.192.0/24 Pacific Networks BGP ANNOUNCED ● high
2001:dec:0:1::21/128 Pacific Networks PEERINGDB ASSIGNED ● high
2001:dec:0:1::22/128 Pacific Networks PEERINGDB ASSIGNED ● high
2001:df2:a700::/48 Pacific Networks BGP ANNOUNCED ● high
103.65.141.0/24 Pacific Networks APNIC ALLOCATED PORTABLE ● low
2001:df5:6d40::/44 Pacific Networks APNIC ASSIGNED PORTABLE ● low

IPv6 ranges (4)

Footprint over time

11 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-09-06

Network trust

what's this?
RPKI hygiene: C how networks compare →
70.0% of checked blocks have valid RPKI ROA coverage (7 of 10)
Possible discrepancies (1)

These blocks are registered to Pacific Networks 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.65.141.0/24 /24 authorized for AS153346 — HawkNet Labs Pty Ltd

NIC Handles

AP874-AP APNIC-HM AS136996 AS136996 ORG-PN2-AP PNA22-AP PNA22-AP