CONNECT TELECOM LTDA

Data as of 2026-08-09
BGP inherited
Cluster stats
Netblocks8 · 2,051 IPv4 addresses
IPv6 3 prefixes (largest 2001:12f8:0:13::130/128)
Cluster ID219782644
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 9 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

7 weekly snapshots · JSON
8 -13 netblocks since 2026-07-05
2026-07-05 peak 21 2026-08-09

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.184.144.130/32 CONNECT TELECOM LTDA PEERINGDB ASSIGNED ● high
187.16.208.61/32 CONNECT TELECOM LTDA PEERINGDB ASSIGNED ● high
200.192.111.30/32 CONNECT TELECOM LTDA PEERINGDB ASSIGNED ● high
2001:12f8::208:61/128 CONNECT TELECOM LTDA PEERINGDB ASSIGNED ● high
2001:12f8:0:13::130/128 CONNECT TELECOM LTDA PEERINGDB ASSIGNED ● high
2001:12f8:0:14::30/128 CONNECT TELECOM LTDA PEERINGDB ASSIGNED ● high
190.89.156.0/22 CONNECT TELECOM LTDA ARIN ALLOCATED ● low
190.123.68.0/22 CONNECT TELECOM LTDA ARIN ALLOCATED ● low

IPv6 ranges (3)

Network trust

what's this?
RPKI hygiene: B how networks compare →
87.5% of checked blocks have valid RPKI ROA coverage (7 of 8)
Possible discrepancies (1)

These blocks are registered to CONNECT TELECOM LTDA 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.

190.89.156.0/22 /22 authorized for AS270375 — AS270375

NIC Handles

09318485000130 18578613000176 ANDRI31 AS270375 COVIL5 COVIL5 COVIL5 NOCTE9 NOCTE9