216.34.207.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 |
|---|---|---|---|---|---|
| AS26762 Conversant, LLC | no ROA | 33 | 34549646126762 | 2026-09-18 | 2026-09-25 |
| AS25751 Conversant, Inc. | no ROA | 9 | 3772125751 | 2026-09-18 | 2026-09-25 |
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
- 216.32.0.0/14
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 1998-07-30
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 216.34.192.0/19 v4 | AS3561 Lumen (ex. Savvis) | no ROA | 43 | 580573561 | 2026-09-18 |
| 216.32.0.0/14 v4 | AS3561 Lumen (ex. Savvis) | no ROA | 43 | 580573561 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.
Recorded changes
| When | Change | Origin | Path |
|---|---|---|---|
| 2026-09-23 16:27:12Z | origin change | AS25751 → AS26762 | 328840327727174646164612676226762 |
| 2026-09-23 10:58:27Z | origin change | AS26762 → AS25751 | 3772125751 |
| 2026-09-22 11:39:35Z | origin change | AS25751 → AS26762 | 852646164612676226762 |
| 2026-09-22 11:29:54Z | origin change | AS26762 → AS25751 | 55720693925751 |
| 2026-09-22 07:13:28Z | origin change | AS25751 → AS26762 | 852646164612676226762 |
| 2026-09-22 06:22:04Z | origin change | AS26762 → AS25751 | 3772125751 |