bgpreport

Network · data from 2026-11-12

AS23932 World Internetwork Corporation Co

Registry name: winth-as-ap - Internet Service Provider, TH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23932, 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.

202.44.52.0/24 Valid Other origin only 132 20% 49
202.52.4.0/24 Valid None 43 6%low visibility 31
202.52.5.0/24 Valid None 43 6%low visibility 31
202.52.7.0/24 Valid None 43 6%low visibility 31
203.145.112.0/24 Valid Nonecovered by 203.145.112.0/22 43 6%low visibility 31
203.145.114.0/24 Valid Nonecovered by 203.145.112.0/22 43 6%low visibility 31
203.145.115.0/24 Valid Nonecovered by 203.145.112.0/22 43 6%low visibility 31
203.145.116.0/24 Valid Nonecovered by 203.145.116.0/22 43 6%low visibility 31
203.145.117.0/24 Valid Nonecovered by 203.145.116.0/22 43 6%low visibility 31
203.145.118.0/24 Valid Nonecovered by 203.145.116.0/22 43 6%low visibility 31
203.145.119.0/24 Valid Nonecovered by 203.145.116.0/22 43 6%low visibility 31
202.44.53.0/24 Valid Other IRR onlyRADB 132 20% 49
202.44.54.0/24 Valid Other IRR onlyRADB 132 20% 49
202.44.55.0/24 Valid Other IRR onlyRADB 132 20% 49
202.52.6.0/24 Valid Other IRR onlyRADB 132 20% 49
180.128.0.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.1.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.2.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.3.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.4.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.5.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.6.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.7.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.8.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.9.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.10.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.11.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.12.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.13.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.14.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.15.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.16.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.17.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.19.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.20.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.21.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.22.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.23.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.24.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.25.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.27.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.28.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.29.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.30.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.31.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.32.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.33.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.34.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.35.0/24 Valid RIR databaseAPNIC 132 20% 49
180.128.240.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.241.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.242.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.243.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.244.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.245.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.246.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
180.128.247.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49

AS-SET

AS23932'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 21 are in fix.csv.

  • Route object: none11
  • Route object: RIR4
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none202.44.52.0/24Route objects for it name AS4750. Add a route object with origin AS23932 in the RIR database for the space.132 of 673
Route object: none202.52.4.0/24No route object for it. Add a route object with origin AS23932 in the RIR database for the space.43 of 673
Route object: none202.52.5.0/24No route object for it. Add a route object with origin AS23932 in the RIR database for the space.43 of 673
Route object: none202.52.7.0/24No route object for it. Add a route object with origin AS23932 in the RIR database for the space.43 of 673
Route object: none203.145.112.0/24No route object for it. A route object for 203.145.112.0/22 with origin AS23932 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23932 in the RIR database for the space.43 of 673
Route object: none203.145.114.0/24No route object for it. A route object for 203.145.112.0/22 with origin AS23932 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23932 in the RIR database for the space.43 of 673
Route object: none203.145.115.0/24No route object for it. A route object for 203.145.112.0/22 with origin AS23932 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23932 in the RIR database for the space.43 of 673
Route object: none203.145.116.0/24No route object for it. A route object for 203.145.116.0/22 with origin AS23932 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23932 in the RIR database for the space.43 of 673
Route object: none203.145.117.0/24No route object for it. A route object for 203.145.116.0/22 with origin AS23932 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23932 in the RIR database for the space.43 of 673
Route object: none203.145.118.0/24No route object for it. A route object for 203.145.116.0/22 with origin AS23932 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23932 in the RIR database for the space.43 of 673
Route object: none203.145.119.0/24No route object for it. A route object for 203.145.116.0/22 with origin AS23932 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23932 in the RIR database for the space.43 of 673
Route object: RIR202.44.53.0/24Route object only in RADB. Add it in the RIR database for the space.132 of 673
Route object: RIR202.44.54.0/24Route object only in RADB. Add it in the RIR database for the space.132 of 673
Route object: RIR202.44.55.0/24Route object only in RADB. Add it in the RIR database for the space.132 of 673
Route object: RIR202.52.6.0/24Route object only in RADB. Add it in the RIR database for the space.132 of 673

Route objects not announced

Route objects with origin AS23932 whose prefix no peer sees AS23932 announce. Many are kept on purpose (backup routes, space announced only in some places).

180.128.0.0/16APNICInvalid: origin
180.128.12.0/22APNICInvalid: origin
180.128.18.0/24APNIC, RADBValid
180.128.26.0/24APNIC, RADBValid
203.145.112.0/22APNICInvalid: origin
203.145.116.0/22APNICInvalid: origin

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.