2804:469c::/33 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 |
|---|---|---|---|---|---|
| AS267000 META-CTi Tecnologia da Informacao LTDA. | no ROA | 31 | 37721262287267000 | 2026-09-18 | 2026-10-09 |
| AS262287 Latitude.sh LTDA | no ROA | 4 | 566622235652468262287 | 2026-10-08 | 2026-10-09 |
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
- 2804:469c::/32
- RIR
- LACNIC
- Country
- 🇧🇷 BR
- Status
- allocated
- Allocated
- 2017-11-09
Less specific routes
Announced prefixes that contain this one
Nothing less specific is announced.
More specific routes
2 announced prefixes inside this one
| Prefix | Origin | RPKI | Peers | First seen |
|---|---|---|---|---|
| 2804:469c::/48 v6 | AS262287 Latitude.sh LTDA | no ROA | 4 | 2026-10-08 |
| 2804:469c::/48 v6 | AS267000 META-CTi Tecnologia da Informacao LTDA. | no ROA | 31 | 2026-09-18 |