CENTRALNET TELECOMUNICACOES LTDA - ME

Data as of 2026-09-06
BGP inherited
This organisation
Netblocks9 · 1,028 IPv4 addresses
IPv6 4 prefixes (largest 2001:12f8:0:10::136/128)
Record ID236509479
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.74.83/32 CENTRALNET TELECOMUNICACOES LTDA - ME PEERINGDB ASSIGNED ● high
187.16.217.93/32 CENTRALNET TELECOMUNICACOES LTDA - ME PEERINGDB ASSIGNED ● high
200.219.140.10/32 CENTRALNET TELECOMUNICACOES LTDA - ME PEERINGDB ASSIGNED ● high
200.219.147.136/32 CENTRALNET TELECOMUNICACOES LTDA - ME PEERINGDB ASSIGNED ● high
2001:12f8::217:93/128 CENTRALNET TELECOMUNICACOES LTDA - ME PEERINGDB ASSIGNED ● high
2001:12f8:0:9::146:83/128 CENTRALNET TELECOMUNICACOES LTDA - ME PEERINGDB ASSIGNED ● high
2001:12f8:0:10::136/128 CENTRALNET TELECOMUNICACOES LTDA - ME PEERINGDB ASSIGNED ● high
2001:12f8:1:39::10/128 CENTRALNET TELECOMUNICACOES LTDA - ME PEERINGDB ASSIGNED ● high
168.232.64.0/22 CENTRALNET TELECOMUNICACOES LTDA - ME ARIN ALLOCATED ● low

IPv6 ranges (4)

Footprint over time

11 weekly snapshots · JSON
9 -10 netblocks since 2026-07-05
2026-07-05 peak 19 2026-09-06

Network trust

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

These blocks are registered to CENTRALNET TELECOMUNICACOES LTDA - ME 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.

168.232.64.0/22 /22 authorized for AS264935 — AS264935

NIC Handles

23190430000119 ABYOU6 AS264935 VISIL220 YOSLT2