bgpreport

Network · data from 2026-11-12

AS262234 ASI NETWORK

Registry name: AS262234 - ASOCIACION DE SERVICIO DE INTERNET S. DE RL., HN · PeeringDB

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

Announced routes

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

179.49.118.155/32 Invalid: maxLength Nonecovered by 179.49.118.0/24 1 0%low visibility 1
45.4.84.0/24 Valid Nonecovered by 45.4.84.0/22 666 99% 67
45.4.85.0/24 Valid Nonecovered by 45.4.84.0/22 666 99% 67
45.4.86.0/24 Valid Nonecovered by 45.4.84.0/22 666 99% 67
45.4.87.0/24 Valid Nonecovered by 45.4.84.0/22 666 99% 67
190.185.115.0/24 Valid None 665 99% 67
190.124.164.0/24 Valid None 664 99% 67
190.185.113.0/24 Valid None 661 98% 67
190.185.114.0/24 Valid None 661 98% 67
2803:db00::/34 Valid Nonecovered by 2803:db00::/32 635 100% 67
2803:db00:8a0::/43 Valid Nonecovered by 2803:db00::/32 635 100% 67
2803:db00:8b3::/48 Valid Nonecovered by 2803:db00::/32 635 100% 67
2803:db00:a80::/48 Valid Nonecovered by 2803:db00::/32 635 100% 67
170.245.56.0/24 Valid Other IRR onlyRADB 672 100% 67
131.108.232.0/24 Valid Other IRR onlyRADB 667 99% 67
131.108.233.0/24 Valid Other IRR onlyRADB 667 99% 67
131.108.234.0/24 Valid Other IRR onlyRADB 667 99% 67
131.108.235.0/24 Valid Other IRR onlyRADB 667 99% 67
170.245.57.0/24 Valid Other IRR onlyRADB 667 99% 67
179.49.112.0/24 Valid Other IRR onlyRADB 667 99% 67
179.49.114.0/24 Valid Other IRR onlyRADB 667 99% 67
179.49.116.0/24 Valid Other IRR onlyRADB 667 99% 67
179.49.119.0/24 Valid Other IRR onlyRADB 667 99% 67
170.245.58.0/24 Valid Other IRR onlyRADB 665 99% 67
170.245.59.0/24 Valid Other IRR onlyRADB 665 99% 67
179.49.113.0/24 Valid Other IRR onlyRADB 665 99% 67
179.49.115.0/24 Valid Other IRR onlyRADB 665 99% 67
179.49.117.0/24 Valid Other IRR onlyRADB 665 99% 67
179.49.118.0/24 Valid Other IRR onlyRADB 663 99% 67
170.245.56.0/22 Valid RIR databaseALTDB, LACNIC, NTTCOM 665 99% 67
2803:db00::/32 Valid RIR databaseLACNIC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS262234: AS262234: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 (AS262234 isn't in the set, or no route object for AS262234 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 objectsAS262234 in itNot covered
AS262234:AS-ALL In no IRR database read today.

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

  • ROA: maxLength1
  • Route object: none13
  • Route object: RIR16
  • AS-SET: not found1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength179.49.118.155/32ROA 179.49.112.0/21 AS262234 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 179.49.118.155/32.1 of 673
Route object: none179.49.118.155/32No route object for it. A route object for 179.49.118.0/24 with origin AS262234 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS262234 in the RIR database for the space.1 of 673
Route object: none45.4.84.0/24No route object for it. A route object for 45.4.84.0/22 with origin AS262234 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262234 in the RIR database for the space.666 of 673
Route object: none45.4.85.0/24No route object for it. A route object for 45.4.84.0/22 with origin AS262234 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262234 in the RIR database for the space.666 of 673
Route object: none45.4.86.0/24No route object for it. A route object for 45.4.84.0/22 with origin AS262234 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262234 in the RIR database for the space.666 of 673
Route object: none45.4.87.0/24No route object for it. A route object for 45.4.84.0/22 with origin AS262234 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262234 in the RIR database for the space.666 of 673
Route object: none190.185.115.0/24No route object for it. Add a route object with origin AS262234 in the RIR database for the space.665 of 673
Route object: none190.124.164.0/24No route object for it. Add a route object with origin AS262234 in the RIR database for the space.664 of 673
Route object: none190.185.113.0/24No route object for it. Add a route object with origin AS262234 in the RIR database for the space.661 of 673
Route object: none190.185.114.0/24No route object for it. Add a route object with origin AS262234 in the RIR database for the space.661 of 673
Route object: none2803:db00::/34No route object for it. A route object for 2803:db00::/32 with origin AS262234 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262234 in the RIR database for the space.635 of 636
Route object: none2803:db00:8a0::/43No route object for it. A route object for 2803:db00::/32 with origin AS262234 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262234 in the RIR database for the space.635 of 636
Route object: none2803:db00:8b3::/48No route object for it. A route object for 2803:db00::/32 with origin AS262234 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262234 in the RIR database for the space.635 of 636
Route object: none2803:db00:a80::/48No route object for it. A route object for 2803:db00::/32 with origin AS262234 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262234 in the RIR database for the space.635 of 636
Route object: RIR170.245.56.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR131.108.232.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR131.108.233.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR131.108.234.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR131.108.235.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR170.245.57.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR179.49.112.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR179.49.114.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR179.49.116.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR179.49.119.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR170.245.58.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR170.245.59.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR179.49.113.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR179.49.115.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR179.49.117.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR179.49.118.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673
AS-SET: not foundAS262234:AS-ALLPeeringDB names AS262234:AS-ALL; no IRR database read has it.

Route objects not announced

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

45.4.84.0/22ALTDB, NTTCOM, RADBValid
131.108.232.0/22ALTDB, LACNIC, NTTCOMValid
179.49.112.0/21ALTDB, LACNIC, NTTCOM, RADBValid

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.