bgpreport

Network · data from 2026-11-12

AS22860 TECNOERA

Registry name: AS22860 - SERVICIOS INTERNET LTDA, CL · PeeringDB

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

Announced routes

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

45.234.156.0/24 Valid None 671 100% 67
190.113.0.0/22 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.4.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.5.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.6.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.7.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.8.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.9.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.10.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.11.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.12.0/23 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.14.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.15.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.16.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.17.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.18.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.19.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.20.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.21.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.22.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.23.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.24.0/24 Valid Nonecovered by 190.113.24.0/23 671 100% 67
190.113.25.0/24 Valid Nonecovered by 190.113.24.0/23 671 100% 67
190.113.27.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.28.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.29.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.30.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
190.113.31.0/24 Valid Nonecovered by 190.113.0.0/19 671 100% 67
200.91.40.0/23 Valid Nonecovered by 200.91.40.0/21 671 100% 67
2800:8f0::/36 Valid Nonecovered by 2800:8f0::/32 635 100% 67
2800:8f0:2000::/36 Valid Nonecovered by 2800:8f0::/32 635 100% 67
190.113.26.0/24 Valid Other IRR onlyRADB 669 99% 67
200.24.224.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
200.24.225.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
200.24.226.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
200.24.227.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
200.24.228.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
200.24.229.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
200.24.230.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
200.24.231.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
200.24.232.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
200.24.233.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
200.24.234.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
200.24.235.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
200.24.236.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
200.24.237.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
200.24.238.0/24 Valid Other IRR onlyNTTCOM 669 99% 67
200.24.239.0/24 Valid Other IRR onlyNTTCOM 669 99% 67
190.113.24.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
92.118.180.0/24 Valid RIR databaseRIPE 670 100% 67

AS-SET

PeeringDB's irr_as_set for AS22860: AS22860: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 (AS22860 isn't in the set, or no route object for AS22860 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 objectsAS22860 in itNot covered
AS22860:AS-ALL LACNIC 9183 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 53 are in fix.csv.

  • Route object: none31
  • Route object: RIR18
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none45.234.156.0/24No route object for it. Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.0.0/22No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.4.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.5.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.6.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.7.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.8.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.9.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.10.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.11.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.12.0/23No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.14.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.15.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.16.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.17.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.18.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.19.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.20.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.21.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.22.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.23.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.24.0/24No route object for it. A route object for 190.113.24.0/23 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.25.0/24No route object for it. A route object for 190.113.24.0/23 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.27.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.28.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.29.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.30.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none190.113.31.0/24No route object for it. A route object for 190.113.0.0/19 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none200.91.40.0/23No route object for it. A route object for 200.91.40.0/21 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.671 of 673
Route object: none2800:8f0::/36No route object for it. A route object for 2800:8f0::/32 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.635 of 636
Route object: none2800:8f0:2000::/36No route object for it. A route object for 2800:8f0::/32 with origin AS22860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22860 in the RIR database for the space.635 of 636
Route object: RIR190.113.26.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.24.224.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.24.225.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.24.226.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.24.227.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.24.228.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.24.229.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.24.230.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.24.231.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.24.232.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.24.233.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.24.234.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.24.235.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.24.236.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.24.237.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.24.238.0/24Route object only in NTTCOM. Add it in the RIR database for the space.669 of 673
Route object: RIR200.24.239.0/24Route object only in NTTCOM. Add it in the RIR database for the space.669 of 673
Route object: RIR190.113.24.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

190.113.0.0/19LACNIC, NTTCOM, RADBValid
200.24.224.0/20LACNIC, NTTCOM, RADBValid
200.91.40.0/21NTTCOMNo ROA
2800:8f0::/32LACNICValid

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.