Network · data from 2026-11-12
AS131460 ASIASOFTNET-TH - 9 UM Tower
Registry name: ASIASOFTNET-TH - 9 UM Tower, TH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS131460, 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.
| 2001:df0:237::/48 | No ROA | Other IRR onlyRADB | 5 1%low visibility |
| 2001:df0:237::/60 | No ROA | Other IRR onlyRADB | 1 0%low visibility |
| 103.4.156.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.4.157.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.4.159.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 123.242.200.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 123.242.206.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.4.158.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 123.242.201.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 123.242.202.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 123.242.203.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 123.242.204.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 123.242.205.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
AS-SET
AS131460 isn't in PeeringDB, where networks name their AS-SET.
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 21 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2001:df0:237::/48 | No ROA covers it. Add a ROA for AS131460, maxLength 48. |
| Route object: RIR | 2001:df0:237::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2001:df0:237::/60 | No ROA covers it. Add a ROA for AS131460, maxLength 60. |
| Route object: RIR | 2001:df0:237::/60 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS131460 whose prefix no peer sees AS131460 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.90.227.0/24 | APNIC, RADB | Valid |
| 103.4.156.0/22 | RADB | No ROA |
| 119.46.128.0/24 | APNIC, RADB | Valid |
| 119.46.129.0/24 | APNIC, RADB | Valid |
| 119.46.199.0/24 | APNIC, RADB | Valid |
| 119.46.249.0/24 | APNIC, RADB | Valid |
| 123.242.200.0/21 | NTTCOM, RADB | No ROA |
| 123.242.200.0/22 | RADB | No ROA |
| 123.242.200.0/23 | RADB | No ROA |
| 123.242.202.0/23 | RADB | No ROA |
| 123.242.204.0/22 | RADB | No ROA |
| 123.242.204.0/23 | RADB | No ROA |
| 123.242.206.0/23 | RADB | No ROA |
| 203.144.132.0/24 | APNIC | Valid |
| 203.144.213.0/24 | APNIC, RADB | Valid |
| 2001:df0:237:10::/60 | RADB | No ROA |
| 2001:df0:2fb::/48 | RADB | 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.