Network · data from 2026-11-12

AS10126 Taiwan Internet Gateway

Registry name: CHTI-IP-AP - Taiwan Internet Gateway, TW · PeeringDB

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

2IPv6 routes 100.0% RPKI valid · 0.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

18Route objects not announced registered with origin AS10126, seen from no peer

Announced routes

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


2606:c00:32::/48	Valid	None	636 100%	67
2606:c00:35::/48	Valid	Other origin only	636 100%	67
114.30.32.0/20	Valid	Other IRR onlyRADB	672 100%	67
175.111.192.0/18	Valid	Other IRR onlyRADB	672 100%	67
175.111.250.0/24	Valid	Other IRR onlyRADB	672 100%	67
175.111.251.0/24	Valid	Other IRR onlyRADB	672 100%	67
203.160.240.0/20	Valid	Other IRR onlyRADB	672 100%	67
220.128.56.0/21	Valid	Other IRR onlyRADB	672 100%	67
220.128.64.0/20	Valid	Other IRR onlyNTTCOM, RADB	672 100%	67
220.128.80.0/20	Valid	Other IRR onlyNTTCOM, RADB	672 100%	67
220.128.91.0/24	Valid	Other IRR onlyRADB	671 100%	67
175.111.253.0/24	Valid	Other IRR onlyRADB	670 100%	67

AS-SET

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

Route object: none2
Route object: RIR10
Route object: not announced18

Change	Prefix or set	Detail	Full-table peers
Route object: none	2606:c00:32::/48	No route object for it. Add a route object with origin AS10126 in the RIR database for the space.	636 of 636
Route object: none	2606:c00:35::/48	Route objects for it name AS9505. Add a route object with origin AS10126 in the RIR database for the space.	636 of 636
Route object: RIR	114.30.32.0/20	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	175.111.192.0/18	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	175.111.250.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	175.111.251.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	203.160.240.0/20	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	220.128.56.0/21	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	220.128.64.0/20	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	220.128.80.0/20	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	220.128.91.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	175.111.253.0/24	Route object only in RADB. Add it in the RIR database for the space.	670 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

2606:c00:32::/48

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

636 of 636

Route object: none

2606:c00:35::/48

Route objects for it name AS9505. Add a route object with origin AS10126 in the RIR database for the space.

636 of 636

Route object: RIR

114.30.32.0/20

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

672 of 673

Route object: RIR

175.111.192.0/18

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

672 of 673

Route object: RIR

175.111.250.0/24

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

672 of 673

Route object: RIR

175.111.251.0/24

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

672 of 673

Route object: RIR

203.160.240.0/20

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

672 of 673

Route object: RIR

220.128.56.0/21

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

672 of 673

Route object: RIR

220.128.64.0/20

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

672 of 673

Route object: RIR

220.128.80.0/20

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

672 of 673

Route object: RIR

220.128.91.0/24

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

671 of 673

Route object: RIR

175.111.253.0/24

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

670 of 673

Route objects not announced

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


114.30.43.0/24	RADB	Valid
114.30.46.0/24	NTTCOM, RADB	Valid
175.111.255.0/24	RADB	Valid
203.160.242.0/24	RADB	Valid
203.160.243.0/24	NTTCOM, RADB	Valid
203.160.250.0/24	NTTCOM, RADB	Valid
220.128.61.0/24	NTTCOM, RADB	Valid
220.128.70.0/24	NTTCOM, RADB	Valid
220.128.71.0/24	NTTCOM, RADB	Valid
220.128.74.0/24	NTTCOM, RADB	Valid
220.128.75.0/24	NTTCOM, RADB	Valid
220.128.79.0/24	NTTCOM, RADB	Valid
220.128.84.0/24	NTTCOM, RADB	Valid
220.128.88.0/22	NTTCOM, RADB	Valid
220.128.88.0/24	RADB	Valid
220.128.89.0/24	RADB	Valid
220.128.93.0/24	NTTCOM, RADB	Valid
2606:c00:8000::/34	RADB	Valid

114.30.43.0/24

RADB

Valid

114.30.46.0/24

NTTCOM, RADB

Valid

175.111.255.0/24

RADB

Valid

203.160.242.0/24

RADB

Valid

203.160.243.0/24

NTTCOM, RADB

Valid

203.160.250.0/24

NTTCOM, RADB

Valid

220.128.61.0/24

NTTCOM, RADB

Valid

220.128.70.0/24

NTTCOM, RADB

Valid

220.128.71.0/24

NTTCOM, RADB

Valid

220.128.74.0/24

NTTCOM, RADB

Valid

220.128.75.0/24

NTTCOM, RADB

Valid

220.128.79.0/24

NTTCOM, RADB

Valid

220.128.84.0/24

NTTCOM, RADB

Valid

220.128.88.0/22

NTTCOM, RADB

Valid

220.128.88.0/24

RADB

Valid

220.128.89.0/24

RADB

Valid

220.128.93.0/24

NTTCOM, RADB

Valid

2606:c00:8000::/34

RADB

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.