bgpreport

Network · data from 2026-11-12

AS215748 Westeros Westeros Communications (THAILAND) CO., LTD.

Registry name: Westeros Westeros Communications (THAILAND) CO., LTD., TH · not in PeeringDB

45IPv4 routes 93.3% RPKI valid · 97.8% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
3No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS215748, seen from no peer

Announced routes

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

200.0.127.0/24 No ROA Other IRR onlyALTDB, RADB 672 100% 67
200.10.213.0/24 No ROA Other IRR onlyALTDB, RADB 672 100% 67
200.34.58.0/24 No ROA Other IRR onlyALTDB, RADB 672 100% 67
203.84.136.0/24 Valid Other origin only 670 100% 67
23.139.92.0/24 Valid RIR databaseARIN 673 100% 68
23.139.100.0/24 Valid RIR databaseARIN 671 100% 67
23.157.108.0/24 Valid RIR databaseARIN, RADB 671 100% 66
23.157.204.0/24 Valid RIR databaseARIN, RADB 671 100% 66
23.157.252.0/24 Valid RIR databaseARIN, RADB 671 100% 66
46.236.199.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
96.62.35.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
96.62.36.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
96.62.64.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
96.62.65.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
96.62.66.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
96.62.110.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
96.62.123.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
96.62.142.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
96.62.213.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
96.62.226.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
103.78.243.0/24 Valid RIR databaseAPNIC 671 100% 66
103.129.196.0/24 Valid RIR databaseAPNIC 671 100% 66
103.129.198.0/24 Valid RIR databaseAPNIC 671 100% 66
103.227.164.0/23 Valid RIR databaseAPNIC 671 100% 66
103.227.166.0/23 Valid RIR databaseAPNIC 671 100% 66
145.79.92.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
145.79.106.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
145.79.107.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
145.79.118.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
145.79.123.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
145.79.125.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
145.79.167.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
209.209.84.0/24 Valid RIR databaseARIN 671 100% 66
209.209.85.0/24 Valid RIR databaseARIN 671 100% 66
209.209.86.0/24 Valid RIR databaseARIN 671 100% 66
209.209.87.0/24 Valid RIR databaseARIN 671 100% 66
14.192.50.0/24 Valid RIR databaseAPNIC 670 100% 66
103.56.129.0/24 Valid RIR databaseAPNIC 670 100% 67
103.64.12.0/24 Valid RIR databaseAPNIC 670 100% 66
103.92.145.0/24 Valid RIR databaseAPNIC 670 100% 67
103.120.14.0/24 Valid RIR databaseAPNIC 670 100% 67
103.231.36.0/24 Valid RIR databaseAPNIC 670 100% 67
103.231.37.0/24 Valid RIR databaseAPNIC 670 100% 67
23.139.84.0/24 Valid RIR databaseARIN, RADB 643 96% 66
23.138.44.0/24 Valid RIR databaseARIN, RADB 1 0%low visibility 1

AS-SET

AS215748 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 9 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: RIR3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none200.0.127.0/24No ROA covers it. Add a ROA for AS215748, maxLength 24.672 of 673
Route object: RIR200.0.127.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
ROA: none200.10.213.0/24No ROA covers it. Add a ROA for AS215748, maxLength 24.672 of 673
Route object: RIR200.10.213.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
ROA: none200.34.58.0/24No ROA covers it. Add a ROA for AS215748, maxLength 24.672 of 673
Route object: RIR200.34.58.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: none203.84.136.0/24Route objects for it name AS24206. Add a route object with origin AS215748 in the RIR database for the space.670 of 673

Route objects not announced

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

45.92.208.0/22RIPEValid
103.116.45.0/24APNICValid

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.