DIAMOND STATE NETWORKS
Cluster stats
| Netblocks | 19 |
| All fragments | 177 blocks across 79 clusters |
| Cluster ID | 191659478 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 13 shared RIR contact/maintainer handles |
| Registry names | 8 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (19)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 23.136.136.0/24 | DIAMOND STATE NETWORKS, LLC | BGP | ANNOUNCED | ● high |
| 58.185.200.176/30 | DIAMOND-SG | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 58.185.200.184/29 | DIAMOND-SG | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 66.33.24.0/21 | DIAMOND STATE NETWORKS, LLC | BGP | ANNOUNCED | ● high |
| 66.33.80.0/21 | DIAMOND STATE NETWORKS, LLC | BGP | ANNOUNCED | ● high |
| 203.125.25.84/30 | DIAMOND-SG | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 206.51.7.252/32 | DIAMOND STATE NETWORKS | PEERINGDB | ASSIGNED | ● high |
| 206.53.202.166/32 | DIAMOND STATE NETWORKS | PEERINGDB | ASSIGNED | ● high |
| 206.71.12.121/32 | DIAMOND STATE NETWORKS | PEERINGDB | ASSIGNED | ● high |
| 2001:504:1b:1::252/128 | DIAMOND STATE NETWORKS | PEERINGDB | ASSIGNED | ● high |
| 2001:504:40:12::1:121/128 | DIAMOND STATE NETWORKS | PEERINGDB | ASSIGNED | ● high |
| 2001:504:61:0:6:1b12:0:1/128 | DIAMOND STATE NETWORKS | PEERINGDB | ASSIGNED | ● high |
| 2606:d240::/32 | DIAMOND STATE NETWORKS, LLC | BGP | ANNOUNCED | ● high |
| 58.185.187.128/28 | DIAMOND-GAS-SG | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 88.116.128.240/29 | DIAMOND-HWY-AT | RIPE | ASSIGNED PA | ● low |
| 193.62.220.0/22 | DIAMOND-UK | RIPE | ASSIGNED PA | ● low |
| 195.210.168.120/29 | DIAMOND-LED | RIPE | ASSIGNED PA | ● low |
| 2001:630:6d::/48 | DIAMOND-UK | RIPE | ASSIGNED | ● low |
| 2a00:2381:2673::/48 | DIAMOND-AND | RIPE | AGGREGATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
94.7%
of checked blocks have valid RPKI ROA coverage
(18 of 19)
Possible discrepancies (3)
These blocks are registered to DIAMOND STATE NETWORKS but cryptographically authorized for a different, unrelated network (2 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a00:2381:2673::/48 /48 | authorized for AS2856 — British Telecommunications PLC |
| 2001:630:6d::/48 /48 | authorized for AS786 — Jisc Services Limited |
| 193.62.220.0/22 /22 | authorized for AS786 — Jisc Services Limited |
NIC Handles
AS2068-AP
AS400146
AS400146
AS8447-MNT
BTNET-MNT
DUMY-RIPE
DUMY-RIPE
JANET-HOSTMASTER
MAINT-SG-SINGNET
MTU-NOC
RN243-AP
SH9-AP
+1 more