Clean Net Telecom

Aggregated across every cluster whose name starts with "Clean Net Telecom" — a single company can be split across many separate clusters (per-datacenter, per-country, or per-subsidiary naming), so this view sums the true total rather than understating it with a single cluster's count.

22
Total ranges
2
Matched clusters

Matched clusters

Ranges (22)

showing 1–22 of 22 — ⬇ export CSV
CIDR Org name Cluster Registry Status
45.238.128.0/22 Clean Net Telecom Ltda Clean Net Telecom Ltda BGP ANNOUNCED
177.10.0.0/20 Clean Net Telecom Ltda Clean Net Telecom Ltda BGP ANNOUNCED
177.10.0.0/21 Clean Net Telecom Ltda Clean Net Telecom Ltda BGP ANNOUNCED
177.10.0.0/22 Clean Net Telecom Ltda Clean Net Telecom Ltda BGP ANNOUNCED
177.10.4.0/22 Clean Net Telecom Ltda Clean Net Telecom Ltda BGP ANNOUNCED
177.10.8.0/21 Clean Net Telecom Ltda Clean Net Telecom Ltda BGP ANNOUNCED
177.10.8.0/22 Clean Net Telecom Ltda Clean Net Telecom Ltda BGP ANNOUNCED
177.10.12.0/22 Clean Net Telecom Ltda Clean Net Telecom Ltda BGP ANNOUNCED
177.44.208.0/22 Clean Net Telecom Ltda Clean Net Telecom Ltda BGP ANNOUNCED
177.44.208.0/21 Clean Net Telecom Ltda Clean Net Telecom Ltda BGP ANNOUNCED
177.44.212.0/22 Clean Net Telecom Ltda Clean Net Telecom Ltda BGP ANNOUNCED
177.52.38.87/32 Clean Net Telecom Clean Net Telecom PEERINGDB ASSIGNED
2001:12f8:0:6::5:3230/128 Clean Net Telecom Clean Net Telecom PEERINGDB ASSIGNED
2804:2d0::/33 Clean Net Telecom Ltda Clean Net Telecom Ltda BGP ANNOUNCED
2804:2d0::/32 Clean Net Telecom Ltda Clean Net Telecom Ltda BGP ANNOUNCED
2804:2d0:8000::/33 Clean Net Telecom Ltda Clean Net Telecom Ltda BGP ANNOUNCED
177.10.3.208/29 UNKNOWN Clean Net Telecom Ltda LACNIC reallocated
177.10.4.152/29 UNKNOWN Clean Net Telecom Ltda LACNIC reallocated
177.10.4.184/30 UNKNOWN Clean Net Telecom Ltda LACNIC reallocated
177.10.7.248/29 UNKNOWN Clean Net Telecom Ltda LACNIC reallocated
177.10.9.28/30 UNKNOWN Clean Net Telecom Ltda LACNIC reallocated
2804:2d0::/32 UNKNOWN Clean Net Telecom Ltda LACNIC allocated
← Previous Next →

Uses the REST API.