Network · data from 2026-11-12
AS46045 PT. SARANA PEMBANGUNAN SIAK
Registry name: SIAK-AS-ID - PT Sarana Pembangunan Siak, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46045, 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.
| 122.128.17.0/24 | Invalid: origin | RIR databaseAPNIC | 1 0%low visibility |
| 122.128.16.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 122.128.18.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 122.128.19.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 122.128.20.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 122.128.21.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 122.128.23.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS46045: AS46045:AS-ID. 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 (AS46045 isn't in the set, or no route object for AS46045 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 | AS46045 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS46045:AS-ID | In no IRR database read today. | |||||
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 7 are in fix.csv.
- ROA: origin1
- AS-SET: not found1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 122.128.17.0/24 | ROAs covering it name AS150460, not AS46045. If AS46045 should announce it, add a ROA for AS46045. |
| AS-SET: not found | AS46045:AS-ID | PeeringDB names AS46045:AS-ID; no IRR database read has it. |
Route objects not announced
Route objects with origin AS46045 whose prefix no peer sees AS46045 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 122.128.16.0/21 | NTTCOM, RADB | No ROA |
| 122.128.16.0/22 | APNIC, NTTCOM | No ROA |
| 122.128.16.0/23 | NTTCOM | No ROA |
| 122.128.20.0/22 | NTTCOM | No ROA |
| 122.128.22.0/24 | APNIC | Invalid: origin |
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.