One Pay
ONEPAY-NET
Registry
Cluster stats
| Netblocks | 4 |
| All fragments | 9 blocks across 3 clusters |
| Cluster ID | 211324201 |
| 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 | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 91.147.95.32/28 | OnePay | RIPE | ASSIGNED PA | ● high |
| 123.30.6.64/27 | ONEPAY-NET | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 222.255.251.4/30 | ONEPAY-NET | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 2a00:2381:3793::/48 | ONEPAY-LIMITED | RIPE | AGGREGATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (1)
These blocks are registered to One Pay 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.
| 2a00:2381:3793::/48 /48 | authorized for AS2856 — British Telecommunications Limited |
NIC Handles
BTNET-MNT
DUMY-RIPE
DUMY-RIPE
MAINT-VN-VNPT
MNT-PS
ORG-PSKZ1587-RIPE
PDQ2-AP
PDQ2-AP