bgpreport

Network · data from 2026-11-12

AS150770 SHINENET - SHINE TECH INFORMATION COMPANY LIMITED

Registry name: SHINENET - SHINE TECH INFORMATION COMPANY LIMITED, TW · not in PeeringDB

6IPv4 routes 66.7% RPKI valid · 66.7% with a route object
0IPv6 routes
2RPKI invalid 2 origin · 0 maxLength
0No ROA 2 with no route object for this origin
6Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS150770, seen from no peer

Announced routes

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

87.229.92.0/24 Invalid: origin Other origin only 3 0%low visibility 3
31.56.37.0/24 Invalid: origin None 0 0%low visibility 1
103.197.158.0/24 Valid Other IRR onlyRADB 3 0%low visibility 3
103.197.159.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
185.238.212.0/23 Valid RIR databaseRADB, RIPE 3 0%low visibility 3
212.23.206.0/24 Valid RIR databaseRADB, RIPE 3 0%low visibility 3

AS-SET

AS150770 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 11 are in fix.csv.

  • ROA: origin2
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin87.229.92.0/24ROAs covering it name AS834, not AS150770. If AS150770 should announce it, add a ROA for AS150770.3 of 673
Route object: none87.229.92.0/24Route objects for it name AS834. Add a route object with origin AS150770 in the RIR database for the space.3 of 673
ROA: origin31.56.37.0/24ROAs covering it name AS2914, not AS150770. If AS150770 should announce it, add a ROA for AS150770.0 of 673
Route object: none31.56.37.0/24No route object for it. Add a route object with origin AS150770 in the RIR database for the space.0 of 673
Route object: RIR103.197.158.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR103.197.159.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

96.62.221.0/24RADB, RIPEValid
103.197.158.0/23RADBValid
2001:470:25e::/48ARINInvalid: origin
2001:470:3fd::/48ARINInvalid: origin
2400:fe60::/32RADBValid

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.