208.48.165.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 |
|---|---|---|---|---|---|
| AS4455 IX Reach Ltd | no ROA | 30 | 176394455 | 2026-09-18 | 2026-09-18 |
| AS31216 BSO Network Solutions SAS | no ROA | 11 | 37721335631216 | 2026-09-18 | 2026-09-18 |
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
- 208.48.128.0/18
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 1999-07-29
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 208.48.160.0/21 v4 | AS31216 BSO Network Solutions SAS | no ROA | 10 | 3549335631216 | 2026-09-18 |
| 208.48.160.0/21 v4 | AS4455 IX Reach Ltd | no ROA | 31 | 176394455 | 2026-09-18 |
| 208.48.128.0/18 v4 | AS3549 Lumen (fka. Global Crossing) | no ROA | 42 | 3772133563549 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.