bgpreport

Network · data from 2026-11-12

AS152205 IMOBI-AS-KR-KR - imobi inc,

Registry name: IMOBI-AS-KR-KR - imobi inc,, KR · not in PeeringDB

4IPv4 routes 25.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
0Route objects not announced registered with origin AS152205, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS152205, 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.
119.30.128.0/18 No ROA Other IRR onlyRADB 672 100% 69
157.119.36.0/22 No ROA Other IRR onlyRADB 672 100% 69
202.68.224.0/19 No ROA Other IRR onlyRADB 672 100% 67
160.30.232.0/23 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS152205 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 6 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none119.30.128.0/18No ROA covers it. Add a ROA for AS152205, maxLength 18.672 of 673
Route object: RIR119.30.128.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none157.119.36.0/22No ROA covers it. Add a ROA for AS152205, maxLength 22.672 of 673
Route object: RIR157.119.36.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none202.68.224.0/19No ROA covers it. Add a ROA for AS152205, maxLength 19.672 of 673
Route object: RIR202.68.224.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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