bgpreport

Network · data from 2026-11-12

AS10186 REDCROSSNET-AS-KR-KR - Korean Red Cross

Registry name: REDCROSSNET-AS-KR-KR - Korean Red Cross, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10186, 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.
103.127.212.0/24 No ROA Other IRR onlyRADB 672 100% 67
103.127.214.0/24 No ROA Other IRR onlyRADB 672 100% 67
103.127.215.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS10186 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 45 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced39
ChangePrefix or setDetailFull-table peers
ROA: none103.127.212.0/24No ROA covers it. Add a ROA for AS10186, maxLength 24.672 of 673
Route object: RIR103.127.212.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.127.214.0/24No ROA covers it. Add a ROA for AS10186, maxLength 24.672 of 673
Route object: RIR103.127.214.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.127.215.0/24No ROA covers it. Add a ROA for AS10186, maxLength 24.672 of 673
Route object: RIR103.127.215.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

61.251.0.0/20RADBNo ROA
61.251.0.0/24RADBNo ROA
61.251.1.0/24RADBNo ROA
61.251.2.0/23RADBNo ROA
61.251.4.0/23RADBNo ROA
61.251.6.0/24RADBNo ROA
61.251.7.0/24RADBNo ROA
61.251.8.0/23RADBNo ROA
61.251.10.0/24RADBNo ROA
61.251.11.0/24RADBNo ROA
61.251.12.0/24RADBNo ROA
61.251.13.0/24RADBNo ROA
61.251.14.0/23RADBNo ROA
103.127.212.0/22RADBNo ROA
103.127.212.0/25RADBNo ROA
103.127.212.128/26RADBNo ROA
103.127.212.192/26RADBNo ROA
211.172.40.0/22RADBNo ROA
211.232.1.0/24RADBNo ROA
211.232.2.0/23RADBNo ROA
211.232.4.0/24RADBNo ROA
211.232.24.0/23RADBNo ROA
211.237.80.0/20RADBNo ROA
211.238.160.0/20RADBNo ROA
211.238.160.0/24RADBNo ROA
211.238.161.0/24RADBNo ROA
211.238.162.0/24RADBNo ROA
211.238.163.0/24RADBNo ROA
211.238.164.0/24RADBNo ROA
211.238.165.0/24RADBNo ROA
211.238.166.0/24RADBNo ROA
211.238.167.0/24RADBNo ROA
211.238.168.0/24RADBNo ROA
211.238.169.0/24RADBNo ROA
211.238.170.0/24RADBNo ROA
211.238.171.0/24RADBNo ROA
211.238.172.0/24RADBNo ROA
211.238.173.0/25RADBNo ROA
211.238.174.0/23RADBNo 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.