bgpreport

Network · data from 2026-11-12

AS263163 AS263163 - JR LINK PROVEDOR DE INTERNET VIA RARIO LTDA

Registry name: AS263163 - JR LINK PROVEDOR DE INTERNET VIA RARIO LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263163, 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.

177.93.72.0/24 No ROA Other IRR onlyRADB 671 100% 66
177.93.73.0/24 No ROA Other IRR onlyRADB 671 100% 66
177.93.74.0/24 No ROA Other IRR onlyRADB 671 100% 66
177.93.75.0/24 No ROA Other IRR onlyRADB 671 100% 67
177.93.77.0/24 No ROA Other IRR onlyRADB 671 100% 66
177.93.78.0/24 No ROA Other IRR onlyRADB 671 100% 67
177.93.79.0/24 No ROA Other IRR onlyRADB 671 100% 67
177.93.76.0/24 No ROA Other IRR onlyRADB 669 99% 67
2804:17a8::/36 No ROA Other IRR onlyRADB 636 100% 69

AS-SET

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

  • ROA: none9
  • Route object: RIR9
  • Route object: not announced38
ChangePrefix or setDetailFull-table peers
ROA: none177.93.72.0/24No ROA covers it. Add a ROA for AS263163, maxLength 24.671 of 673
Route object: RIR177.93.72.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.93.73.0/24No ROA covers it. Add a ROA for AS263163, maxLength 24.671 of 673
Route object: RIR177.93.73.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.93.74.0/24No ROA covers it. Add a ROA for AS263163, maxLength 24.671 of 673
Route object: RIR177.93.74.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.93.75.0/24No ROA covers it. Add a ROA for AS263163, maxLength 24.671 of 673
Route object: RIR177.93.75.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.93.77.0/24No ROA covers it. Add a ROA for AS263163, maxLength 24.671 of 673
Route object: RIR177.93.77.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.93.78.0/24No ROA covers it. Add a ROA for AS263163, maxLength 24.671 of 673
Route object: RIR177.93.78.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.93.79.0/24No ROA covers it. Add a ROA for AS263163, maxLength 24.671 of 673
Route object: RIR177.93.79.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.93.76.0/24No ROA covers it. Add a ROA for AS263163, maxLength 24.669 of 673
Route object: RIR177.93.76.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2804:17a8::/36No ROA covers it. Add a ROA for AS263163, maxLength 36.636 of 636
Route object: RIR2804:17a8::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

177.93.72.0/21RADBNo ROA
177.93.72.0/22RADBNo ROA
177.93.72.0/23RADBNo ROA
177.93.74.0/23RADBNo ROA
177.93.76.0/22RADBNo ROA
177.93.76.0/23RADBNo ROA
177.93.78.0/23RADBNo ROA
201.131.2.0/24RADBNo ROA
2804:17a8::/32RADBNo ROA
2804:17a8::/33RADBNo ROA
2804:17a8::/34RADBNo ROA
2804:17a8::/35RADBNo ROA
2804:17a8:1000::/36RADBNo ROA
2804:17a8:2000::/35RADBNo ROA
2804:17a8:2000::/36RADBNo ROA
2804:17a8:3000::/36RADBNo ROA
2804:17a8:4000::/34RADBNo ROA
2804:17a8:4000::/35RADBNo ROA
2804:17a8:4000::/36RADBNo ROA
2804:17a8:5000::/36RADBNo ROA
2804:17a8:6000::/35RADBNo ROA
2804:17a8:6000::/36RADBNo ROA
2804:17a8:7000::/36RADBNo ROA
2804:17a8:8000::/33RADBNo ROA
2804:17a8:8000::/34RADBNo ROA
2804:17a8:8000::/35RADBNo ROA
2804:17a8:8000::/36RADBNo ROA
2804:17a8:9000::/36RADBNo ROA
2804:17a8:a000::/35RADBNo ROA
2804:17a8:a000::/36RADBNo ROA
2804:17a8:b000::/36RADBNo ROA
2804:17a8:c000::/34RADBNo ROA
2804:17a8:c000::/35RADBNo ROA
2804:17a8:c000::/36RADBNo ROA
2804:17a8:d000::/36RADBNo ROA
2804:17a8:e000::/35RADBNo ROA
2804:17a8:e000::/36RADBNo ROA
2804:17a8: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.