Network · data from 2026-11-12

AS10061 FSS-AS-KR - Financial Supervisory Service

Registry name: FSS-AS-KR - Financial Supervisory Service, KR · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 50.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

4No ROA 2 with no route object for this origin

4Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS10061, seen from no peer

Announced routes

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


222.110.182.0/25	No ROA	None	15 2%low visibility	12
211.217.133.48/28	No ROA	None	12 2%low visibility	12
61.73.100.0/25	No ROA	Other IRR onlyRADB	33 5%low visibility	24
61.73.100.128/25	No ROA	Other IRR onlyRADB	30 4%low visibility	24

222.110.182.0/25

No ROA

None

15 2%low visibility

211.217.133.48/28

No ROA

None

12 2%low visibility

61.73.100.0/25

No ROA

Other IRR onlyRADB

33 5%low visibility

61.73.100.128/25

No ROA

Other IRR onlyRADB

30 4%low visibility

AS-SET

AS10061 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 8 are in fix.csv.

ROA: none4
Route object: none2
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
ROA: none	222.110.182.0/25	No ROA covers it. Add a ROA for AS10061, maxLength 25.	15 of 673
Route object: none	222.110.182.0/25	No route object for it. Add a route object with origin AS10061 in the RIR database for the space.	15 of 673
ROA: none	211.217.133.48/28	No ROA covers it. Add a ROA for AS10061, maxLength 28.	12 of 673
Route object: none	211.217.133.48/28	No route object for it. Add a route object with origin AS10061 in the RIR database for the space.	12 of 673
ROA: none	61.73.100.0/25	No ROA covers it. Add a ROA for AS10061, maxLength 25.	33 of 673
Route object: RIR	61.73.100.0/25	Route object only in RADB. Add it in the RIR database for the space.	33 of 673
ROA: none	61.73.100.128/25	No ROA covers it. Add a ROA for AS10061, maxLength 25.	30 of 673
Route object: RIR	61.73.100.128/25	Route object only in RADB. Add it in the RIR database for the space.	30 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

222.110.182.0/25

No ROA covers it. Add a ROA for AS10061, maxLength 25.

15 of 673

Route object: none

222.110.182.0/25

No route object for it. Add a route object with origin AS10061 in the RIR database for the space.

15 of 673

ROA: none

211.217.133.48/28

No ROA covers it. Add a ROA for AS10061, maxLength 28.

12 of 673

Route object: none

211.217.133.48/28

No route object for it. Add a route object with origin AS10061 in the RIR database for the space.

12 of 673

ROA: none

61.73.100.0/25

No ROA covers it. Add a ROA for AS10061, maxLength 25.

33 of 673

Route object: RIR

61.73.100.0/25

Route object only in RADB. Add it in the RIR database for the space.

33 of 673

ROA: none

61.73.100.128/25

No ROA covers it. Add a ROA for AS10061, maxLength 25.

30 of 673

Route object: RIR

61.73.100.128/25

Route object only in RADB. Add it in the RIR database for the space.

30 of 673

Route objects not announced

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