bgpreport

Network · data from 2026-11-12

AS264629 COOP. DE PROVISIÓN DE ELECTRICIDAD, SERVICIOS, VIVIENDA Y CRÉDITO DE MAR DEL PLATA

Registry name: AS264629 - COOP. DE PROVISION DE ELECTRICIDAD, SERVICIOS, VIVIENDA Y CREDITO DE MAR DEL PLATA LTDA, AR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264629, 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:6140:c000::/34 Invalid: maxLength Nonecovered by 2803:6140::/32 1 0%low visibility 2
143.202.32.0/24 Valid Nonecovered by 143.202.32.0/22 670 100% 67
143.202.33.0/24 Valid Nonecovered by 143.202.32.0/22 670 100% 67
143.202.34.0/24 Valid Nonecovered by 143.202.32.0/22 670 100% 67
143.202.35.0/24 Valid Nonecovered by 143.202.32.0/22 670 100% 67
2803:6140::/32 Valid RIR databaseLACNIC 636 100% 67

AS-SET

AS264629's PeeringDB record names no 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 7 are in fix.csv.

  • ROA: maxLength1
  • Route object: none5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2803:6140:c000::/34ROA 2803:6140::/32 AS264629 has maxLength 32; the route is a /34. Raise the maxLength, or add a ROA for 2803:6140:c000::/34.1 of 636
Route object: none2803:6140:c000::/34No route object for it. A route object for 2803:6140::/32 with origin AS264629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264629 in the RIR database for the space.1 of 636
Route object: none143.202.32.0/24No route object for it. A route object for 143.202.32.0/22 with origin AS264629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264629 in the RIR database for the space.670 of 673
Route object: none143.202.33.0/24No route object for it. A route object for 143.202.32.0/22 with origin AS264629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264629 in the RIR database for the space.670 of 673
Route object: none143.202.34.0/24No route object for it. A route object for 143.202.32.0/22 with origin AS264629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264629 in the RIR database for the space.670 of 673
Route object: none143.202.35.0/24No route object for it. A route object for 143.202.32.0/22 with origin AS264629 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264629 in the RIR database for the space.670 of 673

Route objects not announced

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

143.202.32.0/22LACNIC, 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.