Network · data from 2026-11-12

AS27986 entel IP Internacional

Registry name: AS27986 - ENTEL CHILE S.A., CL · PeeringDB

7IPv4 routes 100.0% RPKI valid · 85.7% with a route object

2IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

135Route objects not announced registered with origin AS27986, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS27986, 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.42.5.0/24	Valid	None	672 100%	67
152.231.110.0/24	Valid	Other IRR onlyRADB	673 100%	67
152.231.111.0/24	Valid	Other IRR onlyRADB	673 100%	67
186.10.138.0/24	Valid	Other IRR onlyRADB	673 100%	67
181.42.4.0/24	Valid	Other IRR onlyRADB	671 100%	67
186.10.137.0/24	Valid	Other IRR onlyRADB	671 100%	67
2800:330::/32	Valid	Other IRR onlyRADB	636 100%	67
186.67.248.0/24	Valid	RIR databaseLACNIC	672 100%	67
2800:300::/32	Valid	RIR databaseLACNIC, RADB	633 100%	67

AS-SET

PeeringDB's irr_as_set for AS27986: AS27986:AS-TRANSITISP. 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 (AS27986 isn't in the set, or no route object for AS27986 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.

Name	Database	ASNs	Sets	Route objects	AS27986 in it	Not covered
AS27986:AS-TRANSITISP	RADB	47	1	2,027	Yes	1

Name

Database

ASNs

Sets

Route objects

AS27986 in it

Not covered

AS27986:AS-TRANSITISP

RADB

2,027

Yes

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

Route object: none1
Route object: RIR6
Route object: not announced135

Change	Prefix or set	Detail	Full-table peers
Route object: none	181.42.5.0/24	No route object for it. Add a route object with origin AS27986 in the RIR database for the space.	672 of 673
Route object: RIR	152.231.110.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	152.231.111.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	186.10.138.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	181.42.4.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	186.10.137.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	2800:330::/32	Route object only in RADB. Add it in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

181.42.5.0/24

No route object for it. Add a route object with origin AS27986 in the RIR database for the space.

672 of 673

Route object: RIR

152.231.110.0/24