Network · data from 2026-11-12

AS131623 Shopee Taiwan

Registry name: SPETW-AS - SHOPEE (TAIWAN) CO. LTD., TW · PeeringDB

5IPv4 routes 80.0% RPKI valid · 80.0% with a route object

0IPv6 routes

1RPKI invalid 1 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

1Route objects not announced registered with origin AS131623, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS131623, 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.127.231.0/24	Invalid: origin	Other origin only	14 2%low visibility	11
103.117.4.0/24	Valid	Other IRR onlyNTTCOM, RADB	672 100%	67
103.117.5.0/24	Valid	Other IRR onlyNTTCOM, RADB	672 100%	67
103.117.6.0/24	Valid	Other IRR onlyNTTCOM, RADB	672 100%	67
103.117.7.0/24	Valid	Other IRR onlyNTTCOM, RADB	672 100%	67

103.127.231.0/24

Invalid: origin

Other origin only

14 2%low visibility

103.117.4.0/24

Valid

Other IRR onlyNTTCOM, RADB

672 100%

103.117.5.0/24

Valid

Other IRR onlyNTTCOM, RADB

672 100%

103.117.6.0/24

Valid

Other IRR onlyNTTCOM, RADB

672 100%

103.117.7.0/24

Valid

Other IRR onlyNTTCOM, RADB

672 100%

AS-SET

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

ROA: origin1
Route object: none1
Route object: RIR4
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: origin	103.127.231.0/24	ROAs covering it name AS131634, not AS131623. If AS131623 should announce it, add a ROA for AS131623.	14 of 673
Route object: none	103.127.231.0/24	Route objects for it name AS131634. Add a route object with origin AS131623 in the RIR database for the space.	14 of 673
Route object: RIR	103.117.4.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	103.117.5.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	103.117.6.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	103.117.7.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: origin

103.127.231.0/24

ROAs covering it name AS131634, not AS131623. If AS131623 should announce it, add a ROA for AS131623.

14 of 673

Route object: none

103.127.231.0/24

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

14 of 673

Route object: RIR

103.117.4.0/24

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

672 of 673

Route object: RIR

103.117.5.0/24

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

672 of 673

Route object: RIR

103.117.6.0/24

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

672 of 673

Route object: RIR

103.117.7.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 AS131623 whose prefix no peer sees AS131623 announce. Many are kept on purpose (backup routes, space announced only in some places).


103.117.4.0/22	NTTCOM, RADB	Valid

103.117.4.0/22

NTTCOM, 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.