45.132.16.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 |
|---|---|---|---|---|---|
| AS59692 IQWeb FZ-LLC | no ROA | 41 | 3772159692 | 2026-09-18 | 2026-10-14 |
| AS57724 DDOS-GUARD LTD | no ROA | 2 | 4967357724 | 2026-09-18 | 2026-10-14 |
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
- 45.132.16.0/22
- RIR
- RIPENCC
- Country
- 🇦🇪 AE
- Status
- allocated
- Allocated
- 2019-07-22
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-07 15:51:17Z | origin change | AS57724 → AS59692 | 14907129959692 |
| 2026-10-07 14:42:24Z | origin change | AS59692 → AS57724 | 349275665557724 |
| 2026-10-02 01:19:31Z | origin change | AS57724 → AS59692 | 1328253356291459692 |
| 2026-10-01 23:43:11Z | origin change | AS59692 → AS57724 | 349275665557724 |