RJNET Telecomunicacoes Ltda ME

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks7 · 515 IPv4 addresses
IPv6 3 prefixes (largest 2001:12f8:0:6::26:4900/128)
Cluster ID214590030
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 · report an issue

Footprint over time

6 weekly snapshots · JSON
7 -9 netblocks since 2026-07-05
2026-07-05 peak 16 2026-07-26

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.75.85/32 RJNET Telecomunicacoes Ltda ME PEERINGDB ASSIGNED ● high
177.52.38.15/32 RJNET Telecomunicacoes Ltda ME PEERINGDB ASSIGNED ● high
187.16.218.236/32 RJNET Telecomunicacoes Ltda ME PEERINGDB ASSIGNED ● high
2001:12f8::218:236/128 RJNET Telecomunicacoes Ltda ME PEERINGDB ASSIGNED ● high
2001:12f8:0:6::26:4900/128 RJNET Telecomunicacoes Ltda ME PEERINGDB ASSIGNED ● high
2001:12f8:0:9::147:85/128 RJNET Telecomunicacoes Ltda ME PEERINGDB ASSIGNED ● high
170.80.238.0/23 RJNET Telecomunicacoes Ltda ME BGP ANNOUNCED ● low

IPv6 ranges (3)

Network trust

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

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

170.80.238.0/23 /23 authorized for AS264900 — AS264900

NIC Handles

AS264900 AS264900