Pmman Network
Cluster stats
| Netblocks | 5 |
| All fragments | 9 blocks across 3 clusters |
| Cluster ID | 191838033 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 4 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2602:f429:31::20/128 | Pmman Network | PEERINGDB | ASSIGNED | ● high |
| 2a0a:d685:300::/48 | PMMAN-JP | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:4700::/48 | PMMAN-JP | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:4701::/48 | PMMAN-CN | RIPE | ASSIGNED | ● low |
| 2a0f:1cc5:4702::/48 | PMMAN-HK | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
20.0%
of checked blocks have valid RPKI ROA coverage
(1 of 5)
Possible discrepancies (1)
These blocks are registered to Pmman Network 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:d685:300::/48 /48 | authorized for AS219332 — MOEDOVE-MNT |
NIC Handles
AS219332
DUMY-RIPE
DUMY-RIPE
PMMAN-MNT