Network · data from 2026-11-12
AS49608 COCHENTEK-AS-UK CoChen Technology LTD.
Registry name: COCHENTEK-AS-UK CoChen Technology LTD., TW · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49608, 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.
| 151.245.30.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 151.247.214.0/24 | Invalid: origin | None | 2 0%low visibility |
| 31.77.245.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 87.76.216.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 88.209.247.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 96.126.144.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 31.59.72.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 109.64.8.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 201.4.22.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 109.64.25.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
AS-SET
AS49608 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 9 are in fix.csv.
- ROA: origin2
- Route object: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 151.245.30.0/24 | ROAs covering it name AS834, AS205886, not AS49608. If AS49608 should announce it, add a ROA for AS49608. |
| Route object: none | 151.245.30.0/24 | Route objects for it name AS834. Add a route object with origin AS49608 in the RIR database for the space. |
| ROA: origin | 151.247.214.0/24 | ROAs covering it name AS834, not AS49608. If AS49608 should announce it, add a ROA for AS49608. |
| Route object: none | 151.247.214.0/24 | No route object for it. Add a route object with origin AS49608 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS49608 whose prefix no peer sees AS49608 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.58.130.0/24 | RADB, RIPE | Valid |
| 82.26.129.0/24 | RADB, RIPE | Valid |
| 82.47.18.0/24 | RADB, RIPE | Valid |
| 84.75.217.0/24 | RADB, RIPE | Valid |
| 185.18.222.0/24 | RADB | No ROA |
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.