Pmman Network
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 4 |
| IPv6 | 4 prefixes (largest 2602:f429:31::20/128) |
| Cluster ID | 214594751 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
2 weekly snapshots · JSON
8
0 netblocks since 2026-07-13
2026-07-13
peak 8
2026-07-19
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2602:f429:31::20/128 | Pmman Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f92a:1315:2::98/128 | Pmman Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:9::13c/128 | Pmman Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:16::143/128 | Pmman Network | PEERINGDB | ASSIGNED | ● high |
IPv6 ranges (4)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(2 of 4)
No discrepancies found among checked blocks.
NIC Handles
AS219332