14.49.22.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 |
|---|---|---|---|---|---|
| AS4040 Korea Telecom | no ROA | 6 | 3800129144040 | 2026-09-18 | 2026-09-19 |
| AS4766 Korea Telecom | no ROA | 1 | 496733150031133237644766 | 2026-09-18 | 2026-09-19 |
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
- 14.32.0.0/11
- RIR
- APNIC
- Country
- 🇰🇷 KR
- Status
- allocated
- Allocated
- 2010-08-02
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 14.49.16.0/21 v4 | AS4766 Korea Telecom | no ROA | 43 | 503044766 | 2026-09-18 |
| 14.48.0.0/13 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.