185.244.240.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 |
|---|---|---|---|---|---|
| AS206666 MULTIMEDIA-NET DOO SKOPJE | no ROA | 47 | 693925467206666 | 2026-09-18 | 2026-10-09 |
| AS25467 Akton d.o.o. | no ROA | 1 | 494324836225467 | 2026-09-28 | 2026-10-09 |
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
- 185.244.240.0/22
- RIR
- RIPENCC
- Country
- 🇲🇰 MK
- Status
- allocated
- Allocated
- 2018-02-05
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-09-28 00:06:42Z | origin change | AS25467 → AS206666 | 202365693925467206666 |
| 2026-09-28 00:03:49Z | origin change | AS206666 → AS25467 | 494324836225467 |
| 2026-09-27 22:29:58Z | origin change | AS25467 → AS206666 | 852693925467206666 |
| 2026-09-27 22:01:31Z | origin change | AS206666 → AS25467 | 494324836225467 |