CLOUDITY Network
Data as of 2026-09-06
BGP inherited
This organisation
| Netblocks | 5 |
| IPv6 | 4 prefixes (largest 2a05:9f00::/31) |
| Record ID | 236602157 |
| Registry | PEERINGDB |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 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 (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.1.222.91/32 | CLOUDITY Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:b7::a504:4222:1/128 | CLOUDITY Network | PEERINGDB | ASSIGNED | ● high |
| 2a05:9f00::/31 | CLOUDITY-IPv6 | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a05:9f02::/31 | CLOUDITY-IPv6 | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a05:9f04::/31 | CLOUDITY-Network-V6 | RIPE | ALLOCATED-BY-LIR | ● low |
IPv6 ranges (4)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
60.0%
of checked blocks have valid RPKI ROA coverage
(3 of 5)
Possible discrepancies (3)
These blocks are registered to CLOUDITY Network 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.
| 2a05:9f00::/31 /31 | authorized for AS44222 — Nuno Felgueiras |
| 2a05:9f02::/31 /31 | authorized for AS44222 — Nuno Felgueiras |
| 2a05:9f04::/31 /31 | authorized for AS44222 — Nuno Felgueiras |
NIC Handles
AS44222
CLOUDITY
DUMY-RIPE
DUMY-RIPE