3L CLOUD INTERNET SERVICES

Data as of 2026-09-13
BGP inherited
This organisation
Netblocks10
IPv6 5 prefixes (largest 2001:12f8:0:13::37/128)
Also registered under this name 25 netblocks across 2 separate records
Record ID242146686
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.73.14/32 3L CLOUD INTERNET SERVICES PEERINGDB ASSIGNED ● high
45.184.144.37/32 3L CLOUD INTERNET SERVICES PEERINGDB ASSIGNED ● high
45.184.146.66/32 3L CLOUD INTERNET SERVICES PEERINGDB ASSIGNED ● high
187.16.208.198/32 3L CLOUD INTERNET SERVICES PEERINGDB ASSIGNED ● high
187.16.212.238/32 3L CLOUD INTERNET SERVICES PEERINGDB ASSIGNED ● high
2001:12f8::208:198/128 3L CLOUD INTERNET SERVICES PEERINGDB ASSIGNED ● high
2001:12f8::212:238/128 3L CLOUD INTERNET SERVICES PEERINGDB ASSIGNED ● high
2001:12f8:0:4::66/128 3L CLOUD INTERNET SERVICES PEERINGDB ASSIGNED ● high
2001:12f8:0:9::145:14/128 3L CLOUD INTERNET SERVICES PEERINGDB ASSIGNED ● high
2001:12f8:0:13::37/128 3L CLOUD INTERNET SERVICES PEERINGDB ASSIGNED ● high

IPv6 ranges (5)

Footprint over time

12 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-09-13

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

AS266444