bgpreport

Network · data from 2026-11-12

AS52481 INFRACOM DE INFRAESTRUCTURAS S .A.

Registry name: AS52481 - INFRACOM S.A., AR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52481, 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.
168.0.204.0/24 No ROA Nonecovered by 168.0.204.0/22 670 100% 67
168.0.205.0/24 No ROA Nonecovered by 168.0.204.0/22 670 100% 67
168.0.206.0/24 No ROA Nonecovered by 168.0.204.0/22 670 100% 67
168.0.207.0/24 No ROA Nonecovered by 168.0.204.0/22 670 100% 67
2803:bf00:100::/40 No ROA None 354 56% 65

AS-SET

AS52481'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 12 are in fix.csv.

  • ROA: none5
  • Route object: none5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none168.0.204.0/24No ROA covers it. Add a ROA for AS52481, maxLength 24.670 of 673
Route object: none168.0.204.0/24No route object for it. A route object for 168.0.204.0/22 with origin AS52481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52481 in the RIR database for the space.670 of 673
ROA: none168.0.205.0/24No ROA covers it. Add a ROA for AS52481, maxLength 24.670 of 673
Route object: none168.0.205.0/24No route object for it. A route object for 168.0.204.0/22 with origin AS52481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52481 in the RIR database for the space.670 of 673
ROA: none168.0.206.0/24No ROA covers it. Add a ROA for AS52481, maxLength 24.670 of 673
Route object: none168.0.206.0/24No route object for it. A route object for 168.0.204.0/22 with origin AS52481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52481 in the RIR database for the space.670 of 673
ROA: none168.0.207.0/24No ROA covers it. Add a ROA for AS52481, maxLength 24.670 of 673
Route object: none168.0.207.0/24No route object for it. A route object for 168.0.204.0/22 with origin AS52481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52481 in the RIR database for the space.670 of 673
ROA: none2803:bf00:100::/40No ROA covers it. Add a ROA for AS52481, maxLength 40.354 of 636
Route object: none2803:bf00:100::/40No route object for it. Add a route object with origin AS52481 in the RIR database for the space.354 of 636

Route objects not announced

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

168.0.204.0/22RADBNo ROA
181.199.160.0/20RADBNo ROA

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.