Pongery AS
BGP inherited
Cluster stats
Netblocks11
Cluster ID191636253
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 9 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
192.34.27.114/32 Pongery AS PEERINGDB ASSIGNED ● high
2001:504:125:e1::bb/128 Pongery AS PEERINGDB ASSIGNED ● high
2001:7f8:d0::3:de0:1/128 Pongery AS PEERINGDB ASSIGNED ● high
2400:9c80:0:173::200:160/128 Pongery AS PEERINGDB ASSIGNED ● high
2602:ffb1:200:0:192:34:27:114/128 Pongery AS PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:32::11f/128 Pongery AS PEERINGDB ASSIGNED ● high
2a0a:280:1100::/44 Pongery-AS RIPE ALLOCATED-BY-LIR ● low
2a0a:280:1110::/44 Pongery-AS RIPE ALLOCATED-BY-LIR ● low
2a0a:280:1120::/44 Pongery-AS RIPE ALLOCATED-BY-LIR ● low
2a0e:46c4:2810::/44 Pongery As RIPE ALLOCATED-BY-LIR ● low
2a0e:b107:bb4::/48 Pongery-SJC-US RIPE ASSIGNED ● low

Network trust

what's this?
RPKI hygiene: D how networks compare →
45.5% of checked blocks have valid RPKI ROA coverage (5 of 11)
Possible discrepancies (4)

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

2a0a:280:1100::/44 /44 authorized for AS200160 — Putu Paundrayana Waringin
2a0a:280:1110::/44 /44 authorized for AS200160 — Putu Paundrayana Waringin
2a0a:280:1120::/44 /44 authorized for AS200160 — Putu Paundrayana Waringin
2a0e:b107:bb4::/48 /48 authorized for AS200160 — Putu Paundrayana Waringin

NIC Handles

AS200160 ContentID DED3L-MNT DUMY-RIPE DUMY-RIPE MNT-DED3L ORG-PA1505-RIPE PONG-MNT nap-mnt