197.29.122.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 |
|---|---|---|---|---|---|
| AS328126 Orange Tunisie | no ROA | 29 | 580571743727337447328126 | 2026-09-20 | 2026-10-28 |
| AS37447 ORANGE RDC | no ROA | 10 | 2089726017137447 | 2026-10-07 | 2026-10-28 |
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
- 197.0.0.0/11
- RIR
- AFRINIC
- Country
- 🇹🇳 TN
- Status
- allocated
- Allocated
- 2010-05-03
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 197.29.64.0/18 v4 | AS37492 Orange Tunisie | no ROA | 42 | 34549551137492 | 2026-09-18 |
| 197.29.0.0/16 v4 | AS37492 Orange Tunisie | no ROA | 42 | 34549551137492 | 2026-09-18 |
| 197.28.0.0/15 v4 | AS37492 Orange Tunisie | no ROA | 42 | 3333676237492 | 2026-09-18 |
| 197.0.0.0/11 v4 | AS2609 Tunisia BackBone AS | no ROA | 42 | 333367622609 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.