Atlanet Telecomunicacoes

BGP inherited
Cluster stats
Netblocks6
Cluster ID208802432
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 2 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
7 0 netblocks since 2026-07-13
2026-07-13 peak 7 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
187.16.223.60/32 Atlanet Telecomunicacoes PEERINGDB ASSIGNED ● high
187.16.223.194/32 Atlanet Telecomunicacoes PEERINGDB ASSIGNED ● high
2001:12f8::223:60/128 Atlanet Telecomunicacoes PEERINGDB ASSIGNED ● high
2001:12f8::223:194/128 Atlanet Telecomunicacoes PEERINGDB ASSIGNED ● high
2804:3174::/36 Atlanet Telecomunicacoes Ltda BGP ANNOUNCED ● low
2804:3174:8000::/36 Atlanet Telecomunicacoes Ltda BGP ANNOUNCED ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
Possible discrepancies (2)

These blocks are registered to Atlanet Telecomunicacoes 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.

2804:3174::/36 /36 authorized for AS265016 — AS265016
2804:3174:8000::/36 /36 authorized for AS265016 — AS265016

NIC Handles

AS265016 AS265016