Network · data from 2026-11-12
AS45254 ISSP-AS-AP - Internet Solution & Service Provider Co., Ltd.
Registry name: ISSP-AS-AP - Internet Solution & Service Provider Co., Ltd., TH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45254, 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.
| 110.49.97.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 110.49.111.0/24 | Valid | Other IRR onlyRADB | 673 100% |
AS-SET
AS45254 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.
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 110.49.97.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 110.49.111.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS45254 whose prefix no peer sees AS45254 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 119.46.76.0/24 | APNIC | Valid |
| 203.153.187.0/24 | 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.