bgpreport

Network · data from 2026-11-12

AS263104 Net Rápida Brasil LTDA

Registry name: AS263104 - Net Rapida Brasil LTDA, BR · PeeringDB

6IPv4 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
7No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS263104, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS263104, 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.
179.124.48.0/24 No ROA Other IRR onlyRADB 671 100% 67
179.124.49.0/24 No ROA Other IRR onlyRADB 671 100% 67
179.124.50.0/24 No ROA Other IRR onlyRADB 671 100% 67
179.124.53.0/24 No ROA Other IRR onlyRADB 671 100% 67
179.124.54.0/24 No ROA Other IRR onlyRADB 671 100% 67
179.124.55.0/24 No ROA Other IRR onlyRADB 671 100% 67
2804:16dc::/32 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

AS263104'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 17 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none179.124.48.0/24No ROA covers it. Add a ROA for AS263104, maxLength 24.671 of 673
Route object: RIR179.124.48.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none179.124.49.0/24No ROA covers it. Add a ROA for AS263104, maxLength 24.671 of 673
Route object: RIR179.124.49.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none179.124.50.0/24No ROA covers it. Add a ROA for AS263104, maxLength 24.671 of 673
Route object: RIR179.124.50.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none179.124.53.0/24No ROA covers it. Add a ROA for AS263104, maxLength 24.671 of 673
Route object: RIR179.124.53.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none179.124.54.0/24No ROA covers it. Add a ROA for AS263104, maxLength 24.671 of 673
Route object: RIR179.124.54.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none179.124.55.0/24No ROA covers it. Add a ROA for AS263104, maxLength 24.671 of 673
Route object: RIR179.124.55.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:16dc::/32No ROA covers it. Add a ROA for AS263104, maxLength 32.636 of 636
Route object: RIR2804:16dc::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

179.124.48.0/21RADBNo ROA
179.124.51.0/24RADBNo ROA
179.124.52.0/24RADBNo 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.