bgpreport

Network · data from 2026-11-12

AS272619 AS272619 - FIVE TELECOM LTDA

Registry name: AS272619 - FIVE TELECOM LTDA, BR · not in PeeringDB

3IPv4 routes 0.0% RPKI valid · 33.3% with a route object
7IPv6 routes 100.0% RPKI valid · 14.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 8 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS272619, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS272619, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
38.225.79.0/24 No ROA Nonecovered by 38.225.78.0/23 668 99% 67
38.225.78.0/24 No ROA Nonecovered by 38.225.78.0/23 667 99% 67
38.225.78.0/23 No ROA Other IRR onlyRADB 669 99% 67
2804:8614::/34 Valid Nonecovered by 2804:8614::/32 635 100% 67
2804:8614:4000::/34 Valid Nonecovered by 2804:8614::/32 635 100% 67
2804:8614:8000::/34 Valid Nonecovered by 2804:8614::/32 635 100% 67
2804:8614:c000::/34 Valid Nonecovered by 2804:8614::/32 635 100% 67
2804:8614::/33 Valid Nonecovered by 2804:8614::/32 1 0%low visibility 1
2804:8614:8000::/33 Valid Nonecovered by 2804:8614::/32 1 0%low visibility 1
2804:8614::/32 Valid Other IRR onlyRADB, TC 635 100% 67

AS-SET

AS272619 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 13 are in fix.csv.

  • ROA: none3
  • Route object: none8
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none38.225.79.0/24No ROA covers it. Add a ROA for AS272619, maxLength 24.668 of 673
Route object: none38.225.79.0/24No route object for it. A route object for 38.225.78.0/23 with origin AS272619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272619 in the RIR database for the space.668 of 673
ROA: none38.225.78.0/24No ROA covers it. Add a ROA for AS272619, maxLength 24.667 of 673
Route object: none38.225.78.0/24No route object for it. A route object for 38.225.78.0/23 with origin AS272619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272619 in the RIR database for the space.667 of 673
ROA: none38.225.78.0/23No ROA covers it. Add a ROA for AS272619, maxLength 23.669 of 673
Route object: RIR38.225.78.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: none2804:8614::/34No route object for it. A route object for 2804:8614::/32 with origin AS272619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272619 in the RIR database for the space.635 of 636
Route object: none2804:8614:4000::/34No route object for it. A route object for 2804:8614::/32 with origin AS272619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272619 in the RIR database for the space.635 of 636
Route object: none2804:8614:8000::/34No route object for it. A route object for 2804:8614::/32 with origin AS272619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272619 in the RIR database for the space.635 of 636
Route object: none2804:8614:c000::/34No route object for it. A route object for 2804:8614::/32 with origin AS272619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272619 in the RIR database for the space.635 of 636
Route object: none2804:8614::/33No route object for it. A route object for 2804:8614::/32 with origin AS272619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272619 in the RIR database for the space.1 of 636
Route object: none2804:8614:8000::/33No route object for it. A route object for 2804:8614::/32 with origin AS272619 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272619 in the RIR database for the space.1 of 636
Route object: RIR2804:8614::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS272619 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.