41.220.213.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 |
|---|---|---|---|---|---|
| AS36901 DATANET.COM LLC | no ROA | 35 | 37721166372029436901 | 2026-09-18 | 2026-10-12 |
| AS29032 DATANET LLC | no ROA | 8 | 345493084429032 | 2026-09-23 | 2026-10-12 |
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
- 41.220.208.0/20
- RIR
- AFRINIC
- Country
- 🇺🇬 UG
- Status
- allocated
- Allocated
- 2007-02-06
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 41.220.212.0/23 v4 | AS29032 DATANET LLC | no ROA | 44 | 345493084429032 | 2026-09-18 |
| 41.220.208.0/20 v4 | AS36901 DATANET.COM LLC | no ROA | 48 | 34549237643099036901 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.