2801:c4:1303::/48 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 |
|---|---|---|---|---|---|
| AS17072 TOTAL PLAY TELECOMUNICACIONES, S.A.P.I. DE C.V. | no ROA | 31 | 377212845817072 | 2026-09-18 | 2026-11-11 |
| AS272336 Secretaría de Relaciones Exteriores | no ROA | 2 | 5738142708129917072272336 | 2026-11-05 | 2026-11-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
- 2801:c4:1000::/36
- RIR
- LACNIC
- Country
- 🇲🇽 MX
- Status
- assigned
- Allocated
- 2023-10-17
Less specific routes
Announced prefixes that contain this one
Nothing less specific is announced.
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.