bgpreport

Network · data from 2026-11-12

AS200596 Adyen

Registry name: ADYEN Adyen N.V., NL · PeeringDB

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

Announced routes

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

66.199.8.0/25 No ROA None 2 0%low visibility 2
64.74.138.0/24 No ROA Other IRR onlyRADB 673 100% 66
85.184.228.0/23 Valid Nonecovered by 85.184.228.0/22 673 100% 67
85.184.230.0/23 Valid Nonecovered by 85.184.228.0/22 673 100% 67
147.12.16.0/22 Valid Nonecovered by 147.12.16.0/20 673 100% 66
147.12.22.0/23 Valid Nonecovered by 147.12.16.0/20 672 100% 67
147.12.20.0/23 Valid Nonecovered by 147.12.16.0/20 670 100% 67
62.146.252.0/24 Valid RIR databaseRIPE 673 100% 66
85.184.229.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
85.184.230.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
135.84.148.0/22 Valid RIR databaseRADB, RIPE 673 100% 67
135.84.148.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
135.84.149.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
135.84.151.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
145.63.66.0/24 Valid RIR databaseRIPE 673 100% 67
145.63.70.0/24 Valid RIR databaseRIPE 673 100% 70
147.12.16.0/24 Valid RIR databaseRIPE 673 100% 66
147.12.17.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
147.12.18.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
147.12.19.0/24 Valid RIR databaseRADB, RIPE 673 100% 70
147.12.20.0/24 Valid RIR databaseRIPE 673 100% 66
147.12.21.0/24 Valid RIR databaseRIPE 673 100% 66
185.101.198.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
62.146.248.0/24 Valid RIR databaseRIPE 672 100% 70
62.146.249.0/24 Valid RIR databaseRIPE 672 100% 67
62.146.250.0/24 Valid RIR databaseRIPE 672 100% 67
85.184.228.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
85.184.231.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
135.84.150.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
147.12.22.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
147.12.23.0/24 Valid RIR databaseRADB, RIPE 672 100% 70

AS-SET

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

  • ROA: none2
  • Route object: none6
  • Route object: RIR1
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none66.199.8.0/25No ROA covers it. Add a ROA for AS200596, maxLength 25.2 of 673
Route object: none66.199.8.0/25No route object for it. Add a route object with origin AS200596 in the RIR database for the space.2 of 673
ROA: none64.74.138.0/24No ROA covers it. Add a ROA for AS200596, maxLength 24.673 of 673
Route object: RIR64.74.138.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: none85.184.228.0/23No route object for it. A route object for 85.184.228.0/22 with origin AS200596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200596 in the RIR database for the space.673 of 673
Route object: none85.184.230.0/23No route object for it. A route object for 85.184.228.0/22 with origin AS200596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200596 in the RIR database for the space.673 of 673
Route object: none147.12.16.0/22No route object for it. A route object for 147.12.16.0/20 with origin AS200596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200596 in the RIR database for the space.673 of 673
Route object: none147.12.22.0/23No route object for it. A route object for 147.12.16.0/20 with origin AS200596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200596 in the RIR database for the space.672 of 673
Route object: none147.12.20.0/23No route object for it. A route object for 147.12.16.0/20 with origin AS200596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200596 in the RIR database for the space.670 of 673

Route objects not announced

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

62.146.248.0/21RIPEValid
62.146.251.0/24RIPEValid
62.146.254.0/24RIPEValid
62.146.255.0/24RIPEValid
85.184.228.0/22RADB, RIPEValid
91.212.42.0/24RIPEInvalid: origin
145.63.64.0/24RIPEValid
145.63.65.0/24RIPEValid
147.12.16.0/20RIPEValid
185.101.196.0/22NTTCOM, RIPEValid
185.101.196.0/24RADBValid
185.101.197.0/24RADB, RIPEValid
185.101.199.0/24RADB, RIPEValid
193.67.130.0/24RADBNo 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.