bgpreport

Network · data from 2026-11-12

AS55609 FSICERT-AS-KR-KR - Financial Security Institute

Registry name: FSICERT-AS-KR-KR - Financial Security Institute, KR · not in PeeringDB

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

Announced routes

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

203.190.4.0/24 No ROA Other IRR onlyRADB 671 100% 66

AS-SET

AS55609 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 46 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced44
ChangePrefix or setDetailFull-table peers
ROA: none203.190.4.0/24No ROA covers it. Add a ROA for AS55609, maxLength 24.671 of 673
Route object: RIR203.190.4.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

39.120.128.0/24RADBNo ROA
58.87.58.0/24RADBNo ROA
58.229.161.0/24RADBNo ROA
61.37.254.0/24RADBNo ROA
61.40.138.0/24RADBNo ROA
61.40.236.0/24RADBNo ROA
61.41.206.0/24RADBNo ROA
61.42.199.0/24RADBNo ROA
61.42.238.0/24RADBNo ROA
118.218.194.0/24RADBNo ROA
121.136.89.0/24RADBNo ROA
121.137.200.0/24RADBNo ROA
121.157.108.0/24RADBNo ROA
121.163.173.0/24RADBNo ROA
121.189.8.224/27RADBNo ROA
125.130.246.0/24RADBNo ROA
168.154.181.0/24RADBNo ROA
182.162.116.0/24RADBNo ROA
182.162.172.0/24RADBNo ROA
183.111.205.64/26RADBNo ROA
203.81.8.0/24RADBNo ROA
203.81.11.0/24RADBNo ROA
203.175.188.0/24RADBNo ROA
203.175.190.0/24RADBNo ROA
203.175.191.0/24RADBNo ROA
203.227.232.0/24RADBNo ROA
203.233.91.0/24RADBNo ROA
203.236.164.0/24RADBNo ROA
203.251.60.0/24RADBNo ROA
210.108.173.0/24RADBNo ROA
210.124.238.0/24RADBNo ROA
210.127.188.0/24RADBNo ROA
211.33.123.0/24RADBNo ROA
211.115.70.0/24RADBNo ROA
211.119.52.0/24RADBNo ROA
211.195.166.0/24RADBNo ROA
211.218.149.0/24RADBNo ROA
211.233.70.0/24RADBNo ROA
218.55.37.0/24RADBNo ROA
218.55.246.0/24RADBNo ROA
218.145.69.192/26RADBNo ROA
220.87.92.0/24RADBNo ROA
222.231.35.0/24RADBNo ROA
222.239.233.0/24RADBNo ROA

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.