bgpreport

Network · data from 2026-11-12

AS27735 AS27735 - TIVIT CHILE TERCERIZACION DE PROCESOS, SERVICIOS Y TECNOLOGIA SpA

Registry name: AS27735 - TIVIT CHILE TERCERIZACION DE PROCESOS, SERVICIOS Y TECNOLOGIA SpA, CL · not in PeeringDB

6IPv4 routes 83.3% RPKI valid · 50.0% with a route object
2IPv6 routes 0.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS27735, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS27735, 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.
192.245.60.0/24 No ROA Other origin only 671 100% 67
2803:5b20:2000::/35 No ROA Nonecovered by 2803:5b20::/32 636 100% 67
2803:5b20:4000::/35 No ROA Nonecovered by 2803:5b20::/32 631 99% 67
45.232.122.0/24 Valid Nonecovered by 45.232.120.0/22 672 100% 67
45.232.123.0/24 Valid Nonecovered by 45.232.120.0/22 672 100% 67
186.0.216.0/24 Valid RIR databaseLACNIC, RADB 673 100% 66
45.232.120.0/22 Valid RIR databaseLACNIC, RADB 671 100% 67
200.27.166.0/24 Valid RIR databaseLACNIC, NTTCOM, RADB 670 100% 67

AS-SET

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

  • ROA: none3
  • Route object: none5
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none192.245.60.0/24No ROA covers it. Add a ROA for AS27735, maxLength 24.671 of 673
Route object: none192.245.60.0/24Route objects for it name AS28116, AS28513. Add a route object with origin AS27735 in the RIR database for the space.671 of 673
ROA: none2803:5b20:2000::/35No ROA covers it. Add a ROA for AS27735, maxLength 35.636 of 636
Route object: none2803:5b20:2000::/35No route object for it. A route object for 2803:5b20::/32 with origin AS27735 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27735 in the RIR database for the space.636 of 636
ROA: none2803:5b20:4000::/35No ROA covers it. Add a ROA for AS27735, maxLength 35.631 of 636
Route object: none2803:5b20:4000::/35No route object for it. A route object for 2803:5b20::/32 with origin AS27735 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27735 in the RIR database for the space.631 of 636
Route object: none45.232.122.0/24No route object for it. A route object for 45.232.120.0/22 with origin AS27735 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27735 in the RIR database for the space.672 of 673
Route object: none45.232.123.0/24No route object for it. A route object for 45.232.120.0/22 with origin AS27735 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27735 in the RIR database for the space.672 of 673

Route objects not announced

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

200.14.89.0/24RADBValid
200.29.155.0/24NTTCOMNo ROA
206.48.139.0/24NTTCOMValid
206.48.140.0/24NTTCOM, RADBValid
2803:5b20::/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.