38.247.68.0/23 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 |
|---|---|---|---|---|---|
| AS272786 X99 INTERNET | no ROA | 32 | 345492914398991272786 | 2026-09-24 | 2026-10-31 |
| AS398991 X99 | no ROA | 10 | 3772160068272786398991 | 2026-09-18 | 2026-10-31 |
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
- 38.0.0.0/8
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 1991-04-16
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 38.0.0.0/8 v4 | AS174 Cogent Communications, LLC | no ROA | 42 | 34549174 | 2026-09-18 |
More specific routes
2 announced prefixes inside this one
| Prefix | Origin | RPKI | Peers | First seen |
|---|---|---|---|---|
| 38.247.68.0/24 v4 | AS398991 X99 | no ROA | 44 | 2026-09-18 |
| 38.247.69.0/24 v4 | AS398991 X99 | no ROA | 44 | 2026-09-18 |