Network · data from 2026-11-12
AS45724 PT Multi Media Access
Registry name: MULTIMEDIA-AS-ID - Multi Media Access, PT, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45724, 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.231.112.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.231.113.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.231.114.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.231.115.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.8.28.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.8.29.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS45724: AS45724:AS-MULTIMEDIA-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 (AS45724 isn't in the set, or no route object for AS45724 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 | AS45724 in it | Not covered |
|---|---|---|---|---|---|
| AS45724:AS-MULTIMEDIA-ID | APNIC | 12 | 1 | No | 6 |
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 12 are in fix.csv.
- Route object: RIR6
- AS-SET: own ASN1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.231.112.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.231.113.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.231.114.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.231.115.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.8.28.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.8.29.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS45724:AS-MULTIMEDIA-ID | AS45724 isn't in AS45724:AS-MULTIMEDIA-ID (APNIC) once expanded. Add AS45724 to it. |
Route objects not announced
Route objects with origin AS45724 whose prefix no peer sees AS45724 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.231.112.0/22 | NTTCOM, RADB | Valid |
| 103.231.112.0/23 | RADB | Valid |
| 103.231.114.0/23 | RADB | Valid |
| 202.8.28.0/23 | NTTCOM, RADB | No ROA |
| 2407:e5c0::/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.