Network · data from 2026-11-12
AS38074 SDCC OpenNetwork
Registry name: SDCC-AS-AP - SDCC Japan-West Area, JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38074, 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.
| 44.31.25.0/24 | No ROA | Other IRR onlyJPIRR | 671 100% |
| 103.152.178.0/24 | Valid | RIR databaseAPNIC, JPIRR | 670 100% |
| 103.160.48.0/24 | Valid | RIR databaseAPNIC, JPIRR | 670 100% |
| 2001:df4:1780::/48 | Valid | RIR databaseAPNIC, JPIRR | 636 100% |
| 2406:7ec0::/33 | Valid | RIR databaseAPNIC, JPIRR | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS38074: AS-SDCC. 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 (AS38074 isn't in the set, or no route object for AS38074 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 | AS38074 in it | Not covered |
|---|---|---|---|---|---|
| AS-SDCC | APNIClists itself further down2 member sets in no database: AS150362:AS-KURIYAMA-NET, AS200455:AS-AL | 55 | 21 | 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 10 are in fix.csv.
- ROA: none1
- Route object: RIR1
- AS-SET: missing member2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 44.31.25.0/24 | No ROA covers it. Add a ROA for AS38074, maxLength 24. |
| Route object: RIR | 44.31.25.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
| AS-SET: missing member | AS-SDCC | AS-SDCC (APNIC) lists AS150362:AS-KURIYAMA-NET; no IRR database read has it. |
| AS-SET: missing member | AS-SDCC | AS-SDCC (APNIC) lists AS200455:AS-AL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS38074 whose prefix no peer sees AS38074 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:df4:1781::/48 | JPIRR | Invalid: origin |
| 2402:2f60:c201::/48 | JPIRR | Valid |
| 2406:7ec0::/32 | APNIC, JPIRR | Valid |
| 2406:7ec0:400::/39 | APNIC, JPIRR | Valid |
| 2406:7ec0:600::/39 | APNIC, JPIRR | Valid |
| 2406:7ec0:800::/38 | APNIC, JPIRR | 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.