bgpreport

Network · data from 2026-11-12

AS214189 Doyeon Lee

Registry name: DoyeonLee-AS Doyeon Lee, KR · PeeringDB

2IPv4 routes 50.0% RPKI valid · 50.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
2Route objects not announced registered with origin AS214189, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS214189, 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.
160.22.155.0/24 No ROA None 4 1%low visibility 3
199.242.182.0/24 Valid RIR databaseARIN 673 100% 67
2a11:29c0:51::/48 Valid RIR databaseRADB, RIPE 634 100% 68

AS-SET

AS214189's PeeringDB record names no 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 4 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none160.22.155.0/24No ROA covers it. Add a ROA for AS214189, maxLength 24.4 of 673
Route object: none160.22.155.0/24No route object for it. Add a route object with origin AS214189 in the RIR database for the space.4 of 673

Route objects not announced

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

2607:eb40:beef::/48ARINValid
2a0f:9400:750d::/48RIPENo 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.