Network · data from 2026-11-12

AS137551 REDLINK-AS-AP - REDLINK TELECOM Co., Ltd

Registry name: REDLINK-AS-AP - REDLINK TELECOM Co., Ltd, KH · not in PeeringDB

20IPv4 routes 95.0% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

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

41Route objects not announced registered with origin AS137551, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS137551, 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.121.188.0/22	No ROA	Other IRR onlyNTTCOM, RADB	673 100%	66
103.112.240.0/22	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	66
103.112.240.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	67
103.112.241.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	67
103.112.242.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	67
103.112.243.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	67
103.120.120.0/22	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	66
103.120.120.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	67
103.120.121.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	67
103.121.188.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	66
103.121.189.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	66
103.121.190.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	66
103.121.191.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	66
139.5.132.0/22	Valid	RIR databaseAPNIC, NTTCOM	673 100%	66
79.109.224.0/22	Valid	RIR databaseAPNIC	672 100%	66
79.109.232.0/22	Valid	RIR databaseAPNIC	672 100%	67
103.120.122.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
103.120.123.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
79.109.228.0/22	Valid	RIR databaseAPNIC	671 100%	67
79.109.236.0/22	Valid	RIR databaseAPNIC	670 100%	67

AS-SET

AS137551 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 43 are in fix.csv.

ROA: none1
Route object: RIR1
Route object: not announced41

Change	Prefix or set	Detail	Full-table peers
ROA: none	103.121.188.0/22	No ROA covers it. Add a ROA for AS137551, maxLength 22.	673 of 673
Route object: RIR	103.121.188.0/22	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

103.121.188.0/22

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

673 of 673

Route object: RIR

103.121.188.0/22

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

673 of 673

Route objects not announced

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


38.196.182.0/23	NTTCOM	No ROA
38.196.182.0/24	NTTCOM, RADB	No ROA
38.196.183.0/24	NTTCOM, RADB	No ROA
79.109.224.0/24	APNIC	Valid
79.109.225.0/24	APNIC	Valid
79.109.226.0/24	APNIC	Valid
79.109.227.0/24	APNIC	Valid
79.109.228.0/23	APNIC	Valid
79.109.228.0/24	APNIC	Valid
79.109.229.0/24	APNIC	Valid
79.109.230.0/23	APNIC	Valid
79.109.230.0/24	APNIC	Valid
79.109.231.0/24	APNIC	Valid
79.109.232.0/23	APNIC	Valid
79.109.232.0/24	APNIC	Valid
79.109.233.0/24	APNIC	Valid
79.109.234.0/23	APNIC	Valid
79.109.234.0/24	APNIC	Valid
79.109.235.0/24	APNIC	Valid
79.109.236.0/23	APNIC	Valid
79.109.236.0/24	APNIC	Valid
79.109.237.0/24	APNIC	Valid
79.109.238.0/23	APNIC	Valid
79.109.238.0/24	APNIC	Valid
79.109.239.0/24	APNIC	Valid
103.112.240.0/23	APNIC, NTTCOM, RADB	Valid
103.112.242.0/23	APNIC, NTTCOM, RADB	Valid
103.121.188.0/23	RADB	No ROA
103.121.190.0/23	RADB	No ROA
103.195.0.0/22	APNIC, NTTCOM	Valid
103.195.0.0/23	APNIC	Valid
103.195.0.0/24	APNIC, NTTCOM	Valid
103.195.1.0/24	APNIC, NTTCOM	Valid
103.195.2.0/23	APNIC	Valid
103.195.2.0/24	APNIC, NTTCOM	Valid
103.195.3.0/24	APNIC, NTTCOM	Valid
139.5.132.0/24	APNIC, NTTCOM	Valid
139.5.133.0/24	APNIC, NTTCOM	Valid
139.5.134.0/23	APNIC	Valid
139.5.134.0/24	APNIC, NTTCOM	Valid
139.5.135.0/24	APNIC, NTTCOM	Valid

38.196.182.0/23

NTTCOM

No ROA

38.196.182.0/24

NTTCOM, RADB

No ROA

38.196.183.0/24

NTTCOM, RADB

No ROA

79.109.224.0/24

APNIC

Valid

79.109.225.0/24

APNIC

Valid

79.109.226.0/24

APNIC

Valid

79.109.227.0/24

APNIC

Valid

79.109.228.0/23

APNIC

Valid

79.109.228.0/24

APNIC

Valid

79.109.229.0/24

APNIC

Valid

79.109.230.0/23

APNIC

Valid

79.109.230.0/24

APNIC

Valid

79.109.231.0/24

APNIC

Valid

79.109.232.0/23

APNIC

Valid

79.109.232.0/24

APNIC

Valid

79.109.233.0/24

APNIC

Valid

79.109.234.0/23

APNIC

Valid

79.109.234.0/24

APNIC

Valid

79.109.235.0/24

APNIC

Valid

79.109.236.0/23

APNIC

Valid

79.109.236.0/24

APNIC

Valid

79.109.237.0/24

APNIC

Valid

79.109.238.0/23

APNIC

Valid

79.109.238.0/24

APNIC

Valid

79.109.239.0/24

APNIC

Valid

103.112.240.0/23

APNIC, NTTCOM, RADB

Valid

103.112.242.0/23

APNIC, NTTCOM, RADB

Valid

103.121.188.0/23

RADB

No ROA

103.121.190.0/23

RADB

No ROA

103.195.0.0/22

APNIC, NTTCOM

Valid

103.195.0.0/23

APNIC

Valid

103.195.0.0/24

APNIC, NTTCOM

Valid

103.195.1.0/24

APNIC, NTTCOM

Valid

103.195.2.0/23

APNIC

Valid

103.195.2.0/24

APNIC, NTTCOM

Valid

103.195.3.0/24

APNIC, NTTCOM

Valid

139.5.132.0/24

APNIC, NTTCOM

Valid

139.5.133.0/24

APNIC, NTTCOM

Valid

139.5.134.0/23

APNIC

Valid

139.5.134.0/24

APNIC, NTTCOM

Valid

139.5.135.0/24

APNIC, NTTCOM

Valid

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.