bgpreport

Network · data from 2026-11-12

AS19373 AS19373 - Triara.com S.A. de C.V.

Registry name: AS19373 - Triara.com S.A. de C.V., MX · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19373, 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.
2806:1080:101::/48 Invalid: origin None 3 0%low visibility 3
187.191.78.0/23 Valid Nonecovered by 187.191.64.0/20 673 100% 67
189.149.252.0/24 Valid Other origin onlycovered by 189.149.252.0/22 673 100% 67
189.149.253.0/24 Valid Other origin onlycovered by 189.149.252.0/22 673 100% 67
189.149.254.0/24 Valid Other origin onlycovered by 189.149.252.0/22 673 100% 67
189.149.255.0/24 Valid Other origin onlycovered by 189.149.252.0/22 673 100% 67
201.98.230.0/24 Valid Nonecovered by 201.98.230.0/23 673 100% 67
201.98.231.0/24 Valid Nonecovered by 201.98.230.0/23 673 100% 67
201.107.15.0/24 Valid Nonecovered by 201.107.12.0/22 673 100% 67
201.107.64.0/24 Valid Other origin onlycovered by 201.107.64.0/23 673 100% 67
201.107.65.0/24 Valid Other origin onlycovered by 201.107.64.0/23 673 100% 67
201.113.238.0/24 Valid Nonecovered by 201.113.238.0/23 673 100% 67
201.113.239.0/24 Valid Nonecovered by 201.113.238.0/23 673 100% 67
201.161.116.0/24 Valid Nonecovered by 201.161.112.0/21 673 100% 67
200.57.130.0/24 Valid Nonecovered by 200.57.128.0/20 672 100% 67
200.57.155.0/24 Valid Nonecovered by 200.57.144.0/20 672 100% 67
200.57.156.0/24 Valid Nonecovered by 200.57.144.0/20 672 100% 67
2806:270:7000::/40 Valid Nonecovered by 2806:270:4000::/34 636 100% 67
2806:270:7200::/40 Valid Nonecovered by 2806:270:4000::/34 636 100% 68
2806:270:7100::/40 Valid Nonecovered by 2806:270:4000::/34 635 100% 67
2806:270:7300::/40 Valid Nonecovered by 2806:270:4000::/34 635 100% 68
2806:270:7400::/40 Valid Nonecovered by 2806:270:4000::/34 635 100% 67
143.202.204.0/23 Valid RIR databaseLACNIC 673 100% 67
143.202.206.0/23 Valid RIR databaseLACNIC 673 100% 67
187.175.226.0/24 Valid RIR databaseLACNIC 673 100% 67
187.191.64.0/20 Valid RIR databaseLACNIC 673 100% 67
187.191.80.0/20 Valid RIR databaseLACNIC 673 100% 67
187.191.88.0/24 Valid RIR databaseLACNIC 673 100% 67
187.218.4.0/24 Valid RIR databaseLACNIC 673 100% 67
187.228.0.0/24 Valid RIR databaseLACNIC 673 100% 67
187.228.7.0/24 Valid RIR databaseLACNIC 673 100% 67
201.107.0.0/22 Valid RIR databaseLACNIC 673 100% 67
201.107.4.0/22 Valid RIR databaseLACNIC 673 100% 67
201.107.8.0/22 Valid RIR databaseLACNIC 673 100% 67
201.107.12.0/22 Valid RIR databaseLACNIC 673 100% 67
201.107.16.0/22 Valid RIR databaseLACNIC 673 100% 67
201.116.88.0/24 Valid RIR databaseLACNIC 673 100% 67
201.161.64.0/19 Valid RIR databaseLACNIC 673 100% 67
201.161.96.0/20 Valid RIR databaseLACNIC 673 100% 67
201.161.112.0/21 Valid RIR databaseLACNIC 673 100% 67
201.161.120.0/21 Valid RIR databaseLACNIC 673 100% 67
200.38.17.0/24 Valid RIR databaseLACNIC 672 100% 67
200.38.18.0/24 Valid RIR databaseLACNIC 672 100% 67
200.57.128.0/20 Valid RIR databaseLACNIC 672 100% 67
200.57.139.0/24 Valid RIR databaseLACNIC 672 100% 67
200.57.140.0/24 Valid RIR databaseLACNIC 672 100% 67
200.57.144.0/20 Valid RIR databaseLACNIC, RADB 672 100% 67
200.57.160.0/21 Valid RIR databaseLACNIC 672 100% 67
200.57.168.0/21 Valid RIR databaseLACNIC 672 100% 67
200.57.170.0/24 Valid RIR databaseLACNIC 672 100% 67
200.57.171.0/24 Valid RIR databaseLACNIC 672 100% 67
200.57.172.0/24 Valid RIR databaseLACNIC 672 100% 67
200.57.173.0/24 Valid RIR databaseLACNIC 672 100% 67
200.57.176.0/21 Valid RIR databaseLACNIC 672 100% 67
200.57.184.0/21 Valid RIR databaseLACNIC 672 100% 67
2806:270::/34 Valid RIR databaseLACNIC 635 100% 67
2806:270:4000::/34 Valid RIR databaseLACNIC 635 100% 67
2806:270:8000::/34 Valid RIR databaseLACNIC 635 100% 67
2806:270:c000::/34 Valid RIR databaseLACNIC 635 100% 67

AS-SET

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

  • ROA: origin1
  • Route object: none22
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: origin2806:1080:101::/48ROAs covering it name AS8151, not AS19373. If AS19373 should announce it, add a ROA for AS19373.3 of 636
Route object: none2806:1080:101::/48No route object for it. Add a route object with origin AS19373 in the RIR database for the space.3 of 636
Route object: none187.191.78.0/23No route object for it. A route object for 187.191.64.0/20 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.673 of 673
Route object: none189.149.252.0/24Route objects for it name AS8151. A route object for 189.149.252.0/22 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.673 of 673
Route object: none189.149.253.0/24Route objects for it name AS8151. A route object for 189.149.252.0/22 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.673 of 673
Route object: none189.149.254.0/24Route objects for it name AS8151. A route object for 189.149.252.0/22 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.673 of 673
Route object: none189.149.255.0/24Route objects for it name AS8151. A route object for 189.149.252.0/22 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.673 of 673
Route object: none201.98.230.0/24No route object for it. A route object for 201.98.230.0/23 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.673 of 673
Route object: none201.98.231.0/24No route object for it. A route object for 201.98.230.0/23 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.673 of 673
Route object: none201.107.15.0/24No route object for it. A route object for 201.107.12.0/22 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.673 of 673
Route object: none201.107.64.0/24Route objects for it name AS8151. A route object for 201.107.64.0/23 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.673 of 673
Route object: none201.107.65.0/24Route objects for it name AS8151. A route object for 201.107.64.0/23 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.673 of 673
Route object: none201.113.238.0/24No route object for it. A route object for 201.113.238.0/23 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.673 of 673
Route object: none201.113.239.0/24No route object for it. A route object for 201.113.238.0/23 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.673 of 673
Route object: none201.161.116.0/24No route object for it. A route object for 201.161.112.0/21 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.673 of 673
Route object: none200.57.130.0/24No route object for it. A route object for 200.57.128.0/20 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.672 of 673
Route object: none200.57.155.0/24No route object for it. A route object for 200.57.144.0/20 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.672 of 673
Route object: none200.57.156.0/24No route object for it. A route object for 200.57.144.0/20 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.672 of 673
Route object: none2806:270:7000::/40No route object for it. A route object for 2806:270:4000::/34 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.636 of 636
Route object: none2806:270:7200::/40No route object for it. A route object for 2806:270:4000::/34 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.636 of 636
Route object: none2806:270:7100::/40No route object for it. A route object for 2806:270:4000::/34 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.635 of 636
Route object: none2806:270:7300::/40No route object for it. A route object for 2806:270:4000::/34 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.635 of 636
Route object: none2806:270:7400::/40No route object for it. A route object for 2806:270:4000::/34 with origin AS19373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19373 in the RIR database for the space.635 of 636

Route objects not announced

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

187.191.80.0/22LACNICValid
189.149.252.0/22LACNICValid
200.57.136.176/28LACNICValid
200.57.142.112/28LACNICValid
200.57.152.208/28LACNICValid
200.57.162.64/26LACNICValid
201.98.230.0/23LACNICValid
201.107.64.0/23LACNICValid
201.113.238.0/23LACNICValid

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.