Network · data from 2026-11-12
AS139358 Kansuiun Co., Ltd
Registry name: KANSUIUN-AS-AP - Kansuiun Co., Ltd, JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS139358, 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.
| 202.179.152.0/24 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 61.200.87.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 115.42.62.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 161.129.41.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 103.82.169.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 103.211.71.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 167.253.99.0/24 | Valid | RIR databaseARIN, RADB | 667 99% |
| 2401:e60:20::/44 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:e60:100::/40 | Valid | RIR databaseAPNIC | 635 100% |
| 2001:df4:e141::/48 | Valid | RIR databaseAPNIC | 335 53% |
AS-SET
PeeringDB's irr_as_set for AS139358: APNIC::AS-KANSUIUN. 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 (AS139358 isn't in the set, or no route object for AS139358 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 | AS139358 in it | Not covered |
|---|---|---|---|---|---|
| APNIC::AS-KANSUIUN | APNIC | 10 | 1 | 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 14 are in fix.csv.
- ROA: none1
- Route object: RIR2
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 202.179.152.0/24 | No ROA covers it. Add a ROA for AS139358, maxLength 24. |
| Route object: RIR | 202.179.152.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.200.87.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS139358 whose prefix no peer sees AS139358 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.102.4.0/24 | APNIC | Valid |
| 103.141.182.0/23 | APNIC | Valid |
| 103.141.182.0/24 | APNIC | Valid |
| 103.141.183.0/24 | APNIC | Valid |
| 157.20.135.0/24 | APNIC, RADB | Valid |
| 192.208.2.0/24 | ARIN, RADB | Valid |
| 2401:e60:20::/48 | APNIC | Valid |
| 2401:e60:30::/44 | APNIC | Valid |
| 2405:2040::/33 | APNIC | No ROA |
| 2405:2040:8000::/33 | APNIC | No ROA |
| 2602:f96c:c0::/48 | ARIN | 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.