bgpreport

Network · data from 2026-11-12

AS18258 MS-JP-AS-AP - Morgan Stanley Japan Limited

Registry name: MS-JP-AS-AP - Morgan Stanley Japan Limited, JP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18258, 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.228.96.0/24 No ROA RIR databaseARIN, NTTCOM, RADB 673 100% 67
205.228.104.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
205.228.108.0/24 No ROA RIR databaseARIN, NTTCOM 673 100% 67
205.228.118.0/24 No ROA RIR databaseARIN 673 100% 67
205.228.123.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
209.8.176.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67

AS-SET

AS18258 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 63 are in fix.csv.

  • ROA: none5
  • Route object: not announced58
ChangePrefix or setDetailFull-table peers
ROA: none205.228.96.0/24No ROA covers it. Add a ROA for AS18258, maxLength 24.673 of 673
ROA: none205.228.104.0/24No ROA covers it. Add a ROA for AS18258, maxLength 24.673 of 673
ROA: none205.228.108.0/24No ROA covers it. Add a ROA for AS18258, maxLength 24.673 of 673
ROA: none205.228.118.0/24No ROA covers it. Add a ROA for AS18258, maxLength 24.673 of 673
ROA: none205.228.123.0/24No ROA covers it. Add a ROA for AS18258, maxLength 24.673 of 673

Route objects not announced

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

205.228.96.0/19NTTCOM, RADBNo ROA
205.228.96.0/20NTTCOMNo ROA
205.228.96.0/21ARINNo ROA
205.228.96.0/22ARINNo ROA
205.228.96.0/23ARINNo ROA
205.228.97.0/24ARINNo ROA
205.228.98.0/23ARINNo ROA
205.228.98.0/24ARINNo ROA
205.228.99.0/24ARINNo ROA
205.228.100.0/22ARINNo ROA
205.228.100.0/23ARINNo ROA
205.228.100.0/24ARINNo ROA
205.228.101.0/24ARINNo ROA
205.228.102.0/23ARINNo ROA
205.228.102.0/24ARINNo ROA
205.228.103.0/24ARINNo ROA
205.228.104.0/21ARINNo ROA
205.228.104.0/22ARINNo ROA
205.228.104.0/23ARINNo ROA
205.228.105.0/24ARINNo ROA
205.228.106.0/23ARINNo ROA
205.228.106.0/24ARINNo ROA
205.228.107.0/24ARINNo ROA
205.228.108.0/22ARINNo ROA
205.228.108.0/23ARINNo ROA
205.228.109.0/24ARINNo ROA
205.228.110.0/23ARINNo ROA
205.228.110.0/24ARINNo ROA
205.228.111.0/24ARINNo ROA
205.228.112.0/20ARIN, NTTCOMNo ROA
205.228.112.0/21ARINNo ROA
205.228.112.0/22ARINNo ROA
205.228.112.0/23ARINNo ROA
205.228.112.0/24ARINNo ROA
205.228.113.0/24ARINNo ROA
205.228.114.0/23ARINNo ROA
205.228.114.0/24ARINNo ROA
205.228.115.0/24ARINNo ROA
205.228.116.0/22ARINNo ROA
205.228.116.0/23ARINNo ROA
205.228.116.0/24ARINNo ROA
205.228.117.0/24ARINNo ROA
205.228.118.0/23ARINNo ROA
205.228.119.0/24ARINNo ROA
205.228.120.0/21ARINNo ROA
205.228.120.0/22ARINNo ROA
205.228.120.0/23ARINNo ROA
205.228.120.0/24ARINNo ROA
205.228.121.0/24ARINNo ROA
205.228.122.0/23ARINNo ROA
205.228.122.0/24ARINNo ROA
205.228.124.0/22ARINNo ROA
205.228.124.0/23ARINNo ROA
205.228.124.0/24ARINNo ROA
205.228.125.0/24ARINNo ROA
205.228.126.0/23ARINNo ROA
205.228.126.0/24ARINNo ROA
205.228.127.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.