Fast Could
PUMO-NET
Registry
Cluster stats
| Netblocks | 6 · 12,411 IPv4 addresses |
| Cluster ID | 206735006 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
4 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-13
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 202.153.203.128/25 | Pumo | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 103.20.40.0/22 | PUMO-NET | APNIC | ALLOCATED PORTABLE | ● low |
| 103.133.44.0/22 | PUMO-NET | APNIC | ALLOCATED PORTABLE | ● low |
| 124.150.128.0/21 | PUMO-NET | APNIC | ALLOCATED PORTABLE | ● low |
| 223.27.32.0/19 | PUMO-NET | APNIC | ALLOCATED PORTABLE | ● low |
| 2400:b380::/32 | PUMO-NET | APNIC | ALLOCATED PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
83.3%
of checked blocks have valid RPKI ROA coverage
(5 of 6)
Possible discrepancies (4)
These blocks are registered to PUMO-NET 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.
| 2400:b380::/32 /32 | authorized for AS38843 — FastCould |
| 223.27.32.0/19 /19 | authorized for AS38843 — FastCould |
| 124.150.128.0/21 /21 | authorized for AS38843 — FastCould |
| 103.20.40.0/22 /22 | authorized for AS38843 — FastCould |
NIC Handles
AS1152-AP
AS1152-AP
AT939-AP
AU223-AP
LC1857-AP
LC1857-AP
MAINT-TW-TWNIC
MAINT-TW-UNIGATE