bgpreport

Network · data from 2026-11-12

AS18303 SMARTRO-AS-KR-KR - SMARTRO

Registry name: SMARTRO-AS-KR-KR - SMARTRO, KR · not in PeeringDB

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

Announced routes

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

211.193.35.0/24 No ROA None 673 100% 67
211.196.246.128/25 No ROA None 16 2%low visibility 13
211.180.116.192/26 No ROA None 14 2%low visibility 13
210.220.149.48/29 No ROA None 10 1%low visibility 10
210.220.149.64/29 No ROA None 10 1%low visibility 10
211.192.50.0/24 No ROA Other IRR onlyRADB 673 100% 66

AS-SET

AS18303 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 12 are in fix.csv.

  • ROA: none6
  • Route object: none5
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none211.193.35.0/24No ROA covers it. Add a ROA for AS18303, maxLength 24.673 of 673
Route object: none211.193.35.0/24No route object for it. Add a route object with origin AS18303 in the RIR database for the space.673 of 673
ROA: none211.196.246.128/25No ROA covers it. Add a ROA for AS18303, maxLength 25.16 of 673
Route object: none211.196.246.128/25No route object for it. Add a route object with origin AS18303 in the RIR database for the space.16 of 673
ROA: none211.180.116.192/26No ROA covers it. Add a ROA for AS18303, maxLength 26.14 of 673
Route object: none211.180.116.192/26No route object for it. Add a route object with origin AS18303 in the RIR database for the space.14 of 673
ROA: none210.220.149.48/29No ROA covers it. Add a ROA for AS18303, maxLength 29.10 of 673
Route object: none210.220.149.48/29No route object for it. Add a route object with origin AS18303 in the RIR database for the space.10 of 673
ROA: none210.220.149.64/29No ROA covers it. Add a ROA for AS18303, maxLength 29.10 of 673
Route object: none210.220.149.64/29No route object for it. Add a route object with origin AS18303 in the RIR database for the space.10 of 673
ROA: none211.192.50.0/24No ROA covers it. Add a ROA for AS18303, maxLength 24.673 of 673
Route object: RIR211.192.50.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 AS18303 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.