bgpreport

Network · data from 2026-11-12

AS266830 AP Telecom

Registry name: AS266830 - AIRPOINT TELECOMUNICACIONES LIMITADA, CL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266830, 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.
200.114.94.146/32 Invalid: origin None 1 0%low visibility 1
209.14.248.10/32 Invalid: maxLength Nonecovered by 209.14.248.0/23 1 0%low visibility 1
45.238.20.0/23 Valid Nonecovered by 45.238.20.0/22 673 100% 66
45.238.22.0/23 Valid Nonecovered by 45.238.20.0/22 673 100% 66
209.14.248.0/24 Valid Nonecovered by 209.14.248.0/23 9 1%low visibility 6
209.14.249.0/24 Valid Nonecovered by 209.14.248.0/23 8 1%low visibility 5
209.14.248.0/23 Valid Other IRR onlyRADB 673 100% 66
209.14.250.0/24 Valid Other IRR onlyALTDB 106 16% 40
45.238.21.0/24 Valid Other IRR onlyNTTCOM, RADB 105 16% 42
45.238.20.0/24 Valid Other IRR onlyNTTCOM, RADB 104 15% 41
45.238.22.0/24 Valid Other IRR onlyNTTCOM, RADB 104 15% 41
45.238.23.0/24 Valid Other IRR onlyNTTCOM, RADB 104 15% 41
45.238.20.0/22 Valid RIR databaseLACNIC, NTTCOM, RADB 673 100% 66
2803:f4a0::/32 Valid RIR databaseLACNIC, RADB 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS266830: AS266830:AS-AIRPOINT. 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 (AS266830 isn't in the set, or no route object for AS266830 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 objectsAS266830 in itNot covered
AS266830:AS-AIRPOINT LACNIC 91113 Yes 2

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

  • ROA: origin1
  • ROA: maxLength1
  • Route object: none6
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: origin200.114.94.146/32ROAs covering it name AS28120, AS265703, AS265831, not AS266830. If AS266830 should announce it, add a ROA for AS266830.1 of 673
Route object: none200.114.94.146/32No route object for it. Add a route object with origin AS266830 in the RIR database for the space.1 of 673
ROA: maxLength209.14.248.10/32ROA 209.14.248.0/23 AS266830 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 209.14.248.10/32.1 of 673
Route object: none209.14.248.10/32No route object for it. A route object for 209.14.248.0/23 with origin AS266830 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS266830 in the RIR database for the space.1 of 673
Route object: none45.238.20.0/23No route object for it. A route object for 45.238.20.0/22 with origin AS266830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266830 in the RIR database for the space.673 of 673
Route object: none45.238.22.0/23No route object for it. A route object for 45.238.20.0/22 with origin AS266830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266830 in the RIR database for the space.673 of 673
Route object: none209.14.248.0/24No route object for it. A route object for 209.14.248.0/23 with origin AS266830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266830 in the RIR database for the space.9 of 673
Route object: none209.14.249.0/24No route object for it. A route object for 209.14.248.0/23 with origin AS266830 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266830 in the RIR database for the space.8 of 673
Route object: RIR209.14.248.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR209.14.250.0/24Route object only in ALTDB. Add it in the RIR database for the space.106 of 673
Route object: RIR45.238.21.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.105 of 673
Route object: RIR45.238.20.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.104 of 673
Route object: RIR45.238.22.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.104 of 673
Route object: RIR45.238.23.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.104 of 673

Route objects not announced

Every route object with origin AS266830 is announced.

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.