204.193.36.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 |
|---|---|---|---|---|---|
| AS3257 GTT Communications Inc. | no ROA | 32 | 377213257 | 2026-09-18 | 2026-09-20 |
| AS26651 CareFusion Corporation | no ROA | 10 | 3454964614688726651 | 2026-09-18 | 2026-09-20 |
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
- 204.193.32.0/19
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 1994-11-25
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-19 08:43:24Z | origin change | AS26651 → AS3257 | 3288403277271743257 |
| 2026-09-19 08:30:40Z | origin change | AS3257 → AS26651 | 295041593564614688726651 |
| 2026-09-18 14:02:36Z | origin change | AS26651 → AS3257 | 3288403277271743257 |
| 2026-09-18 07:14:37Z | origin change | AS3257 → AS26651 | 573814270864614688726651 |