bgpreport

Network · data from 2026-11-12

AS52263 Telecable Economico S.A.

Registry name: AS52263 - Telecable Economico S.A., CR · PeeringDB

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

Announced routes

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

8.242.197.0/24 No ROA Other IRR onlyRADB 673 100% 68
64.209.9.0/24 No ROA Other IRR onlyRADB 672 100% 68
190.61.108.0/24 Valid Other origin only 670 100% 67
2803:1300::/36 Valid Nonecovered by 2803:1300::/32 635 100% 70
2803:1300:2000::/36 Valid Nonecovered by 2803:1300::/32 635 100% 70
2803:1300:b000::/36 Valid Nonecovered by 2803:1300::/32 635 100% 70
2803:1300:b003::/48 Valid Nonecovered by 2803:1300::/32 635 100% 70
2803:1300:b601::/48 Valid Nonecovered by 2803:1300::/32 635 100% 70
2803:1300:e000::/36 Valid Nonecovered by 2803:1300::/32 635 100% 70
2803:1300:f000::/36 Valid Nonecovered by 2803:1300::/32 635 100% 70
2803:1300:f010::/44 Valid Nonecovered by 2803:1300::/32 635 100% 70
170.246.157.0/24 Valid RIR databaseLACNIC 673 100% 68
177.93.3.0/24 Valid RIR databaseLACNIC 673 100% 68
177.93.10.0/24 Valid RIR databaseLACNIC 673 100% 68
177.93.13.0/24 Valid RIR databaseLACNIC 673 100% 68
177.93.21.0/24 Valid RIR databaseLACNIC 673 100% 68
177.93.31.0/24 Valid RIR databaseLACNIC 673 100% 68
186.121.128.0/24 Valid RIR databaseLACNIC 673 100% 68
186.121.129.0/24 Valid RIR databaseLACNIC 673 100% 68
186.121.130.0/24 Valid RIR databaseLACNIC 673 100% 68
186.121.131.0/24 Valid RIR databaseLACNIC 673 100% 68
186.121.133.0/24 Valid RIR databaseLACNIC 673 100% 68
186.121.135.0/24 Valid RIR databaseLACNIC 673 100% 68
138.118.80.0/22 Valid RIR databaseLACNIC, RADB 672 100% 68
138.118.80.0/24 Valid RIR databaseLACNIC 672 100% 68
138.118.81.0/24 Valid RIR databaseLACNIC 672 100% 68
138.118.82.0/24 Valid RIR databaseLACNIC 672 100% 68
138.118.83.0/24 Valid RIR databaseLACNIC 672 100% 68
170.150.58.0/24 Valid RIR databaseLACNIC 672 100% 68
170.150.59.0/24 Valid RIR databaseLACNIC 672 100% 68
170.246.158.0/24 Valid RIR databaseLACNIC 672 100% 68
170.246.159.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.0.0/24 Valid RIR databaseLACNIC, RADB 672 100% 68
177.93.1.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.2.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.5.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.6.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.7.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.8.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.9.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.11.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.12.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.14.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.16.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.17.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.18.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.19.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.20.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.22.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.23.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.24.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.25.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.27.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.28.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.29.0/24 Valid RIR databaseLACNIC 672 100% 68
177.93.30.0/24 Valid RIR databaseLACNIC 672 100% 68
186.121.134.0/24 Valid RIR databaseLACNIC 672 100% 68
190.113.110.0/24 Valid RIR databaseLACNIC, RADB 672 100% 68
190.171.106.0/24 Valid RIR databaseLACNIC 672 100% 68
190.171.127.0/24 Valid RIR databaseLACNIC 672 100% 68
200.105.101.0/24 Valid RIR databaseLACNIC 672 100% 68
200.229.0.0/24 Valid RIR databaseLACNIC 672 100% 68
200.229.10.0/24 Valid RIR databaseLACNIC 672 100% 68
200.229.11.0/24 Valid RIR databaseLACNIC 672 100% 68
200.229.13.0/24 Valid RIR databaseLACNIC 672 100% 68
200.229.15.0/24 Valid RIR databaseLACNIC 672 100% 68
170.150.56.0/22 Valid RIR databaseLACNIC, RADB 671 100% 68
170.150.56.0/24 Valid RIR databaseLACNIC 671 100% 67
170.150.57.0/24 Valid RIR databaseLACNIC 671 100% 68
170.246.156.0/22 Valid RIR databaseLACNIC, RADB 671 100% 68
177.93.0.0/19 Valid RIR databaseLACNIC 671 100% 68
177.93.15.0/24 Valid RIR databaseLACNIC 671 100% 68
177.93.26.0/24 Valid RIR databaseLACNIC 671 100% 68
186.121.128.0/21 Valid RIR databaseLACNIC 671 100% 68
190.113.98.0/24 Valid RIR databaseLACNIC, RADB 671 100% 68
190.113.99.0/24 Valid RIR databaseLACNIC, RADB 671 100% 68
190.113.100.0/24 Valid RIR databaseLACNIC, RADB 671 100% 68
190.113.101.0/24 Valid RIR databaseLACNIC, RADB 671 100% 69
190.113.102.0/24 Valid RIR databaseLACNIC, RADB 671 100% 68
190.113.104.0/24 Valid RIR databaseLACNIC, RADB 671 100% 68
190.113.105.0/24 Valid RIR databaseLACNIC, RADB 671 100% 68
190.113.106.0/24 Valid RIR databaseLACNIC, RADB 671 100% 68
190.113.107.0/24 Valid RIR databaseLACNIC, RADB 671 100% 68
190.113.108.0/24 Valid RIR databaseLACNIC, RADB 671 100% 68
190.113.109.0/24 Valid RIR databaseLACNIC, RADB 671 100% 68
190.113.111.0/24 Valid RIR databaseLACNIC, RADB 671 100% 68
190.113.112.0/24 Valid RIR databaseLACNIC 671 100% 68
190.113.113.0/24 Valid RIR databaseLACNIC 671 100% 68
190.113.114.0/24 Valid RIR databaseLACNIC 671 100% 69
190.113.116.0/24 Valid RIR databaseLACNIC 671 100% 68
190.113.117.0/24 Valid RIR databaseLACNIC 671 100% 68
190.113.118.0/24 Valid RIR databaseLACNIC 671 100% 68
190.113.119.0/24 Valid RIR databaseLACNIC 671 100% 68
190.113.120.0/24 Valid RIR databaseLACNIC 671 100% 68
190.113.121.0/24 Valid RIR databaseLACNIC 671 100% 68
190.113.122.0/24 Valid RIR databaseLACNIC 671 100% 68
190.113.123.0/24 Valid RIR databaseLACNIC 671 100% 68
190.113.124.0/24 Valid RIR databaseLACNIC 671 100% 68
190.113.125.0/24 Valid RIR databaseLACNIC 671 100% 68
190.113.126.0/24 Valid RIR databaseLACNIC 671 100% 68
190.113.127.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.97.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.98.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.99.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.100.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.101.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.102.0/24 Valid RIR databaseLACNIC 671 100% 69
190.171.104.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.105.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.107.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.108.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.109.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.110.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.113.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.114.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.115.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.116.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.117.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.118.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.119.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.120.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.121.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.122.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.123.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.124.0/24 Valid RIR databaseLACNIC 671 100% 68
190.171.126.0/24 Valid RIR databaseLACNIC 671 100% 68
200.105.96.0/24 Valid RIR databaseLACNIC 671 100% 68
200.105.98.0/24 Valid RIR databaseLACNIC 671 100% 68
200.105.99.0/24 Valid RIR databaseLACNIC 671 100% 69
200.105.100.0/24 Valid RIR databaseLACNIC 671 100% 68
200.105.102.0/24 Valid RIR databaseLACNIC 671 100% 68
200.229.2.0/24 Valid RIR databaseLACNIC 671 100% 68
200.229.3.0/24 Valid RIR databaseLACNIC 671 100% 68
200.229.4.0/24 Valid RIR databaseLACNIC 671 100% 68
200.229.5.0/24 Valid RIR databaseLACNIC 671 100% 68
200.229.7.0/24 Valid RIR databaseLACNIC 671 100% 68
200.229.8.0/24 Valid RIR databaseLACNIC 671 100% 68
200.229.9.0/24 Valid RIR databaseLACNIC 671 100% 68
200.229.12.0/24 Valid RIR databaseLACNIC 671 100% 69
200.229.14.0/24 Valid RIR databaseLACNIC 671 100% 68
190.113.96.0/19 Valid RIR databaseLACNIC, RADB 670 100% 68
190.113.96.0/24 Valid RIR databaseLACNIC, RADB 670 100% 67
190.113.97.0/24 Valid RIR databaseLACNIC, RADB 670 100% 67
190.171.96.0/19 Valid RIR databaseLACNIC, RADB 670 100% 68
190.171.96.0/24 Valid RIR databaseLACNIC 670 100% 67
190.171.103.0/24 Valid RIR databaseLACNIC 670 100% 67
190.171.112.0/24 Valid RIR databaseLACNIC 670 100% 68
190.171.125.0/24 Valid RIR databaseLACNIC 670 100% 68
190.217.121.0/24 Valid RIR databaseLACNIC, RADB 670 100% 67
200.105.96.0/21 Valid RIR databaseLACNIC, RADB 670 100% 68
200.105.97.0/24 Valid RIR databaseLACNIC 670 100% 67
200.105.103.0/24 Valid RIR databaseLACNIC 670 100% 68
200.229.6.0/24 Valid RIR databaseLACNIC 670 100% 68
154.194.69.0/24 Valid RIR databaseAFRINIC, RADB 669 99% 68
170.246.156.0/24 Valid RIR databaseLACNIC 668 99% 67
177.93.4.0/24 Valid RIR databaseLACNIC 668 99% 68
190.113.103.0/24 Valid RIR databaseLACNIC, RADB 667 99% 68
190.113.115.0/24 Valid RIR databaseLACNIC 667 99% 68
190.171.111.0/24 Valid RIR databaseLACNIC 667 99% 68
200.229.1.0/24 Valid RIR databaseLACNIC 667 99% 68
186.121.132.0/24 Valid RIR databaseLACNIC 0 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS52263: AS52263:AS-ALL. 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 (AS52263 isn't in the set, or no route object for AS52263 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 objectsAS52263 in itNot covered
AS52263:AS-ALL LACNIC 20256,603 Yes 1

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

  • ROA: none2
  • Route object: none9
  • Route object: RIR2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none8.242.197.0/24No ROA covers it. Add a ROA for AS52263, maxLength 24.673 of 673
Route object: RIR8.242.197.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none64.209.9.0/24No ROA covers it. Add a ROA for AS52263, maxLength 24.672 of 673
Route object: RIR64.209.9.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none190.61.108.0/24Route objects for it name AS52468. Add a route object with origin AS52263 in the RIR database for the space.670 of 673
Route object: none2803:1300::/36No route object for it. A route object for 2803:1300::/32 with origin AS52263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52263 in the RIR database for the space.635 of 636
Route object: none2803:1300:2000::/36No route object for it. A route object for 2803:1300::/32 with origin AS52263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52263 in the RIR database for the space.635 of 636
Route object: none2803:1300:b000::/36No route object for it. A route object for 2803:1300::/32 with origin AS52263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52263 in the RIR database for the space.635 of 636
Route object: none2803:1300:b003::/48No route object for it. A route object for 2803:1300::/32 with origin AS52263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52263 in the RIR database for the space.635 of 636
Route object: none2803:1300:b601::/48No route object for it. A route object for 2803:1300::/32 with origin AS52263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52263 in the RIR database for the space.635 of 636
Route object: none2803:1300:e000::/36No route object for it. A route object for 2803:1300::/32 with origin AS52263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52263 in the RIR database for the space.635 of 636
Route object: none2803:1300:f000::/36No route object for it. A route object for 2803:1300::/32 with origin AS52263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52263 in the RIR database for the space.635 of 636
Route object: none2803:1300:f010::/44No route object for it. A route object for 2803:1300::/32 with origin AS52263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52263 in the RIR database for the space.635 of 636

Route objects not announced

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

190.108.72.0/22RADBNo ROA
190.113.82.0/24RADBNo ROA
200.229.0.0/20LACNICValid
2001:470:5a::/48ARINValid
2803:1300::/32LACNICValid
2803:7810::/32RADBNo 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.