bgpreport

Network · data from 2026-11-12

AS56223 CSLOXINFO-INET-THAISUMMIT-AS - Thai Summit Autopart Industry Co.,Ltd

Registry name: CSLOXINFO-INET-THAISUMMIT-AS - Thai Summit Autopart Industry Co.,Ltd, TH · not in PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS56223, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS56223, 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.
58.137.33.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 66
58.137.62.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
203.150.250.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
203.151.111.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68

AS-SET

AS56223 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 1 are in fix.csv.

  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
Route object: RIR58.137.33.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS56223 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.