bgpreport

Network · data from 2026-11-12

AS152281 SHARE-AS-KR-KR - onesolution

Registry name: SHARE-AS-KR-KR - onesolution, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS152281, 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.
121.133.165.160/28 No ROA None 13 2%low visibility 13
49.128.194.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
49.128.220.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
101.55.4.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
101.55.9.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
101.55.10.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
101.55.35.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.6.74.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.7.33.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.7.35.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
124.66.218.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67

AS-SET

AS152281 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 2 are in fix.csv.

  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none121.133.165.160/28No ROA covers it. Add a ROA for AS152281, maxLength 28.13 of 673
Route object: none121.133.165.160/28No route object for it. Add a route object with origin AS152281 in the RIR database for the space.13 of 673

Route objects not announced

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