Network · data from 2026-11-12

AS146813 SUIJI - Shanghai Suiji Networks Tech. Co. Ltd.

Registry name: SUIJI - Shanghai Suiji Networks Tech. Co. Ltd., CN · not in PeeringDB

3IPv4 routes 33.3% RPKI valid · 33.3% with a route object

0IPv6 routes

2RPKI invalid 2 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

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

Announced routes

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


74.2.101.0/24	Invalid: origin	Other origin only	1 0%low visibility	1
185.196.25.0/24	Invalid: origin	Other origin only	1 0%low visibility	1
23.236.111.0/24	Valid	RIR databaseARIN, RADB	673 100%	66

74.2.101.0/24

Invalid: origin

Other origin only

1 0%low visibility

185.196.25.0/24

Invalid: origin

Other origin only

1 0%low visibility

23.236.111.0/24

Valid

RIR databaseARIN, RADB

673 100%

AS-SET

AS146813 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 6 are in fix.csv.

ROA: origin2
Route object: none2
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: origin	74.2.101.0/24	ROAs covering it name AS834, not AS146813. If AS146813 should announce it, add a ROA for AS146813.	1 of 673
Route object: none	74.2.101.0/24	Route objects for it name AS834. Add a route object with origin AS146813 in the RIR database for the space.	1 of 673
ROA: origin	185.196.25.0/24	ROAs covering it name AS152606, not AS146813. If AS146813 should announce it, add a ROA for AS146813.	1 of 673
Route object: none	185.196.25.0/24	Route objects for it name AS152606. Add a route object with origin AS146813 in the RIR database for the space.	1 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

74.2.101.0/24

ROAs covering it name AS834, not AS146813. If AS146813 should announce it, add a ROA for AS146813.

1 of 673

Route object: none

74.2.101.0/24

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

1 of 673

ROA: origin

185.196.25.0/24

ROAs covering it name AS152606, not AS146813. If AS146813 should announce it, add a ROA for AS146813.

1 of 673

Route object: none

185.196.25.0/24

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

1 of 673

Route objects not announced

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


89.213.1.0/24	RADB, RIPE	Valid
89.213.130.0/24	RADB, RIPE	Valid

89.213.1.0/24

RADB, RIPE

Valid

89.213.130.0/24

RADB, RIPE

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.