121.139.137.0/24 no ROA MOAS
Announced by 2 different origins, which is either a deliberate multi-origin setup or a hijack.
This prefix is announced by more than one AS. Compare how many collector
peers see each origin below: a hijack is usually visible as a second
origin seen by far fewer peers than the legitimate one.
Origins
| Origin AS | RPKI | Peers seeing it | Sample path | First seen | Last seen |
|---|---|---|---|---|---|
| AS23591 LS ITC | no ROA | 43 | 37721378623591 | 2026-09-18 | 2026-10-29 |
| AS3786 LG DACOM Corporation | no ROA | 2 | 4608122146373786 | 2026-09-18 | 2026-10-29 |
RPKI
No ROA covers this prefix
No ROA covers this prefix, so origin validation returns "unknown". That is not a fault; most of the table is still unsigned.
Registry
Who this address space is delegated to, regardless of whether it is routed
- Delegated block
- 121.128.0.0/11
- RIR
- APNIC
- Country
- 🇰🇷 KR
- Status
- allocated
- Allocated
- 2006-04-07
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 121.136.0.0/13 v4 | AS4766 Korea Telecom | no ROA | 43 | 503044766 | 2026-09-18 |
| 121.128.0.0/12 v4 | AS4766 Korea Telecom | no ROA | 43 | 503044766 | 2026-09-18 |
| 121.128.0.0/11 v4 | AS4766 Korea Telecom | no ROA | 43 | 503044766 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.
Recorded changes
| When | Change | Origin | Path |
|---|---|---|---|
| 2026-10-24 01:32:19Z | origin change | AS3786 → AS23591 | 503006939476623591 |
| 2026-10-24 01:08:54Z | origin change | AS23591 → AS3786 | 50300335646373786 |
| 2026-10-22 16:55:36Z | origin change | AS3786 → AS23591 | 2023656939476623591 |
| 2026-10-22 16:32:11Z | origin change | AS23591 → AS3786 | 2162858280676246373786 |
| 2026-10-20 00:51:47Z | origin change | AS3786 → AS23591 | 2023656939476623591 |
| 2026-10-20 00:05:17Z | origin change | AS23591 → AS3786 | 2162858280676246373786 |