63.79.88.0/22 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 |
|---|---|---|---|---|---|
| AS32851 Walmart Inc. | no ROA | 31 | 3454912992277332851 | 2026-09-18 | 2026-09-19 |
| AS10695 Wal-Mart Stores, Inc. | no ROA | 10 | 3549335620910695 | 2026-09-18 | 2026-09-19 |
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
- 63.64.0.0/10
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 1999-01-22
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 63.64.0.0/12 v4 | AS701 Verizon Business | no ROA | 42 | 17639701 | 2026-09-18 |
More specific routes
2 announced prefixes inside this one
| Prefix | Origin | RPKI | Peers | First seen |
|---|---|---|---|---|
| 63.79.89.0/24 v4 | AS10695 Wal-Mart Stores, Inc. | no ROA | 43 | 2026-09-18 |
| 63.79.91.0/24 v4 | AS32851 Walmart Inc. | no ROA | 41 | 2026-09-18 |