bgpreport

Network · data from 2026-11-12

AS264642 TELESISTEMA

Registry name: AS264642 - TELESISTEMA S.R.L., AR · PeeringDB

30IPv4 routes 100.0% RPKI valid · 73.3% with a route object
4IPv6 routes 100.0% RPKI valid · 25.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 11 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
12Route objects not announced registered with origin AS264642, seen from no peer

Announced routes

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

181.177.14.0/24 Valid Nonecovered by 181.177.0.0/18 670 100% 67
181.177.16.0/21 Valid Nonecovered by 181.177.0.0/18 670 100% 67
181.177.20.0/24 Valid Nonecovered by 181.177.0.0/18 670 100% 67
181.177.24.0/24 Valid Nonecovered by 181.177.0.0/18 670 100% 67
181.177.40.0/24 Valid Nonecovered by 181.177.0.0/18 670 100% 67
200.73.189.0/24 Valid Nonecovered by 200.73.188.0/22 669 99% 67
200.73.190.0/24 Valid Nonecovered by 200.73.188.0/22 669 99% 67
200.73.191.0/24 Valid Nonecovered by 200.73.188.0/22 669 99% 67
2803:cf00::/33 Valid Nonecovered by 2803:cf00::/32 636 100% 67
2803:cf00:1800::/40 Valid Nonecovered by 2803:cf00::/32 636 100% 67
2803:cf00:8000::/33 Valid Nonecovered by 2803:cf00::/32 636 100% 67
200.73.188.0/24 Valid Other IRR onlyRADB 669 99% 67
186.125.200.0/24 Valid Other IRR onlyRADB 666 99% 67
186.125.201.0/24 Valid Other IRR onlyRADB 666 99% 67
190.228.42.0/24 Valid Other IRR onlyRADB 665 99% 67
190.228.43.0/24 Valid Other IRR onlyRADB 665 99% 67
190.228.116.0/24 Valid Other IRR onlyRADB 665 99% 67
190.228.117.0/24 Valid Other IRR onlyRADB 665 99% 67
190.228.166.0/24 Valid Other IRR onlyRADB 665 99% 67
190.228.167.0/24 Valid Other IRR onlyRADB 665 99% 67
181.177.0.0/18 Valid RIR databaseLACNIC, RADB 670 100% 67
186.190.128.0/19 Valid RIR databaseLACNIC, RADB 670 100% 67
190.137.162.0/23 Valid RIR databaseLACNIC 669 99% 67
200.73.188.0/22 Valid RIR databaseLACNIC, RADB 669 99% 67
181.105.228.0/22 Valid RIR databaseLACNIC 666 99% 67
186.125.199.0/24 Valid RIR databaseLACNIC 666 99% 67
190.30.254.0/24 Valid RIR databaseLACNIC, RADB 665 99% 67
190.228.64.0/23 Valid RIR databaseLACNIC 665 99% 67
190.228.88.0/22 Valid RIR databaseLACNIC 665 99% 67
190.228.93.0/24 Valid RIR databaseLACNIC, RADB 665 99% 67
190.228.94.0/24 Valid RIR databaseLACNIC, RADB 665 99% 67
190.228.115.0/24 Valid RIR databaseLACNIC, RADB 665 99% 67
190.228.165.0/24 Valid RIR databaseLACNIC, RADB 665 99% 67
2803:cf00::/32 Valid RIR databaseLACNIC, RADB 634 100% 67

AS-SET

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

  • Route object: none11
  • Route object: RIR9
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
Route object: none181.177.14.0/24No route object for it. A route object for 181.177.0.0/18 with origin AS264642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264642 in the RIR database for the space.670 of 673
Route object: none181.177.16.0/21No route object for it. A route object for 181.177.0.0/18 with origin AS264642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264642 in the RIR database for the space.670 of 673
Route object: none181.177.20.0/24No route object for it. A route object for 181.177.0.0/18 with origin AS264642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264642 in the RIR database for the space.670 of 673
Route object: none181.177.24.0/24No route object for it. A route object for 181.177.0.0/18 with origin AS264642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264642 in the RIR database for the space.670 of 673
Route object: none181.177.40.0/24No route object for it. A route object for 181.177.0.0/18 with origin AS264642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264642 in the RIR database for the space.670 of 673
Route object: none200.73.189.0/24No route object for it. A route object for 200.73.188.0/22 with origin AS264642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264642 in the RIR database for the space.669 of 673
Route object: none200.73.190.0/24No route object for it. A route object for 200.73.188.0/22 with origin AS264642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264642 in the RIR database for the space.669 of 673
Route object: none200.73.191.0/24No route object for it. A route object for 200.73.188.0/22 with origin AS264642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264642 in the RIR database for the space.669 of 673
Route object: none2803:cf00::/33No route object for it. A route object for 2803:cf00::/32 with origin AS264642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264642 in the RIR database for the space.636 of 636
Route object: none2803:cf00:1800::/40No route object for it. A route object for 2803:cf00::/32 with origin AS264642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264642 in the RIR database for the space.636 of 636
Route object: none2803:cf00:8000::/33No route object for it. A route object for 2803:cf00::/32 with origin AS264642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264642 in the RIR database for the space.636 of 636
Route object: RIR200.73.188.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR186.125.200.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR186.125.201.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR190.228.42.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR190.228.43.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR190.228.116.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR190.228.117.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR190.228.166.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR190.228.167.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673

Route objects not announced

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

186.125.200.0/23LACNICValid
186.190.128.0/21RADBValid
186.190.136.0/21RADBValid
186.190.144.0/21RADBValid
186.190.152.0/21RADBValid
186.228.88.0/22RADBNo ROA
190.228.42.0/23LACNICValid
190.228.64.0/24RADBValid
190.228.65.0/24RADBValid
190.228.88.0/24RADBValid
190.228.116.0/23LACNICValid
190.228.166.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.