Network · data from 2026-11-12

AS136617 Fortune Telecom Company

Registry name: FTCL-AS-AP - Fortune Telecom Company Limited, MM · PeeringDB

10IPv4 routes 100.0% RPKI valid · 100.0% with a route object

2IPv6 routes 50.0% RPKI valid · 50.0% with a route object

1RPKI invalid 0 origin · 1 maxLength

0No ROA 1 with no route object for this origin

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

2Route objects not announced registered with origin AS136617, seen from no peer

Announced routes

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


2401:35c0::/48	Invalid: maxLength	Nonecovered by 2401:35c0::/32	7 1%low visibility	5
203.109.36.0/22	Valid	RIR databaseAPNIC, RADB	673 100%	68
203.109.36.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
203.109.37.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	67
203.109.38.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
203.109.39.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
103.94.68.0/22	Valid	RIR databaseAPNIC, RADB	672 100%	67
103.94.68.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.94.69.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.94.70.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
103.94.71.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	67
2401:35c0::/32	Valid	RIR databaseAPNIC	635 100%	69

2401:35c0::/48

Invalid: maxLength

Nonecovered by 2401:35c0::/32

7 1%low visibility

203.109.36.0/22

Valid

RIR databaseAPNIC, RADB

673 100%

203.109.36.0/24

Valid

RIR databaseAPNIC, RADB

673 100%

203.109.37.0/24

Valid

RIR databaseAPNIC, RADB

673 100%

203.109.38.0/24

Valid

RIR databaseAPNIC, RADB

673 100%

203.109.39.0/24

Valid

RIR databaseAPNIC, RADB

673 100%

103.94.68.0/22

Valid

RIR databaseAPNIC, RADB

672 100%

103.94.68.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

672 100%

103.94.69.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

672 100%

103.94.70.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

672 100%

103.94.71.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

672 100%

2401:35c0::/32

Valid

RIR databaseAPNIC

635 100%

AS-SET

AS136617's PeeringDB record names no 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 4 are in fix.csv.

ROA: maxLength1
Route object: none1
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	2401:35c0::/48	ROA 2401:35c0::/32 AS136617 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2401:35c0::/48.	7 of 636
Route object: none	2401:35c0::/48	No route object for it. A route object for 2401:35c0::/32 with origin AS136617 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136617 in the RIR database for the space.	7 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

2401:35c0::/48

ROA 2401:35c0::/32 AS136617 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2401:35c0::/48.

7 of 636

Route object: none

2401:35c0::/48

No route object for it. A route object for 2401:35c0::/32 with origin AS136617 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136617 in the RIR database for the space.

7 of 636

Route objects not announced

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


103.94.68.0/23	APNIC	Valid
103.94.70.0/23	APNIC	Valid

103.94.68.0/23

APNIC

Valid

103.94.70.0/23

APNIC

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.