102.36.220.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 |
|---|---|---|---|---|---|
| AS37027 Simbanet (T) Limited | no ROA | 28 | 377213710037027 | 2026-09-18 | 2026-10-11 |
| AS15399 Wananchi Group (Kenya) Limited | no ROA | 21 | 345493727115399 | 2026-09-18 | 2026-10-11 |
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
- 102.36.216.0/21
- RIR
- AFRINIC
- Country
- 🇺🇬 UG
- Status
- allocated
- Allocated
- 2019-07-30
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 102.36.216.0/21 v4 | AS37027 Simbanet (T) Limited | no ROA | 49 | 345493710037027 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.