bgpreport

Network · data from 2026-11-12

AS152229 COUPANGCIC-AS-KR-KR - Coupang Inc

Registry name: COUPANGCIC-AS-KR-KR - Coupang Inc, KR · not in PeeringDB

8IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
8No 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 AS152229, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS152229, 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.
118.129.73.0/24 No ROA Other IRR onlyRADB 673 100% 67
118.129.84.0/24 No ROA Other IRR onlyRADB 673 100% 67
211.56.109.0/24 No ROA Other IRR onlyRADB 673 100% 67
115.92.28.0/24 No ROA Other IRR onlyRADB 672 100% 67
139.150.233.0/24 No ROA Other IRR onlyRADB 672 100% 67
139.150.234.0/24 No ROA Other IRR onlyRADB 672 100% 67
211.56.101.0/24 No ROA Other IRR onlyRADB 672 100% 67
211.181.187.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS152229 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 16 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none118.129.73.0/24No ROA covers it. Add a ROA for AS152229, maxLength 24.673 of 673
Route object: RIR118.129.73.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none118.129.84.0/24No ROA covers it. Add a ROA for AS152229, maxLength 24.673 of 673
Route object: RIR118.129.84.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.56.109.0/24No ROA covers it. Add a ROA for AS152229, maxLength 24.673 of 673
Route object: RIR211.56.109.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none115.92.28.0/24No ROA covers it. Add a ROA for AS152229, maxLength 24.672 of 673
Route object: RIR115.92.28.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none139.150.233.0/24No ROA covers it. Add a ROA for AS152229, maxLength 24.672 of 673
Route object: RIR139.150.233.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none139.150.234.0/24No ROA covers it. Add a ROA for AS152229, maxLength 24.672 of 673
Route object: RIR139.150.234.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none211.56.101.0/24No ROA covers it. Add a ROA for AS152229, maxLength 24.672 of 673
Route object: RIR211.56.101.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none211.181.187.0/24No ROA covers it. Add a ROA for AS152229, maxLength 24.672 of 673
Route object: RIR211.181.187.0/24Route 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 AS152229 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.