bgpreport

Network · data from 2026-11-12

AS45393 SFS-AS-KR-KR - SFS

Registry name: SFS-AS-KR-KR - SFS, 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 AS45393, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS45393, 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.102.100.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
58.102.101.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
58.102.102.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
58.102.103.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
211.63.20.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
222.110.7.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 66
222.110.8.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 66
222.110.9.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 66

AS-SET

AS45393 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: none58.102.100.0/24No ROA covers it. Add a ROA for AS45393, maxLength 24.673 of 673
Route object: RIR58.102.100.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none58.102.101.0/24No ROA covers it. Add a ROA for AS45393, maxLength 24.673 of 673
Route object: RIR58.102.101.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none58.102.102.0/24No ROA covers it. Add a ROA for AS45393, maxLength 24.673 of 673
Route object: RIR58.102.102.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none58.102.103.0/24No ROA covers it. Add a ROA for AS45393, maxLength 24.673 of 673
Route object: RIR58.102.103.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none211.63.20.0/24No ROA covers it. Add a ROA for AS45393, maxLength 24.673 of 673
Route object: RIR211.63.20.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none222.110.7.0/24No ROA covers it. Add a ROA for AS45393, maxLength 24.673 of 673
Route object: RIR222.110.7.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none222.110.8.0/24No ROA covers it. Add a ROA for AS45393, maxLength 24.673 of 673
Route object: RIR222.110.8.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none222.110.9.0/24No ROA covers it. Add a ROA for AS45393, maxLength 24.673 of 673
Route object: RIR222.110.9.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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