bgpreport

Network · data from 2026-11-12

AS38427 STXIDC-AS-KR-KR - FORCETEC Co., LTD.

Registry name: STXIDC-AS-KR-KR - FORCETEC Co., LTD., KR · not in PeeringDB

8IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
8No 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 AS38427, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38427, 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.
61.43.209.0/24 No ROA Other IRR onlyRADB 673 100% 67
61.74.191.0/24 No ROA Other IRR onlyRADB 673 100% 67
61.75.253.0/24 No ROA Other IRR onlyRADB 673 100% 67
61.75.254.0/24 No ROA Other IRR onlyRADB 673 100% 67
121.177.31.0/24 No ROA Other IRR onlyRADB 673 100% 67
203.169.4.0/23 No ROA Other IRR onlyRADB 673 100% 67
211.51.145.0/24 No ROA Other IRR onlyRADB 673 100% 67
218.145.190.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS38427 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 16 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none61.43.209.0/24No ROA covers it. Add a ROA for AS38427, maxLength 24.673 of 673
Route object: RIR61.43.209.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none61.74.191.0/24No ROA covers it. Add a ROA for AS38427, maxLength 24.673 of 673
Route object: RIR61.74.191.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none61.75.253.0/24No ROA covers it. Add a ROA for AS38427, maxLength 24.673 of 673
Route object: RIR61.75.253.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none61.75.254.0/24No ROA covers it. Add a ROA for AS38427, maxLength 24.673 of 673
Route object: RIR61.75.254.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none121.177.31.0/24No ROA covers it. Add a ROA for AS38427, maxLength 24.673 of 673
Route object: RIR121.177.31.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.169.4.0/23No ROA covers it. Add a ROA for AS38427, maxLength 23.673 of 673
Route object: RIR203.169.4.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.51.145.0/24No ROA covers it. Add a ROA for AS38427, maxLength 24.673 of 673
Route object: RIR211.51.145.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none218.145.190.0/24No ROA covers it. Add a ROA for AS38427, maxLength 24.673 of 673
Route object: RIR218.145.190.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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