Network · data from 2026-11-12
AS149404 Cepat Multi Data
Registry name: IDNIC-CEPATMULTIDATA-AS-ID - PT Cepat Multi Data, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS149404, 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.183.8.0/24 | No ROA | Nonecovered by 103.183.8.0/23 | 671 100% |
| 103.183.9.0/24 | No ROA | Nonecovered by 103.183.8.0/23 | 671 100% |
| 2001:df7:cd00::/48 | No ROA | None | 521 82% |
| 103.183.8.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS149404: AS-CMD. 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 (AS149404 isn't in the set, or no route object for AS149404 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 | AS149404 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-CMD | 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 9 are in fix.csv.
- ROA: none4
- Route object: none3
- Route object: RIR1
- AS-SET: not found1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.183.8.0/24 | No ROA covers it. Add a ROA for AS149404, maxLength 24. |
| Route object: none | 103.183.8.0/24 | No route object for it. A route object for 103.183.8.0/23 with origin AS149404 covers it (filters allowing more-specifics accept it). Add a route object with origin AS149404 in the RIR database for the space. |
| ROA: none | 103.183.9.0/24 | No ROA covers it. Add a ROA for AS149404, maxLength 24. |
| Route object: none | 103.183.9.0/24 | No route object for it. A route object for 103.183.8.0/23 with origin AS149404 covers it (filters allowing more-specifics accept it). Add a route object with origin AS149404 in the RIR database for the space. |
| ROA: none | 2001:df7:cd00::/48 | No ROA covers it. Add a ROA for AS149404, maxLength 48. |
| Route object: none | 2001:df7:cd00::/48 | No route object for it. Add a route object with origin AS149404 in the RIR database for the space. |
| ROA: none | 103.183.8.0/23 | No ROA covers it. Add a ROA for AS149404, maxLength 23. |
| Route object: RIR | 103.183.8.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS-CMD | PeeringDB names AS-CMD; no IRR database read has it. |
Route objects not announced
Every route object with origin AS149404 is announced.
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.