bgpreport

Network · data from 2026-11-12

AS11289 AS11289 - SANDISK TECHNOLOGIES, INC.

Registry name: AS11289 - SANDISK TECHNOLOGIES, INC., US · not in PeeringDB

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

Announced routes

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

129.253.204.0/22 No ROA RIR databaseARIN 672 100% 66
129.253.204.0/23 No ROA RIR databaseARIN 672 100% 66
129.253.220.0/24 No ROA RIR databaseARIN 672 100% 67
129.253.222.0/24 No ROA RIR databaseARIN 672 100% 67
129.253.223.0/24 No ROA RIR databaseARIN 672 100% 67
129.253.240.0/22 No ROA RIR databaseARIN 672 100% 66
129.253.208.0/22 No ROA RIR databaseARIN 670 100% 67
129.253.208.0/23 No ROA RIR databaseARIN 670 100% 67
129.253.212.0/22 No ROA RIR databaseARIN, RADB 670 100% 67
129.253.212.0/23 No ROA RIR databaseARIN, RADB 670 100% 67
129.253.216.0/22 No ROA RIR databaseARIN 669 99% 67
129.253.217.0/24 No ROA RIR databaseARIN 669 99% 67

AS-SET

AS11289 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 41 are in fix.csv.

  • ROA: none12
  • Route object: not announced29
ChangePrefix or setDetailFull-table peers
ROA: none129.253.204.0/22No ROA covers it. Add a ROA for AS11289, maxLength 22.672 of 673
ROA: none129.253.204.0/23No ROA covers it. Add a ROA for AS11289, maxLength 23.672 of 673
ROA: none129.253.220.0/24No ROA covers it. Add a ROA for AS11289, maxLength 24.672 of 673
ROA: none129.253.222.0/24No ROA covers it. Add a ROA for AS11289, maxLength 24.672 of 673
ROA: none129.253.223.0/24No ROA covers it. Add a ROA for AS11289, maxLength 24.672 of 673
ROA: none129.253.240.0/22No ROA covers it. Add a ROA for AS11289, maxLength 22.672 of 673
ROA: none129.253.208.0/22No ROA covers it. Add a ROA for AS11289, maxLength 22.670 of 673
ROA: none129.253.208.0/23No ROA covers it. Add a ROA for AS11289, maxLength 23.670 of 673
ROA: none129.253.212.0/22No ROA covers it. Add a ROA for AS11289, maxLength 22.670 of 673
ROA: none129.253.212.0/23No ROA covers it. Add a ROA for AS11289, maxLength 23.670 of 673
ROA: none129.253.216.0/22No ROA covers it. Add a ROA for AS11289, maxLength 22.669 of 673
ROA: none129.253.217.0/24No ROA covers it. Add a ROA for AS11289, maxLength 24.669 of 673

Route objects not announced

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

129.253.204.0/24ARINNo ROA
129.253.205.0/24ARINNo ROA
129.253.206.0/23ARINNo ROA
129.253.206.0/24ARINNo ROA
129.253.207.0/24ARINNo ROA
129.253.208.0/24ARINNo ROA
129.253.209.0/24ARINNo ROA
129.253.210.0/23ARINNo ROA
129.253.210.0/24ARINNo ROA
129.253.211.0/24ARINNo ROA
129.253.212.0/24ARIN, RADBNo ROA
129.253.213.0/24ARIN, RADBNo ROA
129.253.214.0/23ARIN, RADBNo ROA
129.253.214.0/24ARIN, RADBNo ROA
129.253.215.0/24ARIN, RADBNo ROA
129.253.216.0/23ARINNo ROA
129.253.216.0/24ARINNo ROA
129.253.218.0/23ARINNo ROA
129.253.218.0/24ARINNo ROA
129.253.219.0/24ARINNo ROA
129.253.220.0/22ARINNo ROA
129.253.220.0/23ARINNo ROA
129.253.221.0/24ARINNo ROA
129.253.222.0/23ARINNo ROA
129.253.240.0/23ARINNo ROA
129.253.240.0/24ARINNo ROA
129.253.241.0/24ARINNo ROA
129.253.242.0/23ARINNo ROA
129.253.243.0/24ARINNo 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.