bgpreport

Network · data from 2026-11-12

AS27659 Ingenieria e Informatica Asociada

Registry name: AS27659 - Ingenieria e Informatica Asociada Ltda (IIA Ltda), CL · PeeringDB

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

Announced routes

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

190.14.56.0/23 Valid Other IRR onlyALTDB 672 100% 67
200.6.98.0/23 Valid Other IRR onlyALTDB 672 100% 67
200.6.100.0/23 Valid Other IRR onlyALTDB 672 100% 67
200.6.114.0/23 Valid Other IRR onlyALTDB 672 100% 67
200.6.120.0/23 Valid Other IRR onlyALTDB 672 100% 67
190.14.48.0/23 Valid Other IRR onlyALTDB 671 100% 66
190.14.50.0/23 Valid Other IRR onlyALTDB 671 100% 66
190.14.52.0/23 Valid Other IRR onlyALTDB 671 100% 66
190.14.58.0/23 Valid Other IRR onlyALTDB 671 100% 66
190.14.60.0/23 Valid Other IRR onlyALTDB 671 100% 66
190.14.62.0/23 Valid Other IRR onlyALTDB 671 100% 66
200.6.96.0/20 Valid Other IRR onlyALTDB 671 100% 66
200.6.96.0/23 Valid Other IRR onlyALTDB 671 100% 66
200.6.102.0/23 Valid Other IRR onlyALTDB 671 100% 66
200.6.104.0/23 Valid Other IRR onlyALTDB 671 100% 66
200.6.106.0/23 Valid Other IRR onlyALTDB 671 100% 66
200.6.110.0/23 Valid Other IRR onlyALTDB 671 100% 66
200.6.112.0/20 Valid Other IRR onlyALTDB 671 100% 66
200.6.112.0/23 Valid Other IRR onlyALTDB 671 100% 66
200.6.116.0/23 Valid Other IRR onlyALTDB 671 100% 66
200.6.118.0/23 Valid Other IRR onlyALTDB 671 100% 66
200.6.122.0/23 Valid Other IRR onlyALTDB 671 100% 66
200.6.124.0/23 Valid Other IRR onlyALTDB 671 100% 66
200.6.126.0/23 Valid Other IRR onlyALTDB 671 100% 66
190.14.48.0/20 Valid RIR databaseALTDB, LACNIC, RADB 671 100% 66
200.6.96.0/19 Valid RIR databaseALTDB, LACNIC 671 100% 66
2803:aa00::/32 Valid RIR databaseALTDB, LACNIC 606 95% 67

AS-SET

PeeringDB's irr_as_set for AS27659: AS27659: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 (AS27659 isn't in the set, or no route object for AS27659 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 objectsAS27659 in itNot covered
AS27659:AS-ALL LACNIC 1130 Yes 0
ALTDB (also) 4233 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 27 are in fix.csv.

  • Route object: RIR24
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: RIR190.14.56.0/23Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.6.98.0/23Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.6.100.0/23Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.6.114.0/23Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.6.120.0/23Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR190.14.48.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.14.50.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.14.52.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.14.58.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.14.60.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR190.14.62.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.6.96.0/20Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.6.96.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.6.102.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.6.104.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.6.106.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.6.110.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.6.112.0/20Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.6.112.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.6.116.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.6.118.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.6.122.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.6.124.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.6.126.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

64.76.100.0/24RADBNo ROA
64.76.103.0/24RADBNo ROA
200.6.108.0/23ALTDBValid

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.