bgpreport

Network · data from 2026-11-12

AS37141 ETI SA

Registry name: ETI SA - ETI SA, GN · PeeringDB

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

Announced routes

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

41.79.238.0/24 No ROA Nonecovered by 41.79.236.0/22 671 100% 68
41.79.236.0/22 No ROA Other IRR onlyRIPE-NONAUTH 671 100% 69
41.191.220.0/22 No ROA Other IRR onlyRIPE-NONAUTH 671 100% 69

AS-SET

AS37141'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 6 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none41.79.238.0/24No ROA covers it. Add a ROA for AS37141, maxLength 24.671 of 673
Route object: none41.79.238.0/24No route object for it. A route object for 41.79.236.0/22 with origin AS37141 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37141 in the RIR database for the space.671 of 673
ROA: none41.79.236.0/22No ROA covers it. Add a ROA for AS37141, maxLength 22.671 of 673
Route object: RIR41.79.236.0/22Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
ROA: none41.191.220.0/22No ROA covers it. Add a ROA for AS37141, maxLength 22.671 of 673
Route object: RIR41.191.220.0/22Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673

Route objects not announced

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