Network · data from 2026-11-12
AS132625 SDECB-AS-AP - SDEC
Registry name: SDECB-AS-AP - SDEC, MY · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS132625, 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.186.160.0/23 | No ROA | RIR databaseAPNIC | 671 100% |
| 103.186.160.0/24 | No ROA | RIR databaseAPNIC | 671 100% |
| 85.137.16.0/23 | No ROA | RIR databaseAPNIC | 670 100% |
| 2001:df0:abc0::/48 | No ROA | RIR databaseAPNIC | 636 100% |
AS-SET
AS132625 isn't in PeeringDB, where networks name their AS-SET.
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 5 are in fix.csv.
- ROA: none4
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.186.160.0/23 | No ROA covers it. Add a ROA for AS132625, maxLength 23. |
| ROA: none | 103.186.160.0/24 | No ROA covers it. Add a ROA for AS132625, maxLength 24. |
| ROA: none | 85.137.16.0/23 | No ROA covers it. Add a ROA for AS132625, maxLength 23. |
| ROA: none | 2001:df0:abc0::/48 | No ROA covers it. Add a ROA for AS132625, maxLength 48. |
Route objects not announced
Route objects with origin AS132625 whose prefix no peer sees AS132625 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.186.161.0/24 | APNIC | 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.