Network · data from 2026-11-12
AS152617 Hyper Network Technology
Registry name: PPTECH - PPTECH co., ltd., TW · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS152617, 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.
| 203.18.157.0/24 | No ROA | None | 661 98% |
| 203.18.156.0/23 | No ROA | None | 1 0%low visibility |
| 2402:6d20::/32 | Valid | RIR databaseAPNIC | 632 99% |
| 43.242.6.0/24 | Valid | RIR databaseAPNIC | 121 18% |
AS-SET
PeeringDB's irr_as_set for AS152617: APNIC::AS152617. 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 (AS152617 isn't in the set, or no route object for AS152617 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 | AS152617 in it | Not covered | |
|---|---|---|---|---|---|---|
| APNIC::AS152617 | A single AS number, not a set: AS152617 (this network), 8 route objects. | |||||
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 10 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.18.157.0/24 | No ROA covers it. Add a ROA for AS152617, maxLength 24. |
| Route object: none | 203.18.157.0/24 | No route object for it. Add a route object with origin AS152617 in the RIR database for the space. |
| ROA: none | 203.18.156.0/23 | No ROA covers it. Add a ROA for AS152617, maxLength 23. |
| Route object: none | 203.18.156.0/23 | No route object for it. Add a route object with origin AS152617 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS152617 whose prefix no peer sees AS152617 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.242.6.0/23 | APNIC | Valid |
| 43.242.7.0/24 | APNIC | Valid |
| 160.187.194.0/23 | RADB | No ROA |
| 211.167.32.0/22 | RADB | No ROA |
| 211.167.36.0/22 | RADB | No ROA |
| 2401:ca60::/32 | 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.