2606:7e00:8::/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 |
|---|---|---|---|---|---|
| AS3064 HDC/HW Enterprise, LLC | no ROA | 25 | 3772133563064 | 2026-09-18 | 2026-09-22 |
| AS18447 HDC/HW Enterprise, LLC | no ROA | 10 | 149071915118447 | 2026-09-18 | 2026-09-22 |
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
- 2606:7e00::/32
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 2011-02-10
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.
Recorded changes
| When | Change | Origin | Path |
|---|---|---|---|
| 2026-09-22 00:55:46Z | origin change | AS18447 → AS3064 | 4943221551048362129933563064 |
| 2026-09-21 17:28:45Z | origin change | AS3064 → AS18447 | 3454929141915118447 |
| 2026-09-21 05:08:28Z | origin change | AS18447 → AS3064 | 2162858280676233563064 |
| 2026-09-20 04:44:57Z | origin change | AS3064 → AS18447 | 348002963290021915118447 |
| 2026-09-19 13:47:45Z | origin change | AS18447 → AS3064 | 29504693933563064 |
| 2026-09-19 12:04:11Z | origin change | AS3064 → AS18447 | 56662130301915118447 |
| 2026-09-18 05:35:59Z | origin change | AS18447 → AS3064 | 4943248362176433563064 |