bgpreport

Network · data from 2026-11-12

AS262194 Dese Technologies Argentina

Registry name: AS262194 - Dese Technologies Argentina S.A., AR · PeeringDB

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

Announced routes

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

190.109.33.0/24 Valid Nonecovered by 190.109.32.0/19 671 100% 66
190.109.36.0/24 Valid Nonecovered by 190.109.32.0/19 671 100% 66
190.109.37.0/24 Valid Nonecovered by 190.109.32.0/19 671 100% 66
190.109.38.0/24 Valid Nonecovered by 190.109.32.0/19 671 100% 66
190.109.39.0/24 Valid Nonecovered by 190.109.32.0/19 671 100% 66
190.109.40.0/24 Valid Nonecovered by 190.109.32.0/19 671 100% 66
190.109.41.0/24 Valid Nonecovered by 190.109.32.0/19 671 100% 66
190.109.42.0/24 Valid Nonecovered by 190.109.32.0/19 671 100% 67
190.109.43.0/24 Valid Nonecovered by 190.109.32.0/19 671 100% 67
190.109.44.0/24 Valid Nonecovered by 190.109.32.0/19 671 100% 67
190.109.45.0/24 Valid Nonecovered by 190.109.32.0/19 671 100% 67
190.109.52.0/24 Valid Nonecovered by 190.109.32.0/19 671 100% 66
190.109.56.0/24 Valid Nonecovered by 190.109.32.0/19 671 100% 67
190.109.57.0/24 Valid Nonecovered by 190.109.32.0/19 671 100% 67
190.109.58.0/24 Valid Nonecovered by 190.109.32.0/19 671 100% 67
190.109.32.0/24 Valid Nonecovered by 190.109.32.0/19 669 99% 67
190.109.35.0/24 Valid Nonecovered by 190.109.32.0/19 669 99% 67
190.109.47.0/24 Valid Nonecovered by 190.109.32.0/19 669 99% 66
190.109.48.0/24 Valid Nonecovered by 190.109.32.0/19 669 99% 66
190.109.46.0/24 Valid Nonecovered by 190.109.32.0/19 668 99% 66
190.109.59.0/24 Valid Nonecovered by 190.109.32.0/19 3 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS262194: AS262194:AS-DESE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS262194 isn't in the set, or no route object for AS262194 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS262194 in itNot covered
AS262194:AS-DESE LACNIC 112 Yes 0

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

  • Route object: none21
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none190.109.33.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.671 of 673
Route object: none190.109.36.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.671 of 673
Route object: none190.109.37.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.671 of 673
Route object: none190.109.38.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.671 of 673
Route object: none190.109.39.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.671 of 673
Route object: none190.109.40.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.671 of 673
Route object: none190.109.41.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.671 of 673
Route object: none190.109.42.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.671 of 673
Route object: none190.109.43.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.671 of 673
Route object: none190.109.44.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.671 of 673
Route object: none190.109.45.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.671 of 673
Route object: none190.109.52.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.671 of 673
Route object: none190.109.56.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.671 of 673
Route object: none190.109.57.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.671 of 673
Route object: none190.109.58.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.671 of 673
Route object: none190.109.32.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.669 of 673
Route object: none190.109.35.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.669 of 673
Route object: none190.109.47.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.669 of 673
Route object: none190.109.48.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.669 of 673
Route object: none190.109.46.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.668 of 673
Route object: none190.109.59.0/24No route object for it. A route object for 190.109.32.0/19 with origin AS262194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262194 in the RIR database for the space.3 of 673

Route objects not announced

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

190.109.32.0/19LACNIC, RADBValid
2803:9000::/32LACNIC, RADBValid

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.