Network · data from 2026-11-12
AS135302 DC West CloudSigma
Registry name: CLOUDSIGMA-AS-AP - CLOUDSIGMA-AU, AU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135302, 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.
| 103.9.160.0/24 | No ROA | Other origin onlycovered by 103.9.160.0/22 | 670 100% |
| 103.9.161.0/24 | No ROA | Other origin onlycovered by 103.9.160.0/22 | 669 99% |
| 103.9.162.0/24 | No ROA | Other origin onlycovered by 103.9.160.0/22 | 669 99% |
| 103.9.163.0/24 | No ROA | Other origin onlycovered by 103.9.160.0/22 | 669 99% |
| 103.9.160.0/22 | No ROA | RIR databaseAPNIC | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS135302: AS-CLOUDSIGMA. 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 (AS135302 isn't in the set, or no route object for AS135302 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 | AS135302 in it | Not covered |
|---|---|---|---|---|---|
| AS-CLOUDSIGMA | RIPE | 2 | 1 | No | 5 |
| APNIC (also) | 1 | 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 15 are in fix.csv.
- ROA: none5
- Route object: none4
- AS-SET: own ASN1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.9.160.0/24 | No ROA covers it. Add a ROA for AS135302, maxLength 24. |
| Route object: none | 103.9.160.0/24 | Route objects for it name AS38716, AS58511. A route object for 103.9.160.0/22 with origin AS135302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135302 in the RIR database for the space. |
| ROA: none | 103.9.161.0/24 | No ROA covers it. Add a ROA for AS135302, maxLength 24. |
| Route object: none | 103.9.161.0/24 | Route objects for it name AS38716, AS58511. A route object for 103.9.160.0/22 with origin AS135302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135302 in the RIR database for the space. |
| ROA: none | 103.9.162.0/24 | No ROA covers it. Add a ROA for AS135302, maxLength 24. |
| Route object: none | 103.9.162.0/24 | Route objects for it name AS38716, AS58511. A route object for 103.9.160.0/22 with origin AS135302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135302 in the RIR database for the space. |
| ROA: none | 103.9.163.0/24 | No ROA covers it. Add a ROA for AS135302, maxLength 24. |
| Route object: none | 103.9.163.0/24 | Route objects for it name AS38716, AS58511. A route object for 103.9.160.0/22 with origin AS135302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135302 in the RIR database for the space. |
| ROA: none | 103.9.160.0/22 | No ROA covers it. Add a ROA for AS135302, maxLength 22. |
| AS-SET: own ASN | AS-CLOUDSIGMA | AS135302 isn't in AS-CLOUDSIGMA (RIPE) once expanded. Add AS135302 to it. |
Route objects not announced
Route objects with origin AS135302 whose prefix no peer sees AS135302 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.169.14.0/23 | APNIC | No ROA |
| 103.169.14.0/24 | APNIC | No ROA |
| 103.169.15.0/24 | APNIC | No ROA |
| 2001:df6:e680::/48 | APNIC | No ROA |
| 2402:1300::/32 | 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.