FIVE TELECOM LTDA

BGP inherited
Cluster stats
Netblocks10
All fragments 223 blocks across 76 clusters
Cluster ID204730503
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
10 +4 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-13

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
38.225.78.0/24 AS272619 BGP ANNOUNCED ● medium
38.225.78.0/23 AS272619 BGP ANNOUNCED ● medium
38.225.79.0/24 AS272619 BGP ANNOUNCED ● medium
2804:8614::/33 FIVE TELECOM LTDA BGP ANNOUNCED ● medium
2804:8614::/34 AS272619 BGP ANNOUNCED ● medium
2804:8614::/32 AS272619 BGP ANNOUNCED ● medium
2804:8614:4000::/34 AS272619 BGP ANNOUNCED ● medium
2804:8614:8000::/33 FIVE TELECOM LTDA BGP ANNOUNCED ● medium
2804:8614:8000::/34 AS272619 BGP ANNOUNCED ● medium
2804:8614:c000::/34 AS272619 BGP ANNOUNCED ● medium

Network trust

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

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

2804:8614::/32 /32 authorized for AS272619 — AS272619
2804:8614::/33 /33 authorized for AS272619 — AS272619
2804:8614:8000::/33 /33 authorized for AS272619 — AS272619
2804:8614::/34 /34 authorized for AS272619 — AS272619
2804:8614:4000::/34 /34 authorized for AS272619 — AS272619
2804:8614:8000::/34 /34 authorized for AS272619 — AS272619
2804:8614:c000::/34 /34 authorized for AS272619 — AS272619

NIC Handles

AS272619