CIRA-CLOUD1
Data as of 2026-09-06
Handle
This organisation
| Netblocks | 41 |
| IPv6 | 20 prefixes (largest 2001:12f8::222:98/128) |
| Registered in | Canada (5) · United Kingdom (2) · Australia (2) · France (2) · Singapore (2) · Czechia (1) |
| Record ID | 239843665 |
| Registry | PEERINGDB |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (41)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 5.57.81.125/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 27.111.230.240/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 37.49.238.107/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 45.120.248.230/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 45.183.47.23/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 103.16.102.44/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 103.26.71.167/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 103.231.152.57/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 185.0.20.135/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 187.16.222.98/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 195.42.145.8/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 195.66.226.79/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 196.60.10.29/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 206.71.11.32/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 206.72.208.6/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 206.72.211.14/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 206.108.34.219/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 206.126.225.30/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 206.130.15.5/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 217.29.67.191/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 218.100.78.139/32 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:504:13::211:14/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:504:1a::34:219/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:504:26::5:5195:1/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:504:2f::5:5195:2/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:504:37:10::50/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:504:69:8000::32/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:4::d79b:1/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:b:100:1d1:a5d5:5195:191/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:17::d79b:1/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:43::5:5195:2/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:54::2:107/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:7f::135/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:11:1:0:d79b:0:1/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:4::5:5195:1/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:12:100::44/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:dea:0:30::a7/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:df2:1900:1::230/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:df5:b800:bb00:0:5:5195:1/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8::222:98/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
| 2001:43f8:6d0::10:29/128 | CIRA-CLOUD1 | PEERINGDB | ASSIGNED | ● high |
IPv6 ranges (20)
showing the 15 largest allocationsFootprint over time
6 weekly snapshots · JSON
41
+3 netblocks since 2026-07-26
2026-07-26
peak 41
2026-09-06
Network trust
what's this?
RPKI hygiene: B
how networks compare →
80.5%
of checked blocks have valid RPKI ROA coverage
(33 of 41)
No discrepancies found among checked blocks.
NIC Handles
AS55195