bgpreport

Network · data from 2026-11-12

AS52439 Banda Ancha

Registry name: AS52439 - OPTIC TELECOMUNICACIONES LIMITADA, CL · PeeringDB

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

Announced routes

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

2803:5200:1000::/48 No ROA Other IRR onlyRADB 635 100% 69
2803:5200:1001::/48 No ROA Other IRR onlyRADB 635 100% 67
191.98.204.0/22 Valid Nonecovered by 191.98.200.0/21 671 100% 67
191.98.204.0/24 Valid Other IRR onlyRADB 673 100% 67
131.161.202.0/24 Valid Other IRR onlyRADB 672 100% 67
131.161.203.0/24 Valid Other IRR onlyRADB 672 100% 67
170.82.226.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
170.82.227.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
190.113.244.0/24 Valid Other IRR onlyRADB 672 100% 67
190.113.245.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.128.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.132.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.134.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.135.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.139.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.141.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.142.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.143.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.145.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.147.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.148.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.149.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.151.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.152.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.153.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.154.0/24 Valid Other IRR onlyRADB 672 100% 67
201.218.155.0/24 Valid Other IRR onlyRADB 672 100% 67
143.208.52.0/23 Valid Other IRR onlyRADB 671 100% 66
143.208.54.0/23 Valid Other IRR onlyRADB 671 100% 66
179.63.244.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 68
179.63.245.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 68
179.63.246.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 69
179.63.247.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 69
190.113.247.0/24 Valid Other IRR onlyRADB 671 100% 69
191.98.200.0/24 Valid Other IRR onlyRADB 671 100% 66
191.98.201.0/24 Valid Other IRR onlyRADB 671 100% 66
191.98.202.0/24 Valid Other IRR onlyRADB 671 100% 66
191.98.203.0/24 Valid Other IRR onlyRADB 671 100% 66
191.98.205.0/24 Valid Other IRR onlyRADB 671 100% 69
191.98.206.0/24 Valid Other IRR onlyRADB 671 100% 69
191.98.207.0/24 Valid Other IRR onlyRADB 671 100% 69
191.98.200.0/21 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
170.82.225.0/24 Valid Other IRR onlyNTTCOM, RADB 667 99% 67
190.113.246.0/24 Valid Other IRR onlyRADB 665 99% 67
201.218.138.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
143.208.52.0/22 Valid RIR databaseLACNIC, RADB 671 100% 68
38.56.106.0/24 Valid RIR databaseARIN, RADB 670 100% 67
2803:5200:6411::/48 Valid RIR databaseLACNIC, RADB 635 100% 67
2803:cd60:5032::/48 Valid RIR databaseLACNIC 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS52439: AS-BANDAANCHA. 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 (AS52439 isn't in the set, or no route object for AS52439 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 objectsAS52439 in itNot covered
AS-BANDAANCHA RADB 201567 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 102 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR43
  • Route object: not announced56
ChangePrefix or setDetailFull-table peers
ROA: none2803:5200:1000::/48No ROA covers it. Add a ROA for AS52439, maxLength 48.635 of 636
Route object: RIR2803:5200:1000::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2803:5200:1001::/48No ROA covers it. Add a ROA for AS52439, maxLength 48.635 of 636
Route object: RIR2803:5200:1001::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: none191.98.204.0/22No route object for it. A route object for 191.98.200.0/21 with origin AS52439 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52439 in the RIR database for the space.671 of 673
Route object: RIR191.98.204.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR131.161.202.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR131.161.203.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR170.82.226.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR170.82.227.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.113.244.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.113.245.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.128.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.132.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.134.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.135.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.139.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.141.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.142.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.143.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.145.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.147.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.148.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.149.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.151.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.152.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.153.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.154.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR201.218.155.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR143.208.52.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR143.208.54.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR179.63.244.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR179.63.245.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR179.63.246.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR179.63.247.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.113.247.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR191.98.200.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR191.98.201.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR191.98.202.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR191.98.203.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR191.98.205.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR191.98.206.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR191.98.207.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR191.98.200.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR170.82.225.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR190.113.246.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 AS52439 whose prefix no peer sees AS52439 announce. Many are kept on purpose (backup routes, space announced only in some places).

38.137.215.0/24RADBNo ROA
131.161.200.0/22NTTCOM, RADBNo ROA
131.161.202.0/23LACNICValid
132.225.236.0/22RADBNo ROA
132.225.236.0/24RADBNo ROA
132.255.236.0/22NTTCOM, RADBValid
132.255.236.0/23RADBValid
132.255.236.0/24RADBValid
132.255.237.0/24RADBValid
132.255.238.0/23RADBValid
132.255.238.0/24RADBValid
132.255.239.0/24RADBValid
138.99.176.0/22NTTCOM, RADBNo ROA
138.185.12.0/22NTTCOM, RADBValid
138.185.12.0/24RADBValid
138.185.13.0/24RADBValid
138.185.14.0/24RADBValid
138.185.15.0/24RADBValid
143.208.52.0/24RADBValid
143.208.53.0/24RADBValid
143.208.54.0/24RADBValid
143.208.55.0/24RADBValid
160.19.200.0/22LACNIC, NTTCOM, RADBValid
160.19.200.0/24NTTCOM, RADBValid
160.19.201.0/24NTTCOM, RADBValid
160.19.202.0/24NTTCOM, RADBValid
160.19.203.0/24NTTCOM, RADBValid
168.90.156.0/22NTTCOM, RADBValid
168.90.156.0/24NTTCOM, RADBValid
168.90.157.0/24NTTCOM, RADBValid
168.90.158.0/24NTTCOM, RADBValid
168.90.159.0/24NTTCOM, RADBValid
168.194.168.0/22NTTCOM, RADBValid
168.194.168.0/24NTTCOM, RADBValid
168.194.169.0/24NTTCOM, RADBValid
168.194.170.0/24NTTCOM, RADBValid
168.194.171.0/24NTTCOM, RADBValid
170.82.224.0/22LACNIC, NTTCOM, RADBValid
170.82.224.0/24NTTCOM, RADBValid
179.63.244.0/22LACNIC, NTTCOM, RADBValid
190.113.244.0/22LACNIC, NTTCOM, RADBValid
201.218.128.0/19LACNIC, RADBValid
201.218.129.0/24RADBValid
201.218.130.0/24RADBValid
201.218.131.0/24RADBValid
201.218.133.0/24RADBValid
201.218.136.0/24LACNIC, RADBValid
201.218.137.0/24RADBValid
201.218.140.0/24RADBValid
201.218.144.0/24RADBValid
201.218.146.0/24RADBValid
201.218.150.0/24RADBValid
201.218.156.0/24RADBValid
201.218.159.0/24RADBValid
2803:b0e0:9978::/48LACNIC, RADBValid
2803:b0e0:9979::/48LACNIC, 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.