bgpreport

Network · data from 2026-11-12

AS210423 AS_ATUAXANELA ATUAXANELA, S.L.

Registry name: AS_ATUAXANELA ATUAXANELA, S.L., ES · not in PeeringDB

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

Announced routes

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

149.36.192.0/22 No ROA Other IRR onlyRADB 670 100% 67
154.60.106.0/24 No ROA Other IRR onlyRADB 670 100% 67
154.60.107.0/24 No ROA Other IRR onlyRADB 670 100% 67
80.91.70.0/24 No ROA RIR databaseRADB, RIPE 670 100% 67
80.91.90.0/24 No ROA RIR databaseRADB, RIPE 670 100% 67
79.108.228.0/22 Valid RIR databaseRIPE 672 100% 67
81.172.72.0/21 Valid RIR databaseRIPE 672 100% 67
84.232.37.0/24 Valid RIR databaseRIPE 672 100% 67
84.236.234.0/23 Valid RIR databaseRIPE 672 100% 67
93.157.107.0/24 Valid RIR databaseRIPE 672 100% 67
95.178.112.0/22 Valid RIR databaseRIPE 672 100% 67
95.178.112.0/23 Valid RIR databaseRIPE 672 100% 67
95.178.114.0/23 Valid RIR databaseRIPE 672 100% 67
84.232.35.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

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

  • ROA: none5
  • Route object: RIR3
  • Route object: not announced23
ChangePrefix or setDetailFull-table peers
ROA: none149.36.192.0/22No ROA covers it. Add a ROA for AS210423, maxLength 22.670 of 673
Route object: RIR149.36.192.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none154.60.106.0/24No ROA covers it. Add a ROA for AS210423, maxLength 24.670 of 673
Route object: RIR154.60.106.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none154.60.107.0/24No ROA covers it. Add a ROA for AS210423, maxLength 24.670 of 673
Route object: RIR154.60.107.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none80.91.70.0/24No ROA covers it. Add a ROA for AS210423, maxLength 24.670 of 673
ROA: none80.91.90.0/24No ROA covers it. Add a ROA for AS210423, maxLength 24.670 of 673

Route objects not announced

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

79.108.232.0/21RIPEValid
79.108.232.0/22RIPEValid
79.108.232.0/23RIPEValid
79.108.232.0/24RIPEValid
79.108.233.0/24RIPEValid
79.108.234.0/23RIPEValid
79.108.234.0/24RIPEValid
79.108.235.0/24RIPEValid
79.108.236.0/22RIPEValid
79.108.236.0/23RIPEValid
79.108.236.0/24RIPEValid
79.108.237.0/24RIPEValid
79.108.238.0/23RIPEValid
79.108.238.0/24RIPEValid
79.108.239.0/24RIPEValid
84.232.36.0/23RIPEValid
84.232.36.0/24RIPEValid
84.236.226.0/24RIPEInvalid: origin
84.236.227.0/24RIPEInvalid: origin
88.148.100.0/24RIPEInvalid: origin
88.148.101.0/24RIPEInvalid: origin
149.39.192.0/22RADBNo ROA
185.67.28.0/22RIPEValid

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.