bgpreport

Network · data from 2026-11-12

AS56913 COCHENTEK-AS CoChen Technology LTD.

Registry name: COCHENTEK-AS CoChen Technology LTD., TW · not in PeeringDB

13IPv4 routes 92.3% RPKI valid · 92.3% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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 AS56913, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS56913, 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.
143.20.121.0/24 Invalid: origin None 5 1%low visibility 5
102.135.19.0/24 Valid Other IRR onlyRADB 669 99% 67
102.135.99.0/24 Valid Other IRR onlyRADB 669 99% 67
85.237.71.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
31.58.130.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
82.26.129.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
82.47.18.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
84.75.217.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
95.135.176.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
151.240.15.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
151.244.112.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
151.244.116.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
45.132.219.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
2a13:9500:4d::/48 Valid RIR databaseRIPE 631 99% 69

AS-SET

AS56913 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 5 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin143.20.121.0/24ROAs covering it name AS834, not AS56913. If AS56913 should announce it, add a ROA for AS56913.5 of 673
Route object: none143.20.121.0/24No route object for it. Add a route object with origin AS56913 in the RIR database for the space.5 of 673
Route object: RIR102.135.19.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR102.135.99.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

102.215.229.0/24RADBValid

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.