bgpreport

Network · data from 2026-11-12

AS19315 AS19315 - Banelco S.A.

Registry name: AS19315 - Banelco S.A., AR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19315, 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.121.78.0/24 No ROA Nonecovered by 138.121.78.0/23 670 100% 67
138.121.79.0/24 No ROA Nonecovered by 138.121.78.0/23 670 100% 67
138.121.78.0/23 No ROA Other IRR onlyRADB 672 100% 67
200.59.131.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

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

  • ROA: none4
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none138.121.78.0/24No ROA covers it. Add a ROA for AS19315, maxLength 24.670 of 673
Route object: none138.121.78.0/24No route object for it. A route object for 138.121.78.0/23 with origin AS19315 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19315 in the RIR database for the space.670 of 673
ROA: none138.121.79.0/24No ROA covers it. Add a ROA for AS19315, maxLength 24.670 of 673
Route object: none138.121.79.0/24No route object for it. A route object for 138.121.78.0/23 with origin AS19315 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19315 in the RIR database for the space.670 of 673
ROA: none138.121.78.0/23No ROA covers it. Add a ROA for AS19315, maxLength 23.672 of 673
Route object: RIR138.121.78.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none200.59.131.0/24No ROA covers it. Add a ROA for AS19315, maxLength 24.672 of 673
Route object: RIR200.59.131.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

138.121.76.0/23RADBNo ROA
200.26.111.0/24RADBNo ROA
200.47.32.0/24RADBNo ROA
200.124.123.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.