bgpreport

Network · data from 2026-11-12

AS201017 Achmea Achmea Interne Diensten N.V.

Registry name: Achmea Achmea Interne Diensten N.V., NL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS201017, 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.
145.219.8.0/24 Invalid: origin None 2 0%low visibility 2
145.219.9.0/24 Invalid: origin None 2 0%low visibility 2
145.219.10.0/24 Invalid: origin None 2 0%low visibility 2
145.219.11.0/24 Invalid: origin None 2 0%low visibility 2
145.219.12.0/24 Invalid: origin None 2 0%low visibility 2
145.219.13.0/24 Invalid: origin None 2 0%low visibility 2
145.219.14.0/24 Invalid: origin None 2 0%low visibility 2
145.219.15.0/24 Invalid: origin None 2 0%low visibility 2
145.219.16.0/24 Invalid: origin None 2 0%low visibility 2
145.219.17.0/24 Invalid: origin None 2 0%low visibility 2
145.219.6.0/24 Valid RIR databaseRIPE 673 100% 67
2a04:b0c0:30::/47 Valid RIR databaseRIPE 633 100% 68

AS-SET

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

  • ROA: origin10
  • Route object: none10
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin145.219.8.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS201017 should announce it, add a ROA for AS201017.2 of 673
Route object: none145.219.8.0/24No route object for it. Add a route object with origin AS201017 in the RIR database for the space.2 of 673
ROA: origin145.219.9.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS201017 should announce it, add a ROA for AS201017.2 of 673
Route object: none145.219.9.0/24No route object for it. Add a route object with origin AS201017 in the RIR database for the space.2 of 673
ROA: origin145.219.10.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS201017 should announce it, add a ROA for AS201017.2 of 673
Route object: none145.219.10.0/24No route object for it. Add a route object with origin AS201017 in the RIR database for the space.2 of 673
ROA: origin145.219.11.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS201017 should announce it, add a ROA for AS201017.2 of 673
Route object: none145.219.11.0/24No route object for it. Add a route object with origin AS201017 in the RIR database for the space.2 of 673
ROA: origin145.219.12.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS201017 should announce it, add a ROA for AS201017.2 of 673
Route object: none145.219.12.0/24No route object for it. Add a route object with origin AS201017 in the RIR database for the space.2 of 673
ROA: origin145.219.13.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS201017 should announce it, add a ROA for AS201017.2 of 673
Route object: none145.219.13.0/24No route object for it. Add a route object with origin AS201017 in the RIR database for the space.2 of 673
ROA: origin145.219.14.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS201017 should announce it, add a ROA for AS201017.2 of 673
Route object: none145.219.14.0/24No route object for it. Add a route object with origin AS201017 in the RIR database for the space.2 of 673
ROA: origin145.219.15.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS201017 should announce it, add a ROA for AS201017.2 of 673
Route object: none145.219.15.0/24No route object for it. Add a route object with origin AS201017 in the RIR database for the space.2 of 673
ROA: origin145.219.16.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS201017 should announce it, add a ROA for AS201017.2 of 673
Route object: none145.219.16.0/24No route object for it. Add a route object with origin AS201017 in the RIR database for the space.2 of 673
ROA: origin145.219.17.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS201017 should announce it, add a ROA for AS201017.2 of 673
Route object: none145.219.17.0/24No route object for it. Add a route object with origin AS201017 in the RIR database for the space.2 of 673

Route objects not announced

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

2a04:b0c0:30::/48RIPEValid
2a04:b0c0:31::/48RIPEValid

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.