Network · data from 2026-11-12
AS24168 Cloudmax
Registry name: CLOUDMAX-AS-TW - Cloudmax Inc., TW · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24168, 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.
| 121.50.149.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 121.50.150.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 103.136.60.0/24 | Valid | Other IRR onlyRADB | 477 71% |
| 103.30.45.0/24 | Valid | Other IRR onlyRADB | 226 34% |
| 103.30.46.0/24 | Valid | Other IRR onlyRADB | 226 34% |
AS-SET
PeeringDB's irr_as_set for AS24168: AS-CLOUDMAX. 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 (AS24168 isn't in the set, or no route object for AS24168 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 | AS24168 in it | Not covered |
|---|---|---|---|---|---|
| AS-CLOUDMAX | RADB | 2 | 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 30 are in fix.csv.
- Route object: RIR5
- Route object: not announced25
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 121.50.149.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 121.50.150.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.136.60.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.30.45.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.30.46.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24168 whose prefix no peer sees AS24168 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.30.44.0/23 | RADB | Valid |
| 103.30.44.0/24 | RADB | Valid |
| 103.30.46.0/23 | RADB | Valid |
| 103.30.47.0/24 | RADB | Valid |
| 103.136.60.0/23 | RADB | Valid |
| 103.136.61.0/24 | RADB | Valid |
| 121.50.144.0/21 | NTTCOM, RADB | Valid |
| 121.50.144.0/22 | RADB | Valid |
| 121.50.144.0/23 | RADB | Valid |
| 121.50.144.0/24 | RADB | Valid |
| 121.50.145.0/24 | RADB | Valid |
| 121.50.146.0/23 | RADB | Valid |
| 121.50.146.0/24 | RADB | Valid |
| 121.50.147.0/24 | RADB | Valid |
| 121.50.148.0/22 | RADB | Valid |
| 121.50.148.0/23 | RADB | Valid |
| 121.50.148.0/24 | RADB | Valid |
| 121.50.150.0/23 | RADB | Valid |
| 121.50.151.0/24 | RADB | Valid |
| 211.79.100.0/23 | RADB | Valid |
| 211.79.100.0/24 | RADB | Valid |
| 211.79.101.0/24 | RADB | Valid |
| 2404:8cc::/32 | RADB | No ROA |
| 2405:8700::/32 | RADB | No ROA |
| 2405:8700:3000::/48 | RADB | 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.