Network · data from 2026-11-12
AS150363 THIN NET
Registry name: THIN-NET - SoftEther Corporation, JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS150363, 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.
| 160.186.0.0/16 | No ROA | Other IRR onlyJPIRR | 673 100% |
| 103.115.84.0/23 | No ROA | Other IRR onlyJPIRR | 671 100% |
| 219.100.38.0/24 | No ROA | Other IRR onlyJPIRR | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS150363: AS-SHININFRA. 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 (AS150363 isn't in the set, or no route object for AS150363 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 | AS150363 in it | Not covered |
|---|---|---|---|---|---|
| AS-SHININFRA | JPIRRlists itself further down2 member sets in no database: AS150362:AS-KURIYAMA-NET, AS200455:AS-AL | 57 | 22 | 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 16 are in fix.csv.
- ROA: none3
- Route object: RIR3
- AS-SET: missing member2
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 160.186.0.0/16 | No ROA covers it. Add a ROA for AS150363, maxLength 16. |
| Route object: RIR | 160.186.0.0/16 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 103.115.84.0/23 | No ROA covers it. Add a ROA for AS150363, maxLength 23. |
| Route object: RIR | 103.115.84.0/23 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 219.100.38.0/24 | No ROA covers it. Add a ROA for AS150363, maxLength 24. |
| Route object: RIR | 219.100.38.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
| AS-SET: missing member | AS-SHININFRA | AS-SHININFRA (JPIRR) lists AS150362:AS-KURIYAMA-NET; no IRR database read has it. |
| AS-SET: missing member | AS-SHININFRA | AS-SHININFRA (JPIRR) lists AS200455:AS-AL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS150363 whose prefix no peer sees AS150363 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.115.84.0/24 | JPIRR | No ROA |
| 103.115.85.0/24 | JPIRR | No ROA |
| 160.186.0.0/17 | JPIRR | No ROA |
| 160.186.128.0/17 | JPIRR | No ROA |
| 160.186.247.0/24 | JPIRR | No ROA |
| 160.186.248.0/24 | JPIRR | No ROA |
| 210.251.168.0/21 | JPIRR | Invalid: origin |
| 2401:af80:c100::/40 | JPIRR | 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.