bgpreport

Network · data from 2026-11-12

AS13169 ABN AMRO Bank N.V.

Registry name: ABN AMRO Bank N.V., NL · not in PeeringDB

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

Announced routes

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

167.202.195.0/24 No ROA Nonecovered by 167.202.192.0/19 672 100% 67
167.202.201.0/24 No ROA Nonecovered by 167.202.192.0/19 672 100% 67
167.202.205.0/24 No ROA Other origin onlycovered by 167.202.192.0/19 672 100% 67
167.202.212.0/24 No ROA Other origin onlycovered by 167.202.192.0/19 672 100% 67
167.202.220.0/24 No ROA Nonecovered by 167.202.192.0/19 672 100% 67
167.202.221.0/24 No ROA Nonecovered by 167.202.192.0/19 672 100% 67
167.202.222.0/24 No ROA Nonecovered by 167.202.192.0/19 672 100% 67
167.202.223.0/24 No ROA Nonecovered by 167.202.192.0/19 672 100% 67
164.140.32.0/22 No ROA Nonecovered by 164.140.0.0/16 671 100% 67
164.140.40.0/22 No ROA Nonecovered by 164.140.0.0/16 671 100% 67
167.202.192.0/19 No ROA Other IRR onlyRADB 672 100% 67
167.202.214.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

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

  • ROA: none12
  • Route object: none10
  • Route object: RIR2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none167.202.195.0/24No ROA covers it. Add a ROA for AS13169, maxLength 24.672 of 673
Route object: none167.202.195.0/24No route object for it. A route object for 167.202.192.0/19 with origin AS13169 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13169 in the RIR database for the space.672 of 673
ROA: none167.202.201.0/24No ROA covers it. Add a ROA for AS13169, maxLength 24.672 of 673
Route object: none167.202.201.0/24No route object for it. A route object for 167.202.192.0/19 with origin AS13169 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13169 in the RIR database for the space.672 of 673
ROA: none167.202.205.0/24No ROA covers it. Add a ROA for AS13169, maxLength 24.672 of 673
Route object: none167.202.205.0/24Route objects for it name AS15916. A route object for 167.202.192.0/19 with origin AS13169 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13169 in the RIR database for the space.672 of 673
ROA: none167.202.212.0/24No ROA covers it. Add a ROA for AS13169, maxLength 24.672 of 673
Route object: none167.202.212.0/24Route objects for it name AS15916. A route object for 167.202.192.0/19 with origin AS13169 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13169 in the RIR database for the space.672 of 673
ROA: none167.202.220.0/24No ROA covers it. Add a ROA for AS13169, maxLength 24.672 of 673
Route object: none167.202.220.0/24No route object for it. A route object for 167.202.192.0/19 with origin AS13169 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13169 in the RIR database for the space.672 of 673
ROA: none167.202.221.0/24No ROA covers it. Add a ROA for AS13169, maxLength 24.672 of 673
Route object: none167.202.221.0/24No route object for it. A route object for 167.202.192.0/19 with origin AS13169 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13169 in the RIR database for the space.672 of 673
ROA: none167.202.222.0/24No ROA covers it. Add a ROA for AS13169, maxLength 24.672 of 673
Route object: none167.202.222.0/24No route object for it. A route object for 167.202.192.0/19 with origin AS13169 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13169 in the RIR database for the space.672 of 673
ROA: none167.202.223.0/24No ROA covers it. Add a ROA for AS13169, maxLength 24.672 of 673
Route object: none167.202.223.0/24No route object for it. A route object for 167.202.192.0/19 with origin AS13169 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13169 in the RIR database for the space.672 of 673
ROA: none164.140.32.0/22No ROA covers it. Add a ROA for AS13169, maxLength 22.671 of 673
Route object: none164.140.32.0/22No route object for it. A route object for 164.140.0.0/16 with origin AS13169 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13169 in the RIR database for the space.671 of 673
ROA: none164.140.40.0/22No ROA covers it. Add a ROA for AS13169, maxLength 22.671 of 673
Route object: none164.140.40.0/22No route object for it. A route object for 164.140.0.0/16 with origin AS13169 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13169 in the RIR database for the space.671 of 673
ROA: none167.202.192.0/19No ROA covers it. Add a ROA for AS13169, maxLength 19.672 of 673
Route object: RIR167.202.192.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none167.202.214.0/24No ROA covers it. Add a ROA for AS13169, maxLength 24.672 of 673
Route object: RIR167.202.214.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

164.140.0.0/16RADBNo ROA
164.140.188.0/24RADBNo ROA
164.140.202.0/24RADBNo ROA
164.140.203.0/24RADBNo ROA
2a04:fbc4::/44RIPENo 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.