bgpreport

Network · data from 2026-11-12

AS13919 ALLDATA-NET01 - ADS Alliance Data Systems, Inc.

Registry name: ALLDATA-NET01 - ADS Alliance Data Systems, Inc., US · not in PeeringDB

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

Announced routes

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

205.144.62.0/23 No ROA None 673 100% 67
205.144.60.0/23 No ROA None 672 100% 67
205.144.50.0/24 No ROA Nonecovered by 205.144.50.0/23 671 100% 67
205.144.51.0/24 No ROA Nonecovered by 205.144.50.0/23 671 100% 67
205.144.52.0/24 No ROA Nonecovered by 205.144.52.0/23 671 100% 67
205.144.53.0/24 No ROA Nonecovered by 205.144.52.0/23 671 100% 67
205.144.60.0/24 No ROA None 671 100% 67
205.144.61.0/24 No ROA None 671 100% 67
205.144.62.0/24 No ROA None 671 100% 67
205.144.63.0/24 No ROA None 671 100% 67
205.144.53.203/32 No ROA Nonecovered by 205.144.52.0/23 2 0%low visibility 2
205.144.53.205/32 No ROA Nonecovered by 205.144.52.0/23 2 0%low visibility 2
205.144.50.0/23 No ROA Other IRR onlyRADB 672 100% 67
205.144.52.0/23 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS13919 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 28 are in fix.csv.

  • ROA: none14
  • Route object: none12
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none205.144.62.0/23No ROA covers it. Add a ROA for AS13919, maxLength 23.673 of 673
Route object: none205.144.62.0/23No route object for it. Add a route object with origin AS13919 in the RIR database for the space.673 of 673
ROA: none205.144.60.0/23No ROA covers it. Add a ROA for AS13919, maxLength 23.672 of 673
Route object: none205.144.60.0/23No route object for it. Add a route object with origin AS13919 in the RIR database for the space.672 of 673
ROA: none205.144.50.0/24No ROA covers it. Add a ROA for AS13919, maxLength 24.671 of 673
Route object: none205.144.50.0/24No route object for it. A route object for 205.144.50.0/23 with origin AS13919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13919 in the RIR database for the space.671 of 673
ROA: none205.144.51.0/24No ROA covers it. Add a ROA for AS13919, maxLength 24.671 of 673
Route object: none205.144.51.0/24No route object for it. A route object for 205.144.50.0/23 with origin AS13919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13919 in the RIR database for the space.671 of 673
ROA: none205.144.52.0/24No ROA covers it. Add a ROA for AS13919, maxLength 24.671 of 673
Route object: none205.144.52.0/24No route object for it. A route object for 205.144.52.0/23 with origin AS13919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13919 in the RIR database for the space.671 of 673
ROA: none205.144.53.0/24No ROA covers it. Add a ROA for AS13919, maxLength 24.671 of 673
Route object: none205.144.53.0/24No route object for it. A route object for 205.144.52.0/23 with origin AS13919 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13919 in the RIR database for the space.671 of 673
ROA: none205.144.60.0/24No ROA covers it. Add a ROA for AS13919, maxLength 24.671 of 673
Route object: none205.144.60.0/24No route object for it. Add a route object with origin AS13919 in the RIR database for the space.671 of 673
ROA: none205.144.61.0/24No ROA covers it. Add a ROA for AS13919, maxLength 24.671 of 673
Route object: none205.144.61.0/24No route object for it. Add a route object with origin AS13919 in the RIR database for the space.671 of 673
ROA: none205.144.62.0/24No ROA covers it. Add a ROA for AS13919, maxLength 24.671 of 673
Route object: none205.144.62.0/24No route object for it. Add a route object with origin AS13919 in the RIR database for the space.671 of 673
ROA: none205.144.63.0/24No ROA covers it. Add a ROA for AS13919, maxLength 24.671 of 673
Route object: none205.144.63.0/24No route object for it. Add a route object with origin AS13919 in the RIR database for the space.671 of 673
ROA: none205.144.53.203/32No ROA covers it. Add a ROA for AS13919, maxLength 32.2 of 673
Route object: none205.144.53.203/32No route object for it. A route object for 205.144.52.0/23 with origin AS13919 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS13919 in the RIR database for the space.2 of 673
ROA: none205.144.53.205/32No ROA covers it. Add a ROA for AS13919, maxLength 32.2 of 673
Route object: none205.144.53.205/32No route object for it. A route object for 205.144.52.0/23 with origin AS13919 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS13919 in the RIR database for the space.2 of 673
ROA: none205.144.50.0/23No ROA covers it. Add a ROA for AS13919, maxLength 23.672 of 673
Route object: RIR205.144.50.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none205.144.52.0/23No ROA covers it. Add a ROA for AS13919, maxLength 23.672 of 673
Route object: RIR205.144.52.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS13919 is announced.

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.