bgpreport

Network · data from 2026-11-12

AS138156 CSNE Co

Registry name: CSNE-NETPLAY-AS - CSNE Co., Ltd., TH · PeeringDB

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

Announced routes

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

141.11.156.0/24 Invalid: origin Other origin onlycovered by 141.11.156.0/22 8 1%low visibility 8
141.11.156.0/22 No ROA Other IRR onlyRADB 670 100% 66
66.212.22.0/24 Valid RIR databaseARIN, RADB 670 100% 66
102.129.229.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 66
103.91.206.0/24 Valid RIR databaseAPNIC, RADB 670 100% 66
103.91.207.0/24 Valid RIR databaseAPNIC, RADB 670 100% 66
103.131.200.0/24 Valid RIR databaseAPNIC, RADB 670 100% 66
140.99.96.0/24 Valid RIR databaseARIN, RADB 670 100% 66
140.99.97.0/24 Valid RIR databaseARIN, RADB 670 100% 66
140.99.98.0/24 Valid RIR databaseARIN, RADB 670 100% 66
140.99.99.0/24 Valid RIR databaseARIN, RADB 670 100% 66

AS-SET

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

  • ROA: origin1
  • ROA: none1
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin141.11.156.0/24ROAs covering it name AS203058, not AS138156. If AS138156 should announce it, add a ROA for AS138156.8 of 673
Route object: none141.11.156.0/24Route objects for it name AS203058. A route object for 141.11.156.0/22 with origin AS138156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138156 in the RIR database for the space.8 of 673
ROA: none141.11.156.0/22No ROA covers it. Add a ROA for AS138156, maxLength 22.670 of 673
Route object: RIR141.11.156.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

103.131.200.18/32APNICInvalid: maxLength
140.99.96.0/22ARIN, RADBValid
2401:1240:206::/47RADBNo ROA
2401:1240:206::/48APNIC, RADBValid
2401:1240:207::/48APNIC, RADBValid

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.