RJNET Telecomunicacoes Ltda ME

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

Footprint over time

4 weekly snapshots · JSON
15 -1 netblocks since 2026-07-05
2026-07-05 peak 16 2026-07-13

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
168.228.8.0/23 AS264900 BGP ANNOUNCED ● medium
168.228.8.0/22 AS264900 BGP ANNOUNCED ● medium
168.228.10.0/23 AS264900 BGP ANNOUNCED ● medium
170.80.236.0/23 AS264900 BGP ANNOUNCED ● medium
170.80.236.0/22 AS264900 BGP ANNOUNCED ● medium
170.80.238.0/23 RJNET Telecomunicacoes Ltda ME BGP ANNOUNCED ● medium
2804:2f94::/33 AS264900 BGP ANNOUNCED ● medium
2804:2f94::/32 AS264900 BGP ANNOUNCED ● medium
2804:2f94:8000::/33 AS264900 BGP ANNOUNCED ● medium

Network trust

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

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.

2804:2f94::/32 /32 authorized for AS264900 — AS264900
2804:2f94::/33 /33 authorized for AS264900 — AS264900
2804:2f94:8000::/33 /33 authorized for AS264900 — AS264900
168.228.8.0/22 /22 authorized for AS264900 — AS264900
170.80.236.0/22 /22 authorized for AS264900 — AS264900
168.228.8.0/23 /23 authorized for AS264900 — AS264900
168.228.10.0/23 /23 authorized for AS264900 — AS264900
170.80.236.0/23 /23 authorized for AS264900 — AS264900
170.80.238.0/23 /23 authorized for AS264900 — AS264900

NIC Handles

AS264900