pnb

BGP inherited
Cluster stats
Netblocks6
Registered in United Kingdom (2) · BT (1) · Netherlands (1) · Philippines (1)
All fragments 13 blocks across 7 clusters
Cluster ID209340650
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 14 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-12

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.137.77.24/29 pnb RIPE ASSIGNED PA ● low
93.117.228.96/28 PNB RIPE ASSIGNED PA ● low
119.2.116.64/28 PNB-NET APNIC ASSIGNED NON-PORTABLE ● low
126.209.9.112/29 PNB-Holdings-Corporation APNIC ALLOCATED NON-PORTABLE ● low
217.36.252.0/29 pnb RIPE ASSIGNED PA ● low
2a03:2880:1300::/40 PNB RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “pnb” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
Possible discrepancies (1)

These blocks are registered to pnb 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.

2a03:2880:1300::/40 /40 authorized for AS32934 — Facebook, Inc.

NIC Handles

AB1276-AP AI782-AP BTNET-MNT DUMY-RIPE DUMY-RIPE IIA37-AP IIA37-AP JT106-AP JT106-AP MAINT-BT-DRUKNET MAINT-INFINIVAN-PH TNF-MNT +2 more