Richmond
Richmond_net
Data as of 2026-07-26
Registry
Cluster stats
| Netblocks | 3 · 532 IPv4 addresses |
| All fragments | 48 blocks across 32 clusters |
| Cluster ID | 216492546 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 58.177.212.116/30 | RICHMOND | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 84.45.78.96/28 | Richmond | RIPE | ASSIGNED PA | ● low |
| 216.246.212.0/23 | Richmond_net | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(2 of 3)
Possible discrepancies (1)
These blocks are registered to Richmond_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.
| 216.246.212.0/23 /23 | authorized for AS205659 — UAB code200 |
NIC Handles
C4L-MNT
CH134-AP
DUMY-RIPE
DUMY-RIPE
MAINT-HK-CTI
SL113-AP
mnt-lt-code200-1