Network · data from 2026-11-12

AS56013 SDSC - SAMSUNG SDS CHINA

Registry name: SDSC - SAMSUNG SDS CHINA, CN · not in PeeringDB

13IPv4 routes 0.0% RPKI valid · 84.6% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

13No ROA 2 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

4Route objects not announced registered with origin AS56013, seen from no peer

Announced routes

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


103.8.52.0/22	No ROA	None	673 100%	67
103.249.136.0/24	No ROA	None	672 100%	67
103.14.136.0/24	No ROA	Other IRR onlyNTTCOM, RADB	673 100%	67
103.14.137.0/24	No ROA	Other IRR onlyNTTCOM, RADB	673 100%	67
103.14.138.0/24	No ROA	Other IRR onlyNTTCOM, RADB	673 100%	67
103.14.139.0/24	No ROA	Other IRR onlyNTTCOM, RADB	673 100%	67
27.106.204.0/24	No ROA	Other IRR onlyNTTCOM, RADB	672 100%	67
27.106.205.0/24	No ROA	Other IRR onlyNTTCOM, RADB	672 100%	67
27.106.206.0/24	No ROA	Other IRR onlyNTTCOM, RADB	672 100%	67
27.106.207.0/24	No ROA	Other IRR onlyNTTCOM, RADB	672 100%	67
218.249.63.0/24	No ROA	Other IRR onlyNTTCOM, RADB	672 100%	67
218.249.68.0/24	No ROA	Other IRR onlyNTTCOM, RADB	672 100%	67
218.249.156.0/24	No ROA	Other IRR onlyNTTCOM, RADB	672 100%	67

AS-SET

AS56013 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 30 are in fix.csv.

ROA: none13
Route object: none2
Route object: RIR11
Route object: not announced4

Change	Prefix or set	Detail	Full-table peers
ROA: none	103.8.52.0/22	No ROA covers it. Add a ROA for AS56013, maxLength 22.	673 of 673
Route object: none	103.8.52.0/22	No route object for it. Add a route object with origin AS56013 in the RIR database for the space.	673 of 673
ROA: none	103.249.136.0/24	No ROA covers it. Add a ROA for AS56013, maxLength 24.	672 of 673
Route object: none	103.249.136.0/24	No route object for it. Add a route object with origin AS56013 in the RIR database for the space.	672 of 673
ROA: none	103.14.136.0/24	No ROA covers it. Add a ROA for AS56013, maxLength 24.	673 of 673
Route object: RIR	103.14.136.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	103.14.137.0/24	No ROA covers it. Add a ROA for AS56013, maxLength 24.	673 of 673
Route object: RIR	103.14.137.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	103.14.138.0/24	No ROA covers it. Add a ROA for AS56013, maxLength 24.	673 of 673
Route object: RIR	103.14.138.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	103.14.139.0/24	No ROA covers it. Add a ROA for AS56013, maxLength 24.	673 of 673
Route object: RIR	103.14.139.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	27.106.204.0/24	No ROA covers it. Add a ROA for AS56013, maxLength 24.	672 of 673
Route object: RIR	27.106.204.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	672 of 673
ROA: none	27.106.205.0/24	No ROA covers it. Add a ROA for AS56013, maxLength 24.	672 of 673
Route object: RIR	27.106.205.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	672 of 673
ROA: none	27.106.206.0/24	No ROA covers it. Add a ROA for AS56013, maxLength 24.	672 of 673
Route object: RIR	27.106.206.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	672 of 673
ROA: none	27.106.207.0/24	No ROA covers it. Add a ROA for AS56013, maxLength 24.	672 of 673
Route object: RIR	27.106.207.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	672 of 673
ROA: none	218.249.63.0/24	No ROA covers it. Add a ROA for AS56013, maxLength 24.	672 of 673
Route object: RIR	218.249.63.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	672 of 673
ROA: none	218.249.68.0/24	No ROA covers it. Add a ROA for AS56013, maxLength 24.	672 of 673
Route object: RIR	218.249.68.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	672 of 673
ROA: none	218.249.156.0/24	No ROA covers it. Add a ROA for AS56013, maxLength 24.	672 of 673
Route object: RIR	218.249.156.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

103.8.52.0/22

No ROA covers it. Add a ROA for AS56013, maxLength 22.

673 of 673

Route object: none

103.8.52.0/22

No route object for it. Add a route object with origin AS56013 in the RIR database for the space.

673 of 673

ROA: none

103.249.136.0/24

No ROA covers it. Add a ROA for AS56013, maxLength 24.

672 of 673

Route object: none

103.249.136.0/24

No route object for it. Add a route object with origin AS56013 in the RIR database for the space.

672 of 673

ROA: none

103.14.136.0/24

No ROA covers it. Add a ROA for AS56013, maxLength 24.

673 of 673

Route object: RIR

103.14.136.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

103.14.137.0/24

No ROA covers it. Add a ROA for AS56013, maxLength 24.

673 of 673

Route object: RIR

103.14.137.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

103.14.138.0/24

No ROA covers it. Add a ROA for AS56013, maxLength 24.

673 of 673

Route object: RIR

103.14.138.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

103.14.139.0/24

No ROA covers it. Add a ROA for AS56013, maxLength 24.

673 of 673

Route object: RIR

103.14.139.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

27.106.204.0/24

No ROA covers it. Add a ROA for AS56013, maxLength 24.

672 of 673

Route object: RIR

27.106.204.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

672 of 673

ROA: none

27.106.205.0/24

No ROA covers it. Add a ROA for AS56013, maxLength 24.

672 of 673

Route object: RIR

27.106.205.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

672 of 673

ROA: none

27.106.206.0/24

No ROA covers it. Add a ROA for AS56013, maxLength 24.

672 of 673

Route object: RIR

27.106.206.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

672 of 673

ROA: none

27.106.207.0/24

No ROA covers it. Add a ROA for AS56013, maxLength 24.

672 of 673

Route object: RIR

27.106.207.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

672 of 673

ROA: none

218.249.63.0/24

No ROA covers it. Add a ROA for AS56013, maxLength 24.

672 of 673

Route object: RIR

218.249.63.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

672 of 673

ROA: none

218.249.68.0/24

No ROA covers it. Add a ROA for AS56013, maxLength 24.

672 of 673

Route object: RIR

218.249.68.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

672 of 673

ROA: none

218.249.156.0/24

No ROA covers it. Add a ROA for AS56013, maxLength 24.

672 of 673

Route object: RIR

218.249.156.0/24

Route object only in NTTCOM, RADB. Add it in the RIR database for the space.

672 of 673

Route objects not announced

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


103.8.52.0/24	NTTCOM, RADB	No ROA
103.8.53.0/24	NTTCOM, RADB	No ROA
103.8.54.0/24	NTTCOM, RADB	No ROA
103.8.55.0/24	NTTCOM, RADB	No ROA

103.8.52.0/24

NTTCOM, RADB

No ROA

103.8.53.0/24

NTTCOM, RADB

No ROA

103.8.54.0/24

NTTCOM, RADB

No ROA

103.8.55.0/24

NTTCOM, RADB

No 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.