bgpreport

Network · data from 2026-11-12

AS38704 IDISPOWERTEL-AS-KR-KR - IDIS powertel

Registry name: IDISPOWERTEL-AS-KR-KR - IDIS powertel, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38704, 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.39.208.0/24 No ROA None 673 100% 67
112.175.232.0/27 No ROA None 14 2%low visibility 13
112.175.232.0/28 No ROA None 13 2%low visibility 13
112.175.232.16/28 No ROA None 13 2%low visibility 13
211.47.58.224/28 No ROA Nonecovered by 211.47.58.0/24 13 2%low visibility 13
211.188.7.0/24 No ROA Other IRR onlyRADB 673 100% 67
211.188.11.0/24 No ROA Other IRR onlyRADB 673 100% 67
211.47.58.0/24 No ROA Other IRR onlyRADB 667 99% 67

AS-SET

AS38704 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 18 are in fix.csv.

  • ROA: none8
  • Route object: none5
  • Route object: RIR3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none211.39.208.0/24No ROA covers it. Add a ROA for AS38704, maxLength 24.673 of 673
Route object: none211.39.208.0/24No route object for it. Add a route object with origin AS38704 in the RIR database for the space.673 of 673
ROA: none112.175.232.0/27No ROA covers it. Add a ROA for AS38704, maxLength 27.14 of 673
Route object: none112.175.232.0/27No route object for it. Add a route object with origin AS38704 in the RIR database for the space.14 of 673
ROA: none112.175.232.0/28No ROA covers it. Add a ROA for AS38704, maxLength 28.13 of 673
Route object: none112.175.232.0/28No route object for it. Add a route object with origin AS38704 in the RIR database for the space.13 of 673
ROA: none112.175.232.16/28No ROA covers it. Add a ROA for AS38704, maxLength 28.13 of 673
Route object: none112.175.232.16/28No route object for it. Add a route object with origin AS38704 in the RIR database for the space.13 of 673
ROA: none211.47.58.224/28No ROA covers it. Add a ROA for AS38704, maxLength 28.13 of 673
Route object: none211.47.58.224/28No route object for it. A route object for 211.47.58.0/24 with origin AS38704 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS38704 in the RIR database for the space.13 of 673
ROA: none211.188.7.0/24No ROA covers it. Add a ROA for AS38704, maxLength 24.673 of 673
Route object: RIR211.188.7.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.188.11.0/24No ROA covers it. Add a ROA for AS38704, maxLength 24.673 of 673
Route object: RIR211.188.11.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.47.58.0/24No ROA covers it. Add a ROA for AS38704, maxLength 24.667 of 673
Route object: RIR211.47.58.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

182.162.191.0/24RADBNo ROA
211.39.215.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.