bgpreport

Network · data from 2026-11-12

AS272721 TTFIBRA PROVEDOR DE INTERNET LTDA

Registry name: AS272721 - TTFIBRA PROVEDOR DE INTERNET LTDA, BR · PeeringDB

0IPv4 routes
5IPv6 routes 0.0% RPKI valid · 60.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS272721, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS272721, 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.
2804:87a0::/36 No ROA Nonecovered by 2804:87a0::/34 635 100% 67
2804:87a0:1000::/36 No ROA Nonecovered by 2804:87a0::/34 635 100% 67
2804:87a0::/33 No ROA Other IRR onlyTC 635 100% 67
2804:87a0:8000::/33 No ROA Other IRR onlyTC 635 100% 67
2804:87a0::/32 No ROA Other IRR onlyRADB, TC 634 100% 67

AS-SET

AS272721's PeeringDB record names no 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 14 are in fix.csv.

  • ROA: none5
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2804:87a0::/36No ROA covers it. Add a ROA for AS272721, maxLength 36.635 of 636
Route object: none2804:87a0::/36No route object for it. A route object for 2804:87a0::/34 with origin AS272721 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272721 in the RIR database for the space.635 of 636
ROA: none2804:87a0:1000::/36No ROA covers it. Add a ROA for AS272721, maxLength 36.635 of 636
Route object: none2804:87a0:1000::/36No route object for it. A route object for 2804:87a0::/34 with origin AS272721 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272721 in the RIR database for the space.635 of 636
ROA: none2804:87a0::/33No ROA covers it. Add a ROA for AS272721, maxLength 33.635 of 636
Route object: RIR2804:87a0::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:87a0:8000::/33No ROA covers it. Add a ROA for AS272721, maxLength 33.635 of 636
Route object: RIR2804:87a0:8000::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:87a0::/32No ROA covers it. Add a ROA for AS272721, maxLength 32.634 of 636
Route object: RIR2804:87a0::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

Route objects with origin AS272721 whose prefix no peer sees AS272721 announce. Many are kept on purpose (backup routes, space announced only in some places).

2804:87a0::/34TCNo ROA
2804:87a0:4000::/34TCNo ROA
2804:87a0:8000::/34TCNo ROA
2804:87a0:c000::/34TCNo ROA

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.