Network · data from 2026-11-12
AS3836 Thai Social/Scientific, Academic and Research Network
Registry name: THAISARN-TH-AS-AP - Thai Social/Scientific, Academic and Research Network, TH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS3836, 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.
| 192.150.250.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 203.185.96.0/19 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 2001:f00::/32 | Valid | RIR databaseAPNIC, RADB | 636 100% |
AS-SET
AS3836's PeeringDB record names no 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 67 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced65
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.150.250.0/23 | No ROA covers it. Add a ROA for AS3836, maxLength 23. |
| Route object: RIR | 192.150.250.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS3836 whose prefix no peer sees AS3836 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.150.250.0/24 | NTTCOM, RADB | No ROA |
| 192.150.251.0/24 | NTTCOM, RADB | No ROA |
| 203.185.64.0/18 | NTTCOM, RADB | No ROA |
| 203.185.96.0/20 | APNIC, NTTCOM, RADB | Valid |
| 203.185.96.0/21 | APNIC, NTTCOM, RADB | Valid |
| 203.185.96.0/22 | APNIC, NTTCOM, RADB | Valid |
| 203.185.96.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.185.96.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.97.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.98.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.185.98.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.99.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.100.0/22 | APNIC, NTTCOM, RADB | Valid |
| 203.185.100.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.185.100.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.101.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.102.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.185.102.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.103.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.104.0/21 | APNIC, NTTCOM, RADB | Valid |
| 203.185.104.0/22 | APNIC, NTTCOM, RADB | Valid |
| 203.185.104.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.185.104.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.105.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.106.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.185.106.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.107.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.108.0/22 | APNIC, NTTCOM, RADB | Valid |
| 203.185.108.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.185.108.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.109.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.110.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.185.110.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.111.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.112.0/20 | APNIC, NTTCOM, RADB | Valid |
| 203.185.112.0/21 | APNIC, NTTCOM, RADB | Valid |
| 203.185.112.0/22 | APNIC, NTTCOM, RADB | Valid |
| 203.185.112.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.185.112.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.113.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.114.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.185.114.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.115.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.116.0/22 | APNIC, NTTCOM, RADB | Valid |
| 203.185.116.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.185.116.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.117.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.118.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.185.118.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.119.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.120.0/21 | APNIC, NTTCOM, RADB | Valid |
| 203.185.120.0/22 | APNIC, NTTCOM, RADB | Valid |
| 203.185.120.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.185.120.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.121.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.122.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.185.122.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.123.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.124.0/22 | APNIC, NTTCOM, RADB | Valid |
| 203.185.124.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.185.124.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.125.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.126.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.185.126.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.185.127.0/24 | APNIC, NTTCOM, RADB | 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.