bgpreport

Network · data from 2026-11-12

AS10082 MS-HK-AS-AP - Morgan Stanley Management Service (Singapore) Pte. Ltd

Registry name: MS-HK-AS-AP - Morgan Stanley Management Service (Singapore) Pte. Ltd, SG · not in PeeringDB

9IPv4 routes 11.1% RPKI valid · 88.9% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
7No ROA 1 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS10082, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS10082, 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.
63.217.82.0/24 Invalid: origin None 2 0%low visibility 2
205.228.106.0/24 No ROA Other IRR onlyRADB 672 100% 66
205.228.109.0/24 No ROA Other IRR onlyRADB 672 100% 66
205.228.111.0/24 No ROA Other IRR onlyRADB 672 100% 66
205.228.124.0/24 No ROA Other IRR onlyRADB 672 100% 66
205.228.99.0/24 No ROA RIR databaseARIN, NTTCOM, RADB 672 100% 66
205.228.101.0/24 No ROA RIR databaseARIN, NTTCOM, RADB 672 100% 66
205.228.102.0/24 No ROA RIR databaseARIN, NTTCOM, RADB 672 100% 66
218.188.93.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 2 0%low visibility 2

AS-SET

AS10082 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 15 are in fix.csv.

  • ROA: origin1
  • ROA: none7
  • Route object: none1
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin63.217.82.0/24ROAs covering it name AS3491, AS31713, not AS10082. If AS10082 should announce it, add a ROA for AS10082.2 of 673
Route object: none63.217.82.0/24No route object for it. Add a route object with origin AS10082 in the RIR database for the space.2 of 673
ROA: none205.228.106.0/24No ROA covers it. Add a ROA for AS10082, maxLength 24.672 of 673
Route object: RIR205.228.106.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none205.228.109.0/24No ROA covers it. Add a ROA for AS10082, maxLength 24.672 of 673
Route object: RIR205.228.109.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none205.228.111.0/24No ROA covers it. Add a ROA for AS10082, maxLength 24.672 of 673
Route object: RIR205.228.111.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none205.228.124.0/24No ROA covers it. Add a ROA for AS10082, maxLength 24.672 of 673
Route object: RIR205.228.124.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none205.228.99.0/24No ROA covers it. Add a ROA for AS10082, maxLength 24.672 of 673
ROA: none205.228.101.0/24No ROA covers it. Add a ROA for AS10082, maxLength 24.672 of 673
ROA: none205.228.102.0/24No ROA covers it. Add a ROA for AS10082, maxLength 24.672 of 673

Route objects not announced

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

205.228.79.0/24NTTCOM, RADBNo ROA
205.228.80.0/24NTTCOM, RADBNo 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.