bgpreport

Network · data from 2026-11-12

AS264180 Fernando Net e Telecomunicações

Registry name: AS264180 - Fernando Net e Telecomunicacoes Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264180, 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.
138.94.164.0/22 No ROA Other IRR onlyALTDB, RADB, TC 672 100% 67
138.94.164.0/23 No ROA Other IRR onlyRADB 672 100% 67
138.94.167.0/24 No ROA Other IRR onlyRADB 669 99% 66
2804:23bc::/32 No ROA Other IRR onlyALTDB, RADB, TC 634 100% 67
2804:23bc:900::/40 No ROA Other IRR onlyRADB 633 100% 67
2804:23bc::/33 No ROA Other IRR onlyRADB 353 56% 65
2804:23bc:8000::/33 No ROA Other IRR onlyRADB 353 56% 65
138.94.165.0/24 No ROA Other IRR onlyRADB 207 31% 56
138.94.164.0/24 No ROA Other IRR onlyRADB 206 31% 56
138.94.166.0/24 No ROA Other IRR onlyRADB 206 31% 56

AS-SET

AS264180'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 20 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
ROA: none138.94.164.0/22No ROA covers it. Add a ROA for AS264180, maxLength 22.672 of 673
Route object: RIR138.94.164.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none138.94.164.0/23No ROA covers it. Add a ROA for AS264180, maxLength 23.672 of 673
Route object: RIR138.94.164.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none138.94.167.0/24No ROA covers it. Add a ROA for AS264180, maxLength 24.669 of 673
Route object: RIR138.94.167.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2804:23bc::/32No ROA covers it. Add a ROA for AS264180, maxLength 32.634 of 636
Route object: RIR2804:23bc::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:23bc:900::/40No ROA covers it. Add a ROA for AS264180, maxLength 40.633 of 636
Route object: RIR2804:23bc:900::/40Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none2804:23bc::/33No ROA covers it. Add a ROA for AS264180, maxLength 33.353 of 636
Route object: RIR2804:23bc::/33Route object only in RADB. Add it in the RIR database for the space.353 of 636
ROA: none2804:23bc:8000::/33No ROA covers it. Add a ROA for AS264180, maxLength 33.353 of 636
Route object: RIR2804:23bc:8000::/33Route object only in RADB. Add it in the RIR database for the space.353 of 636
ROA: none138.94.165.0/24No ROA covers it. Add a ROA for AS264180, maxLength 24.207 of 673
Route object: RIR138.94.165.0/24Route object only in RADB. Add it in the RIR database for the space.207 of 673
ROA: none138.94.164.0/24No ROA covers it. Add a ROA for AS264180, maxLength 24.206 of 673
Route object: RIR138.94.164.0/24Route object only in RADB. Add it in the RIR database for the space.206 of 673
ROA: none138.94.166.0/24No ROA covers it. Add a ROA for AS264180, maxLength 24.206 of 673
Route object: RIR138.94.166.0/24Route object only in RADB. Add it in the RIR database for the space.206 of 673

Route objects not announced

Every route object with origin AS264180 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.