Network · data from 2026-11-12
AS135381 SIS-AS-AP - SiS Distribution (Thailand) Public Company Limited descr: (@Genesis Data Center)
Registry name: SIS-AS-AP - SiS Distribution (Thailand) Public Company Limited descr: (@Genesis Data Center), TH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135381, 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.
| 203.150.178.0/24 | Invalid: origin | Other origin only | 181 27% |
| 202.44.246.0/24 | Invalid: origin | Other origin only | 178 26% |
| 202.44.217.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.44.218.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.44.229.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.44.230.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.44.231.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.44.232.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.44.233.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.44.244.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.44.252.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.44.254.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.44.255.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.130.151.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 83.118.16.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 83.118.17.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 83.118.28.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 83.118.30.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 147.50.69.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 161.82.175.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 161.82.218.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.150.118.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.150.121.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.150.122.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.150.131.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.150.175.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.156.30.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 203.156.105.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 2400:6280:11b::/48 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2400:6280:145::/48 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2400:6280:146::/48 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2403:f040:13::/48 | Valid | RIR databaseAPNIC, RADB | 635 100% |
AS-SET
AS135381 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 4 are in fix.csv.
- ROA: origin2
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 203.150.178.0/24 | ROAs covering it name AS4618, not AS135381. If AS135381 should announce it, add a ROA for AS135381. |
| Route object: none | 203.150.178.0/24 | Route objects for it name AS4618. Add a route object with origin AS135381 in the RIR database for the space. |
| ROA: origin | 202.44.246.0/24 | ROAs covering it name AS4618, not AS135381. If AS135381 should announce it, add a ROA for AS135381. |
| Route object: none | 202.44.246.0/24 | Route objects for it name AS4618. Add a route object with origin AS135381 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS135381 is announced.
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.