bgpreport

Network · data from 2026-11-12

AS28065 Citarella S.A.

Registry name: AS28065 - CITARELLA S.A., AR · PeeringDB

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

Announced routes

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

200.114.84.0/23 Invalid: maxLength Nonecovered by 200.114.80.0/21 72 11% 35
200.114.86.0/23 Invalid: maxLength Nonecovered by 200.114.80.0/21 72 11% 35
200.69.159.0/24 No ROA Other IRR onlyRADB 672 100% 67
200.80.226.0/24 No ROA Other IRR onlyRADB 672 100% 67
200.114.82.0/23 Valid Nonecovered by 200.114.80.0/21 670 100% 67
200.114.84.0/22 Valid Nonecovered by 200.114.80.0/21 670 100% 67
200.114.87.0/24 Valid Other IRR onlyRADB 672 100% 67
200.114.83.0/24 Valid Other IRR onlyRADB 671 100% 67
200.114.85.0/24 Valid Other IRR onlyRADB 671 100% 67

AS-SET

AS28065'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 16 are in fix.csv.

  • ROA: maxLength2
  • ROA: none2
  • Route object: none4
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength200.114.84.0/23ROA 200.114.84.0/22 AS28065 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 200.114.84.0/23.72 of 673
Route object: none200.114.84.0/23No route object for it. A route object for 200.114.80.0/21 with origin AS28065 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28065 in the RIR database for the space.72 of 673
ROA: maxLength200.114.86.0/23ROA 200.114.84.0/22 AS28065 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 200.114.86.0/23.72 of 673
Route object: none200.114.86.0/23No route object for it. A route object for 200.114.80.0/21 with origin AS28065 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28065 in the RIR database for the space.72 of 673
ROA: none200.69.159.0/24No ROA covers it. Add a ROA for AS28065, maxLength 24.672 of 673
Route object: RIR200.69.159.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none200.80.226.0/24No ROA covers it. Add a ROA for AS28065, maxLength 24.672 of 673
Route object: RIR200.80.226.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none200.114.82.0/23No route object for it. A route object for 200.114.80.0/21 with origin AS28065 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28065 in the RIR database for the space.670 of 673
Route object: none200.114.84.0/22No route object for it. A route object for 200.114.80.0/21 with origin AS28065 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28065 in the RIR database for the space.670 of 673
Route object: RIR200.114.87.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR200.114.83.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.114.85.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

200.114.80.0/21RADBNo ROA
200.114.84.0/24RADBValid
200.114.86.0/24RADBValid

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.