bgpreport

Network · data from 2026-11-12

AS54535 NIKEUS-NV - Nike, Inc.

Registry name: NIKEUS-NV - Nike, Inc., US · not in PeeringDB

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

Announced routes

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

146.197.27.0/24 Valid RIR databaseARIN 673 100% 67
146.197.63.0/24 Valid RIR databaseARIN 673 100% 67
146.197.79.0/24 Valid RIR databaseARIN 673 100% 67
146.197.83.0/24 Valid RIR databaseARIN 673 100% 67
146.197.120.0/22 Valid RIR databaseARIN 673 100% 67
146.197.122.0/24 Valid RIR databaseARIN 673 100% 67
146.197.123.0/24 Valid RIR databaseARIN 673 100% 67
146.197.199.0/24 Valid RIR databaseARIN, RADB 673 100% 67
146.197.242.0/24 Valid RIR databaseARIN 673 100% 67
146.197.246.0/24 Valid RIR databaseARIN 673 100% 67
156.37.196.0/24 Valid RIR databaseALTDB, ARIN 673 100% 67
156.37.197.0/24 Valid RIR databaseALTDB, ARIN 673 100% 67
156.37.198.0/24 Valid RIR databaseALTDB, ARIN 673 100% 67
156.37.200.0/24 Valid RIR databaseALTDB, ARIN 673 100% 67
156.37.201.0/24 Valid RIR databaseALTDB, ARIN 673 100% 67
156.37.202.0/24 Valid RIR databaseARIN 673 100% 67
156.37.203.0/24 Valid RIR databaseARIN 673 100% 67
156.37.204.0/24 Valid RIR databaseALTDB, ARIN 673 100% 67
156.37.205.0/24 Valid RIR databaseALTDB, ARIN 673 100% 66
156.37.224.0/23 Valid RIR databaseARIN, RADB 673 100% 66
156.37.232.0/23 Valid RIR databaseARIN 673 100% 67
156.37.250.0/24 Valid RIR databaseARIN 673 100% 67
156.37.251.0/24 Valid RIR databaseARIN 673 100% 67
156.37.253.0/24 Valid RIR databaseARIN 673 100% 67
156.53.198.0/24 Valid RIR databaseARIN, RADB 673 100% 67
156.53.199.0/24 Valid RIR databaseARIN, RADB 673 100% 67
156.53.200.0/24 Valid RIR databaseALTDB, ARIN 673 100% 67
156.53.201.0/24 Valid RIR databaseALTDB, ARIN 673 100% 67
156.53.224.0/23 Valid RIR databaseARIN, RADB 673 100% 67
156.53.232.0/23 Valid RIR databaseARIN 673 100% 67
156.53.240.0/22 Valid RIR databaseALTDB, ARIN 673 100% 67
156.53.240.0/23 Valid RIR databaseARIN 673 100% 67
156.53.240.0/24 Valid RIR databaseARIN 673 100% 67
156.53.241.0/24 Valid RIR databaseARIN 673 100% 67
156.53.242.0/23 Valid RIR databaseARIN 673 100% 67
156.53.242.0/24 Valid RIR databaseARIN 673 100% 67
156.53.243.0/24 Valid RIR databaseARIN 673 100% 67
146.197.44.0/23 Valid RIR databaseARIN, RADB 672 100% 67
146.197.50.0/23 Valid RIR databaseARIN, RADB 672 100% 67
146.197.52.0/23 Valid RIR databaseARIN, RADB 672 100% 67
146.197.60.0/23 Valid RIR databaseARIN 672 100% 67
146.197.176.0/22 Valid RIR databaseARIN, RADB 672 100% 67
146.197.184.0/23 Valid RIR databaseARIN 672 100% 67
146.197.188.0/23 Valid RIR databaseARIN, RADB 672 100% 67
146.197.198.0/24 Valid RIR databaseARIN, RADB 672 100% 67
146.197.62.0/24 Valid RIR databaseARIN 671 100% 67

AS-SET

AS54535 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 90 are in fix.csv.

  • Route object: not announced90

Route objects not announced

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

69.25.126.0/24RADBNo ROA
146.197.16.0/23RADBNo ROA
146.197.16.0/24ALTDBNo ROA
146.197.17.0/24RADBNo ROA
146.197.46.0/23RADBNo ROA
146.197.186.0/23RADBNo ROA
146.197.190.0/23RADBNo ROA
146.197.192.0/23RADBNo ROA
146.197.194.0/23RADBNo ROA
146.197.198.0/23RADBNo ROA
146.197.200.0/23RADBNo ROA
146.197.200.0/24RADBNo ROA
156.37.192.0/24ARIN, RADBValid
156.37.193.0/24ARINValid
156.37.194.0/23ARINValid
156.37.198.0/23RADBNo ROA
156.37.200.0/23RADBNo ROA
173.205.134.0/24RADBNo ROA
173.205.135.0/24RADBNo ROA
173.205.158.0/24RADBNo ROA
173.205.159.0/24RADBNo ROA
173.205.160.0/24RADBNo ROA
173.205.161.0/24RADBNo ROA
173.205.168.0/24RADBNo ROA
173.205.169.0/24RADBNo ROA
173.205.178.0/24RADBNo ROA
173.205.179.0/24RADBNo ROA
173.205.182.0/24RADBNo ROA
173.205.183.0/24RADBNo ROA
173.205.202.0/24RADBNo ROA
173.205.203.0/24RADBNo ROA
173.245.106.0/24RADBNo ROA
173.245.107.0/24RADBNo ROA
174.128.130.0/24RADBNo ROA
174.128.131.0/24RADBNo ROA
174.128.146.0/24RADBNo ROA
174.128.147.0/24RADBNo ROA
194.37.195.0/24RADBNo ROA
206.246.69.0/24RADBNo ROA
206.246.70.0/24RADBNo ROA
206.246.72.0/24RADBNo ROA
206.246.76.0/24RADBNo ROA
206.246.78.0/24RADBNo ROA
206.246.79.0/24RADBNo ROA
206.246.80.0/24RADBNo ROA
206.246.81.0/24RADBNo ROA
206.246.83.0/24RADBNo ROA
206.246.86.0/24RADBNo ROA
206.246.87.0/24RADBNo ROA
206.246.88.0/24RADBNo ROA
206.246.91.0/24RADBNo ROA
206.246.92.0/24RADBNo ROA
206.246.96.0/24RADBNo ROA
206.246.99.0/24RADBNo ROA
206.246.100.0/24RADBNo ROA
206.246.101.0/24RADBNo ROA
206.246.103.0/24RADBNo ROA
207.199.137.0/24RADBNo ROA
207.199.138.0/24RADBNo ROA
207.199.141.0/24RADBNo ROA
207.199.142.0/24RADBNo ROA
207.199.160.0/24RADBNo ROA
207.199.162.0/24RADBNo ROA
207.199.164.0/24RADBNo ROA
207.199.166.0/24RADBNo ROA
207.199.168.0/24RADBNo ROA
207.199.169.0/24RADBNo ROA
207.199.170.0/24RADBNo ROA
207.199.180.0/24RADBNo ROA
207.199.181.0/24RADBNo ROA
207.199.182.0/24RADBNo ROA
207.199.183.0/24RADBNo ROA
207.199.184.0/24RADBNo ROA
207.199.185.0/24RADBNo ROA
207.199.186.0/24RADBNo ROA
207.199.187.0/24RADBNo ROA
209.147.65.0/24RADBNo ROA
216.107.33.0/24RADBNo ROA
216.107.34.0/24RADBNo ROA
216.107.35.0/24RADBNo ROA
216.107.50.0/24RADBNo ROA
216.107.51.0/24RADBNo ROA
216.155.17.0/24RADBNo ROA
216.155.19.0/24RADBNo ROA
216.155.23.0/24RADBNo ROA
216.155.24.0/24RADBNo ROA
216.155.28.0/24RADBNo ROA
216.155.29.0/24RADBNo ROA
216.155.31.0/24RADBNo ROA
216.155.33.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.