Network · data from 2026-11-12
AS134809 ViewQwest Digital Sdn. Bhd.
Registry name: VIEWQWEST-AS-AP - ViewQwest Sdn. Bhd., MY · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS134809, 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.
| 163.47.90.0/24 | Invalid: maxLength | Nonecovered by 163.47.88.0/22 | 1 0%low visibility |
| 163.47.91.0/24 | Invalid: maxLength | Nonecovered by 163.47.88.0/22 | 1 0%low visibility |
| 43.228.200.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 43.252.216.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 96.9.160.0/21 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 96.9.168.0/21 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.12.140.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 103.13.74.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.22.160.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 103.26.248.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 103.194.80.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 103.231.251.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.232.28.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.253.105.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 120.138.80.0/20 | Valid | RIR databaseAPNIC | 673 100% |
| 163.47.88.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 163.53.224.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 221.133.32.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 221.133.40.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 223.27.128.0/20 | Valid | RIR databaseAPNIC | 672 100% |
| 103.92.151.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.92.150.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 2001:df7:6400::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2400:6e80::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:9a00::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:7481::/32 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2405:d3c0::/32 | Valid | RIR databaseAPNIC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS134809: AS134809:AS-TRANSIT. 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 (AS134809 isn't in the set, or no route object for AS134809 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 | AS134809 in it | Not covered |
|---|---|---|---|---|---|
| AS134809:AS-TRANSIT | APNIC | 14 | 1 | Yes | 0 |
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: maxLength2
- Route object: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 163.47.90.0/24 | ROA 163.47.88.0/22 AS134809 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 163.47.90.0/24. |
| Route object: none | 163.47.90.0/24 | No route object for it. A route object for 163.47.88.0/22 with origin AS134809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS134809 in the RIR database for the space. |
| ROA: maxLength | 163.47.91.0/24 | ROA 163.47.88.0/22 AS134809 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 163.47.91.0/24. |
| Route object: none | 163.47.91.0/24 | No route object for it. A route object for 163.47.88.0/22 with origin AS134809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS134809 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS134809 whose prefix no peer sees AS134809 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.230.96.0/22 | APNIC | Valid |
| 103.92.150.0/23 | APNIC | 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.