187.108.171.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 |
|---|---|---|---|---|---|
| AS22381 SAMM (Megatelecom) | no ROA | 39 | 377213746822381 | 2026-09-18 | 2026-09-21 |
| AS262589 SAMM (Internexa) | no ROA | 1 | 24482262589 | 2026-09-18 | 2026-09-21 |
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
- 187.108.160.0/19
- RIR
- LACNIC
- Country
- 🇧🇷 BR
- Status
- allocated
- Allocated
- 2010-04-16
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 187.108.160.0/19 v4 | AS262589 SAMM (Internexa) | no ROA | 42 | 24482262589 | 2026-09-18 |
| 187.108.128.0/18 v4 | AS262589 SAMM (Internexa) | no ROA | 2 | 24482262589 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.