2401:eee0:80::/42 RPKI invalid 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
RPKI
2 ROAs cover this prefix
Registry
Who this address space is delegated to, regardless of whether it is routed
- Delegated block
- 2401:eee0::/32
- RIR
- APNIC
- Country
- 🇧🇩 BD
- Status
- allocated
- Allocated
- 2025-02-13
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 2401:eee0::/36 v6 | AS65501 | RPKI invalid | 1 | 3800194985868214943365501 | 2026-09-18 |
| 2401:eee0::/36 v6 | AS149433 FM Networks | RPKI invalid | 1 | 5666213030949858682149433 | 2026-09-19 |
| 2401:eee0::/34 v6 | AS149433 FM Networks | RPKI valid | 37 | 3800158682149433 | 2026-09-18 |
| 2401:eee0::/32 v6 | AS149433 FM Networks | RPKI valid | 37 | 3800158682149433 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.