bgpreport

Network · data from 2026-11-12

AS29063 Atos-NL-AS Eviden Netherlands B.V.

Registry name: Atos-NL-AS Eviden Netherlands B.V., NL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS29063, 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.
161.89.0.0/17 No ROA RIR databaseRIPE 673 100% 66
212.25.214.0/23 No ROA RIR databaseRIPE 673 100% 66
212.25.216.0/21 No ROA RIR databaseRIPE 673 100% 66
161.89.128.0/17 No ROA RIR databaseRIPE 672 100% 67
185.180.76.0/22 No ROA RIR databaseRIPE 672 100% 67
193.109.72.0/23 No ROA RIR databaseRIPE 672 100% 67
129.185.16.0/24 No ROA RIR databaseRIPE 671 100% 67
146.253.51.0/24 No ROA RIR databaseRIPE 671 100% 67
212.25.192.0/20 Valid RIR databaseRIPE 673 100% 66
212.159.192.0/24 Valid RIR databaseRIPE 673 100% 67
212.159.224.0/19 Valid RIR databaseRIPE 673 100% 66
212.159.225.0/24 Valid RIR databaseRIPE 673 100% 67
83.138.0.0/21 Valid RIR databaseRIPE 672 100% 67
212.25.212.0/23 Valid RIR databaseRIPE 672 100% 67
212.159.192.0/19 Valid RIR databaseRIPE 672 100% 67
2a01:8180:3000::/36 Valid RIR databaseRIPE 634 100% 67

AS-SET

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

  • ROA: none8
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none161.89.0.0/17No ROA covers it. Add a ROA for AS29063, maxLength 17.673 of 673
ROA: none212.25.214.0/23No ROA covers it. Add a ROA for AS29063, maxLength 23.673 of 673
ROA: none212.25.216.0/21No ROA covers it. Add a ROA for AS29063, maxLength 21.673 of 673
ROA: none161.89.128.0/17No ROA covers it. Add a ROA for AS29063, maxLength 17.672 of 673
ROA: none185.180.76.0/22No ROA covers it. Add a ROA for AS29063, maxLength 22.672 of 673
ROA: none193.109.72.0/23No ROA covers it. Add a ROA for AS29063, maxLength 23.672 of 673
ROA: none129.185.16.0/24No ROA covers it. Add a ROA for AS29063, maxLength 24.671 of 673
ROA: none146.253.51.0/24No ROA covers it. Add a ROA for AS29063, maxLength 24.671 of 673

Route objects not announced

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

134.54.248.0/21RIPENo ROA
156.150.0.0/16RIPENo ROA
161.90.0.0/16RIPENo ROA
185.180.76.0/24RIPENo ROA
185.180.77.0/24RIPENo ROA
185.180.78.0/24RIPENo ROA
185.180.79.0/24RIPENo ROA
193.221.84.0/24RIPEValid
193.221.85.0/24RIPEValid
194.138.137.0/24RIPENo ROA
195.42.134.0/23RIPENo ROA
199.6.128.0/21RADBNo ROA
199.6.154.0/24RADBNo ROA
212.159.226.0/24RIPEValid
2a01:8180:3f00::/40RIPEValid

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.