205.194.56.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 |
|---|---|---|---|---|---|
| AS2667 Shared Services Canada | no ROA | 41 | 226528122667 | 2026-09-18 | 2026-10-10 |
| AS2675 Shared Services Canada | no ROA | 2 | 14035772675 | 2026-09-18 | 2026-10-10 |
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
- 205.192.0.0/14
- RIR
- ARIN
- Country
- 🇨🇦 CA
- Status
- allocated
- Allocated
- 1995-03-27
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-10-08 22:40:28Z | origin change | AS2675 → AS2667 | 333312738122667 |
| 2026-10-08 22:36:29Z | origin change | AS2667 → AS2675 | 140357726752675267526752675 |
| 2026-10-08 11:02:27Z | origin change | AS2675 → AS2667 | 354933568122667 |
| 2026-10-08 02:01:23Z | origin change | AS2667 → AS2675 | 1403577646126752675 |
| 2026-09-27 21:10:21Z | origin change | AS2675 → AS2667 | 49432215510315431748122667 |
| 2026-09-27 20:30:35Z | origin change | AS2667 → AS2675 | 140357726752675267526752675 |