bgpreport

Network · data from 2026-11-12

AS265777 SOLUCIONES WISP S.A.

Registry name: AS265777 - SOLUCIONES WISP S.A., AR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265777, 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.
2803:4fc0:8010::/44 Valid Nonecovered by 2803:4fc0::/32 632 99% 67
2803:4fc0::/47 Valid Nonecovered by 2803:4fc0::/32 3 0%low visibility 3
2803:4fc0::/48 Valid Nonecovered by 2803:4fc0::/32 3 0%low visibility 3
181.191.64.0/24 Valid Other IRR onlyRADB 4 1%low visibility 3
181.191.65.0/24 Valid Other IRR onlyRADB 4 1%low visibility 3
181.191.66.0/24 Valid Other IRR onlyRADB 4 1%low visibility 3
181.191.67.0/24 Valid Other IRR onlyRADB 4 1%low visibility 3
181.191.64.0/22 Valid RIR databaseLACNIC, RADB 670 100% 67
2803:4fc0::/32 Valid RIR databaseLACNIC, RADB 634 100% 67
209.61.34.0/24 Valid RIR databaseARIN 0 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS265777: AS265777:AS-TRANSIT. 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 (AS265777 isn't in the set, or no route object for AS265777 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 objectsAS265777 in itNot covered
AS265777:AS-TRANSIT LACNIC 3123 No 10

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

  • Route object: none3
  • Route object: RIR4
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
Route object: none2803:4fc0:8010::/44No route object for it. A route object for 2803:4fc0::/32 with origin AS265777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265777 in the RIR database for the space.632 of 636
Route object: none2803:4fc0::/47No route object for it. A route object for 2803:4fc0::/32 with origin AS265777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265777 in the RIR database for the space.3 of 636
Route object: none2803:4fc0::/48No route object for it. A route object for 2803:4fc0::/32 with origin AS265777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265777 in the RIR database for the space.3 of 636
Route object: RIR181.191.64.0/24Route object only in RADB. Add it in the RIR database for the space.4 of 673
Route object: RIR181.191.65.0/24Route object only in RADB. Add it in the RIR database for the space.4 of 673
Route object: RIR181.191.66.0/24Route object only in RADB. Add it in the RIR database for the space.4 of 673
Route object: RIR181.191.67.0/24Route object only in RADB. Add it in the RIR database for the space.4 of 673
AS-SET: own ASNAS265777:AS-TRANSITAS265777 isn't in AS265777:AS-TRANSIT (LACNIC) once expanded. Add AS265777 to it.

Route objects not announced

Every route object with origin AS265777 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.