bgpreport

Network · data from 2026-11-12

AS11278 NINTENDO - Nintendo Of America inc.

Registry name: NINTENDO - Nintendo Of America inc., US · not in PeeringDB

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

Announced routes

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

8.14.212.0/24 No ROA None 672 100% 67
8.45.177.0/24 No ROA None 672 100% 67
192.159.184.0/23 No ROA None 672 100% 67
192.159.184.0/24 No ROA None 672 100% 67
192.159.189.0/24 No ROA Nonecovered by 192.159.188.0/22 672 100% 67
192.159.191.0/24 No ROA Other origin onlycovered by 192.159.188.0/22 672 100% 67
192.195.204.0/24 No ROA None 672 100% 67
205.166.76.0/24 No ROA None 672 100% 67
173.226.198.0/24 No ROA None 671 100% 67
207.108.201.0/24 No ROA None 671 100% 67
2620:a0:e0::/48 No ROA None 636 100% 67
192.159.186.0/24 No ROA Other IRR onlyRADB 672 100% 67
192.159.188.0/22 No ROA Other IRR onlyRADB 672 100% 67
192.159.190.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS11278 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: none11
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none8.14.212.0/24No ROA covers it. Add a ROA for AS11278, maxLength 24.672 of 673
Route object: none8.14.212.0/24No route object for it. Add a route object with origin AS11278 in the RIR database for the space.672 of 673
ROA: none8.45.177.0/24No ROA covers it. Add a ROA for AS11278, maxLength 24.672 of 673
Route object: none8.45.177.0/24No route object for it. Add a route object with origin AS11278 in the RIR database for the space.672 of 673
ROA: none192.159.184.0/23No ROA covers it. Add a ROA for AS11278, maxLength 23.672 of 673
Route object: none192.159.184.0/23No route object for it. Add a route object with origin AS11278 in the RIR database for the space.672 of 673
ROA: none192.159.184.0/24No ROA covers it. Add a ROA for AS11278, maxLength 24.672 of 673
Route object: none192.159.184.0/24No route object for it. Add a route object with origin AS11278 in the RIR database for the space.672 of 673
ROA: none192.159.189.0/24No ROA covers it. Add a ROA for AS11278, maxLength 24.672 of 673
Route object: none192.159.189.0/24No route object for it. A route object for 192.159.188.0/22 with origin AS11278 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11278 in the RIR database for the space.672 of 673
ROA: none192.159.191.0/24No ROA covers it. Add a ROA for AS11278, maxLength 24.672 of 673
Route object: none192.159.191.0/24Route objects for it name AS22552. A route object for 192.159.188.0/22 with origin AS11278 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11278 in the RIR database for the space.672 of 673
ROA: none192.195.204.0/24No ROA covers it. Add a ROA for AS11278, maxLength 24.672 of 673
Route object: none192.195.204.0/24No route object for it. Add a route object with origin AS11278 in the RIR database for the space.672 of 673
ROA: none205.166.76.0/24No ROA covers it. Add a ROA for AS11278, maxLength 24.672 of 673
Route object: none205.166.76.0/24No route object for it. Add a route object with origin AS11278 in the RIR database for the space.672 of 673
ROA: none173.226.198.0/24No ROA covers it. Add a ROA for AS11278, maxLength 24.671 of 673
Route object: none173.226.198.0/24No route object for it. Add a route object with origin AS11278 in the RIR database for the space.671 of 673
ROA: none207.108.201.0/24No ROA covers it. Add a ROA for AS11278, maxLength 24.671 of 673
Route object: none207.108.201.0/24No route object for it. Add a route object with origin AS11278 in the RIR database for the space.671 of 673
ROA: none2620:a0:e0::/48No ROA covers it. Add a ROA for AS11278, maxLength 48.636 of 636
Route object: none2620:a0:e0::/48No route object for it. Add a route object with origin AS11278 in the RIR database for the space.636 of 636
ROA: none192.159.186.0/24No ROA covers it. Add a ROA for AS11278, maxLength 24.672 of 673
Route object: RIR192.159.186.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none192.159.188.0/22No ROA covers it. Add a ROA for AS11278, maxLength 22.672 of 673
Route object: RIR192.159.188.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none192.159.190.0/24No ROA covers it. Add a ROA for AS11278, maxLength 24.672 of 673
Route object: RIR192.159.190.0/24Route 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 AS11278 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.