206.123.144.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 |
|---|---|---|---|---|---|
| AS201813 Contrust Solutions S.R.L. | no ROA | 40 | 2265219318201813 | 2026-09-18 | 2026-10-26 |
| AS205960 HDTIDC LIMITED | no ROA | 1 | 2448217476138415138195205960 | 2026-09-18 | 2026-10-26 |
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
- 206.123.128.0/19
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 2015-03-09
Less specific routes
Announced prefixes that contain this one
Nothing less specific is announced.
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.
Recorded changes
| When | Change | Origin | Path |
|---|---|---|---|
| 2026-10-24 14:02:40Z | origin change | AS205960 → AS201813 | 58057174325719318201813 |
| 2026-10-24 02:46:08Z | origin change | AS201813 → AS205960 | 2448217476138415138195205960 |
| 2026-10-24 01:08:22Z | origin change | AS205960 → AS201813 | 50300174325719318201813 |
| 2026-10-23 20:04:51Z | origin change | AS201813 → AS205960 | 2448217476138415138195205960 |