bgpreport

Network · data from 2026-11-12

AS272623 AS272623 - FIBER NET SERVICOS DE TELECOMUNICACOES LTDA

Registry name: AS272623 - FIBER NET SERVICOS DE TELECOMUNICACOES LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272623, 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.252.87.0/24 No ROA Nonecovered by 38.252.86.0/23 669 99% 66
38.252.86.0/23 No ROA Other IRR onlyRADB 670 100% 66
38.252.86.0/24 No ROA Other IRR onlyRADB 670 100% 66
2804:8620::/34 No ROA Other IRR onlyRADB 631 99% 69
2804:8620::/36 No ROA Other IRR onlyRADB 631 99% 69
2804:8620:1000::/36 No ROA Other IRR onlyRADB 631 99% 69
2804:8620:2000::/36 No ROA Other IRR onlyRADB 631 99% 69

AS-SET

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

  • ROA: none7
  • Route object: none1
  • Route object: RIR6
  • Route object: not announced27
ChangePrefix or setDetailFull-table peers
ROA: none38.252.87.0/24No ROA covers it. Add a ROA for AS272623, maxLength 24.669 of 673
Route object: none38.252.87.0/24No route object for it. A route object for 38.252.86.0/23 with origin AS272623 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272623 in the RIR database for the space.669 of 673
ROA: none38.252.86.0/23No ROA covers it. Add a ROA for AS272623, maxLength 23.670 of 673
Route object: RIR38.252.86.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.252.86.0/24No ROA covers it. Add a ROA for AS272623, maxLength 24.670 of 673
Route object: RIR38.252.86.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:8620::/34No ROA covers it. Add a ROA for AS272623, maxLength 34.631 of 636
Route object: RIR2804:8620::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:8620::/36No ROA covers it. Add a ROA for AS272623, maxLength 36.631 of 636
Route object: RIR2804:8620::/36Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:8620:1000::/36No ROA covers it. Add a ROA for AS272623, maxLength 36.631 of 636
Route object: RIR2804:8620:1000::/36Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:8620:2000::/36No ROA covers it. Add a ROA for AS272623, maxLength 36.631 of 636
Route object: RIR2804:8620:2000::/36Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

2804:8620::/32RADB, TCNo ROA
2804:8620::/33RADBNo ROA
2804:8620::/35RADBNo ROA
2804:8620:2000::/35RADBNo ROA
2804:8620:3000::/36RADBNo ROA
2804:8620:4000::/34RADBNo ROA
2804:8620:4000::/35RADBNo ROA
2804:8620:4000::/36RADBNo ROA
2804:8620:5000::/36RADBNo ROA
2804:8620:6000::/35RADBNo ROA
2804:8620:6000::/36RADBNo ROA
2804:8620:7000::/36RADBNo ROA
2804:8620:8000::/33RADBNo ROA
2804:8620:8000::/34RADBNo ROA
2804:8620:8000::/35RADBNo ROA
2804:8620:8000::/36RADBNo ROA
2804:8620:9000::/36RADBNo ROA
2804:8620:a000::/35RADBNo ROA
2804:8620:a000::/36RADBNo ROA
2804:8620:b000::/36RADBNo ROA
2804:8620:c000::/34RADBNo ROA
2804:8620:c000::/35RADBNo ROA
2804:8620:c000::/36RADBNo ROA
2804:8620:d000::/36RADBNo ROA
2804:8620:e000::/35RADBNo ROA
2804:8620:e000::/36RADBNo ROA
2804:8620:f000::/36RADBNo 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.