bgpreport

Network · data from 2026-11-12

AS200165 AsacAS01 Asac Comunicaciones S.L.

Registry name: AsacAS01 Asac Comunicaciones S.L., ES · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200165, 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.
181.224.167.0/24 No ROA RIR databaseRIPE 673 100% 67
77.227.0.0/24 Valid None 671 100% 67
154.58.17.0/24 Valid Other IRR onlyRADB, RIPE-NONAUTH 673 100% 67
154.58.16.0/24 Valid Other IRR onlyRADB, RIPE-NONAUTH 671 100% 67
154.58.18.0/24 Valid Other IRR onlyRADB, RIPE-NONAUTH 671 100% 67
154.58.19.0/24 Valid Other IRR onlyRADB, RIPE-NONAUTH 671 100% 67
181.224.166.0/24 Valid RIR databaseRIPE 673 100% 67
213.99.28.0/24 Valid RIR databaseRIPE 673 100% 67
190.123.0.0/24 Valid RIR databaseRIPE 672 100% 67
213.0.44.0/24 Valid RIR databaseRIPE 672 100% 67
185.79.128.0/24 Valid RIR databaseRIPE 671 100% 67
185.79.129.0/24 Valid RIR databaseRIPE 671 100% 67
185.79.130.0/24 Valid RIR databaseRIPE 671 100% 67
185.79.131.0/24 Valid RIR databaseRIPE 671 100% 67
195.235.164.0/24 Valid RIR databaseRIPE 671 100% 67
190.123.1.0/24 Valid RIR databaseRIPE 670 100% 67
213.0.45.0/24 Valid RIR databaseRIPE 670 100% 67
2a05:7440:a5ac::/48 Valid RIR databaseRIPE 605 95% 67
2a05:7440:c14b::/48 Valid RIR databaseRIPE 605 95% 67

AS-SET

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

  • ROA: none1
  • Route object: none1
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none181.224.167.0/24No ROA covers it. Add a ROA for AS200165, maxLength 24.673 of 673
Route object: none77.227.0.0/24No route object for it. Add a route object with origin AS200165 in the RIR database for the space.671 of 673
Route object: RIR154.58.17.0/24Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
Route object: RIR154.58.16.0/24Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR154.58.18.0/24Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR154.58.19.0/24Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

154.58.16.0/22ARIN, RIPE-NONAUTHValid

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.