102.55.240.0/21 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 |
|---|---|---|---|---|---|
| AS36903 Maroc Telecom | no ROA | 38 | 34549174671336903 | 2026-09-18 | 2026-09-20 |
| AS6713 Maroc Telecom | no ROA | 3 | 45049669667626713 | 2026-09-18 | 2026-09-20 |
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.48.0.0/13
- RIR
- AFRINIC
- Country
- 🇲🇦 MA
- Status
- allocated
- Allocated
- 2019-03-22
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 102.55.0.0/16 v4 | AS6713 Maroc Telecom | no ROA | 41 | 345491746713 | 2026-09-18 |
| 102.48.0.0/13 v4 | AS6713 Maroc Telecom | no ROA | 41 | 3454955116713 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.