Network · data from 2026-11-12

AS131127 GTEL-VN - GLOBAL TECHNOLOGY - TELECOMMUNICATIONS CORPORATION

Registry name: GTEL-VN - GLOBAL TECHNOLOGY - TELECOMMUNICATIONS CORPORATION, VN · not in PeeringDB

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

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

44Route objects not announced registered with origin AS131127, seen from no peer

Announced routes

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


183.91.160.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	66
183.91.184.0/22	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	66
183.91.188.0/22	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	66
183.91.161.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
183.91.168.0/23	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	66
183.91.168.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	66
183.91.169.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	66
183.91.171.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	66
183.91.172.0/22	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	66
183.91.172.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	66
183.91.176.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	66
183.91.180.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	66
183.91.184.0/21	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	66
183.91.176.0/21	Valid	RIR databaseAPNIC, NTTCOM, RADB	1 0%low visibility	1
183.91.184.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	1 0%low visibility	1
183.91.185.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	1 0%low visibility	1
183.91.186.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	1 0%low visibility	1
183.91.187.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	1 0%low visibility	1
183.91.188.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	1 0%low visibility	1
183.91.189.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	1 0%low visibility	1

183.91.160.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

673 100%

183.91.184.0/22

Valid

RIR databaseAPNIC, NTTCOM, RADB

673 100%

183.91.188.0/22

Valid

RIR databaseAPNIC, NTTCOM, RADB

673 100%

183.91.161.0/24

Valid

RIR databaseAPNIC, RADB

672 100%

183.91.168.0/23

Valid

RIR databaseAPNIC, NTTCOM, RADB

672 100%

183.91.168.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

672 100%

183.91.169.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

672 100%

183.91.171.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

672 100%

183.91.172.0/22

Valid

RIR databaseAPNIC, NTTCOM, RADB

672 100%

183.91.172.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

672 100%

183.91.176.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

672 100%

183.91.180.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

672 100%

183.91.184.0/21

Valid

RIR databaseAPNIC, NTTCOM, RADB

672 100%

183.91.176.0/21

Valid

RIR databaseAPNIC, NTTCOM, RADB

1 0%low visibility

183.91.184.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

1 0%low visibility

183.91.185.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

1 0%low visibility

183.91.186.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

1 0%low visibility

183.91.187.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

1 0%low visibility

183.91.188.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

1 0%low visibility

183.91.189.0/24

Valid

RIR databaseAPNIC, NTTCOM, RADB

1 0%low visibility

AS-SET

AS131127 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 44 are in fix.csv.

Route object: not announced44

Route objects not announced

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


183.91.160.0/19	APNIC, NTTCOM, RADB	Valid
183.91.160.0/20	APNIC, NTTCOM, RADB	Valid
183.91.160.0/21	APNIC, NTTCOM, RADB	Valid
183.91.160.0/22	APNIC, NTTCOM, RADB	Valid
183.91.160.0/23	APNIC, NTTCOM, RADB	Valid
183.91.162.0/23	APNIC, NTTCOM, RADB	Valid
183.91.162.0/24	APNIC, NTTCOM, RADB	Valid
183.91.163.0/24	APNIC, NTTCOM, RADB	Valid
183.91.164.0/22	APNIC, NTTCOM, RADB	Valid
183.91.164.0/23	APNIC, NTTCOM, RADB	Valid
183.91.164.0/24	APNIC, NTTCOM, RADB	Valid
183.91.165.0/24	APNIC, NTTCOM, RADB	Valid
183.91.166.0/23	APNIC, NTTCOM, RADB	Valid
183.91.166.0/24	APNIC, NTTCOM, RADB	Valid
183.91.167.0/24	APNIC, NTTCOM, RADB	Valid
183.91.168.0/21	APNIC, NTTCOM, RADB	Valid
183.91.168.0/22	APNIC, NTTCOM, RADB	Valid
183.91.170.0/23	APNIC, NTTCOM, RADB	Valid
183.91.170.0/24	APNIC, NTTCOM, RADB	Valid
183.91.172.0/23	APNIC, NTTCOM, RADB	Valid
183.91.173.0/24	APNIC, NTTCOM, RADB	Valid
183.91.174.0/23	APNIC, NTTCOM, RADB	Valid
183.91.174.0/24	APNIC, NTTCOM, RADB	Valid
183.91.175.0/24	APNIC, NTTCOM, RADB	Valid
183.91.176.0/20	APNIC, NTTCOM, RADB	Valid
183.91.176.0/22	APNIC, NTTCOM, RADB	Valid
183.91.176.0/23	APNIC, NTTCOM, RADB	Valid
183.91.177.0/24	APNIC, NTTCOM, RADB	Valid
183.91.178.0/23	APNIC, NTTCOM, RADB	Valid
183.91.178.0/24	APNIC, NTTCOM, RADB	Valid
183.91.179.0/24	APNIC, NTTCOM, RADB	Valid
183.91.180.0/22	APNIC, NTTCOM, RADB	Valid
183.91.180.0/23	APNIC, NTTCOM, RADB	Valid
183.91.181.0/24	APNIC, NTTCOM, RADB	Valid
183.91.182.0/23	APNIC, NTTCOM, RADB	Valid
183.91.182.0/24	APNIC, NTTCOM, RADB	Valid
183.91.183.0/24	APNIC, NTTCOM, RADB	Valid
183.91.184.0/23	APNIC, NTTCOM, RADB	Valid
183.91.186.0/23	APNIC, NTTCOM, RADB	Valid
183.91.188.0/23	APNIC, NTTCOM, RADB	Valid
183.91.190.0/23	APNIC, NTTCOM, RADB	Valid
183.91.190.0/24	APNIC, NTTCOM, RADB	Valid
183.91.191.0/24	APNIC, NTTCOM, RADB	Valid
2401:d460::/32	APNIC	Valid

183.91.160.0/19

APNIC, NTTCOM, RADB

Valid

183.91.160.0/20

APNIC, NTTCOM, RADB

Valid

183.91.160.0/21

APNIC, NTTCOM, RADB

Valid

183.91.160.0/22

APNIC, NTTCOM, RADB

Valid

183.91.160.0/23

APNIC, NTTCOM, RADB

Valid

183.91.162.0/23

APNIC, NTTCOM, RADB

Valid

183.91.162.0/24

APNIC, NTTCOM, RADB

Valid

183.91.163.0/24

APNIC, NTTCOM, RADB

Valid

183.91.164.0/22

APNIC, NTTCOM, RADB

Valid

183.91.164.0/23

APNIC, NTTCOM, RADB

Valid

183.91.164.0/24

APNIC, NTTCOM, RADB

Valid

183.91.165.0/24

APNIC, NTTCOM, RADB

Valid

183.91.166.0/23

APNIC, NTTCOM, RADB

Valid

183.91.166.0/24

APNIC, NTTCOM, RADB

Valid

183.91.167.0/24

APNIC, NTTCOM, RADB

Valid

183.91.168.0/21

APNIC, NTTCOM, RADB

Valid

183.91.168.0/22

APNIC, NTTCOM, RADB

Valid

183.91.170.0/23

APNIC, NTTCOM, RADB

Valid

183.91.170.0/24

APNIC, NTTCOM, RADB

Valid

183.91.172.0/23

APNIC, NTTCOM, RADB

Valid

183.91.173.0/24

APNIC, NTTCOM, RADB

Valid

183.91.174.0/23

APNIC, NTTCOM, RADB

Valid

183.91.174.0/24

APNIC, NTTCOM, RADB

Valid

183.91.175.0/24

APNIC, NTTCOM, RADB

Valid

183.91.176.0/20

APNIC, NTTCOM, RADB

Valid

183.91.176.0/22

APNIC, NTTCOM, RADB

Valid

183.91.176.0/23

APNIC, NTTCOM, RADB

Valid

183.91.177.0/24

APNIC, NTTCOM, RADB

Valid

183.91.178.0/23

APNIC, NTTCOM, RADB

Valid

183.91.178.0/24

APNIC, NTTCOM, RADB

Valid

183.91.179.0/24

APNIC, NTTCOM, RADB

Valid

183.91.180.0/22

APNIC, NTTCOM, RADB

Valid

183.91.180.0/23

APNIC, NTTCOM, RADB

Valid

183.91.181.0/24

APNIC, NTTCOM, RADB

Valid

183.91.182.0/23

APNIC, NTTCOM, RADB

Valid

183.91.182.0/24

APNIC, NTTCOM, RADB

Valid

183.91.183.0/24

APNIC, NTTCOM, RADB

Valid

183.91.184.0/23

APNIC, NTTCOM, RADB

Valid

183.91.186.0/23

APNIC, NTTCOM, RADB

Valid

183.91.188.0/23

APNIC, NTTCOM, RADB

Valid

183.91.190.0/23

APNIC, NTTCOM, RADB

Valid

183.91.190.0/24

APNIC, NTTCOM, RADB

Valid

183.91.191.0/24

APNIC, NTTCOM, RADB

Valid

2401:d460::/32

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.