Network · data from 2026-11-12

AS150767 Shi Ji Industrial Co., Ltd.

Registry name: SHIJICOLTD-AS-TW - Shi Ji Industrial Co., Ltd., TW · PeeringDB

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

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

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

Announced routes

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


36.50.248.0/23	Valid	Other IRR onlyRADB	503 75%	66
2401:5f20::/32	Valid	Other IRR onlyRADB	2 0%low visibility	6
2401:5f20::/36	Valid	RIR databaseAPNIC	634 100%	69
36.50.248.0/24	Valid	RIR databaseAPNIC, RADB	7 1%low visibility	6

36.50.248.0/23

Valid

Other IRR onlyRADB

503 75%

2401:5f20::/32

Valid

Other IRR onlyRADB

2 0%low visibility

2401:5f20::/36

Valid

RIR databaseAPNIC

634 100%

36.50.248.0/24

Valid

RIR databaseAPNIC, RADB

7 1%low visibility

AS-SET

PeeringDB's irr_as_set for AS150767: RADB::AS-SHIJICOLTD. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS150767 isn't in the set, or no route object for AS150767 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS150767 in it	Not covered
RADB::AS-SHIJICOLTD	RADB1 member set in no database: AS205329:AS-SHIJICOLTD	1	2	5	Yes	0

Name

Database

ASNs

Sets

Route objects

AS150767 in it

Not covered

RADB::AS-SHIJICOLTD

RADB1 member set in no database: AS205329:AS-SHIJICOLTD

Yes

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.

Route object: RIR2
AS-SET: missing member1
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	36.50.248.0/23	Route object only in RADB. Add it in the RIR database for the space.	503 of 673
Route object: RIR	2401:5f20::/32	Route object only in RADB. Add it in the RIR database for the space.	2 of 636
AS-SET: missing member	RADB::AS-SHIJICOLTD	AS-SHIJICOLTD (RADB) lists AS205329:AS-SHIJICOLTD; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

36.50.248.0/23

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

503 of 673

Route object: RIR

2401:5f20::/32

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

2 of 636

AS-SET: missing member

RADB::AS-SHIJICOLTD

AS-SHIJICOLTD (RADB) lists AS205329:AS-SHIJICOLTD; no IRR database read has it.

Route objects not announced

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


36.50.249.0/24	RADB	Valid

36.50.249.0/24

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.