bgpreport

Network · data from 2026-11-12

AS272465 AS272465 - Fibruz Telecom Ltda

Registry name: AS272465 - Fibruz Telecom Ltda, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272465, 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:819c::/32 No ROA Other IRR onlyRADB, TC 631 99% 67
2804:819c::/33 No ROA Other IRR onlyRADB 105 17% 40
2804:819c:8000::/33 No ROA Other IRR onlyRADB 105 17% 40

AS-SET

AS272465 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 7 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2804:819c::/32No ROA covers it. Add a ROA for AS272465, maxLength 32.631 of 636
Route object: RIR2804:819c::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
ROA: none2804:819c::/33No ROA covers it. Add a ROA for AS272465, maxLength 33.105 of 636
Route object: RIR2804:819c::/33Route object only in RADB. Add it in the RIR database for the space.105 of 636
ROA: none2804:819c:8000::/33No ROA covers it. Add a ROA for AS272465, maxLength 33.105 of 636
Route object: RIR2804:819c:8000::/33Route object only in RADB. Add it in the RIR database for the space.105 of 636

Route objects not announced

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

2804:819c::/34RADBNo 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.