bgpreport

Network · data from 2026-11-12

AS265808 AS265808 - Coop de Serv Pub de Arroyo Dulce Ltda

Registry name: AS265808 - Coop de Serv Pub de Arroyo Dulce Ltda, AR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265808, 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.
201.182.112.0/24 Invalid: maxLength Nonecovered by 201.182.112.0/22 1 0%low visibility 2
201.182.113.0/24 Invalid: maxLength Nonecovered by 201.182.112.0/22 1 0%low visibility 2
201.182.114.0/24 Invalid: maxLength Nonecovered by 201.182.112.0/22 1 0%low visibility 2
201.182.115.0/24 Invalid: maxLength Nonecovered by 201.182.112.0/22 1 0%low visibility 2
201.182.112.0/22 Valid RIR databaseLACNIC 672 100% 66

AS-SET

AS265808 isn't in PeeringDB, where networks name their AS-SET.

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.

  • ROA: maxLength4
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: maxLength201.182.112.0/24ROA 201.182.112.0/22 AS265808 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 201.182.112.0/24.1 of 673
Route object: none201.182.112.0/24No route object for it. A route object for 201.182.112.0/22 with origin AS265808 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265808 in the RIR database for the space.1 of 673
ROA: maxLength201.182.113.0/24ROA 201.182.112.0/22 AS265808 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 201.182.113.0/24.1 of 673
Route object: none201.182.113.0/24No route object for it. A route object for 201.182.112.0/22 with origin AS265808 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265808 in the RIR database for the space.1 of 673
ROA: maxLength201.182.114.0/24ROA 201.182.112.0/22 AS265808 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 201.182.114.0/24.1 of 673
Route object: none201.182.114.0/24No route object for it. A route object for 201.182.112.0/22 with origin AS265808 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265808 in the RIR database for the space.1 of 673
ROA: maxLength201.182.115.0/24ROA 201.182.112.0/22 AS265808 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 201.182.115.0/24.1 of 673
Route object: none201.182.115.0/24No route object for it. A route object for 201.182.112.0/22 with origin AS265808 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265808 in the RIR database for the space.1 of 673

Route objects not announced

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