205.211.134.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 |
|---|---|---|---|---|---|
| AS2675 Shared Services Canada | no ROA | 39 | 14035772675 | 2026-09-18 | 2026-09-30 |
| AS806 Shared Services Canada | no ROA | 3 | 333311036509376806 | 2026-09-18 | 2026-09-30 |
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.211.132.0/22
- RIR
- ARIN
- Country
- 🇨🇦 CA
- Status
- allocated
- Allocated
- 1995-10-20
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-29 13:05:53Z | origin change | AS806 → AS2675 | 295043939217457726752675 |
| 2026-09-29 12:38:02Z | origin change | AS2675 → AS806 | 460875756509376806 |
| 2026-09-27 20:30:39Z | origin change | AS806 → AS2675 | 140357726752675 |
| 2026-09-27 20:19:59Z | origin change | AS2675 → AS806 | 333311036509376806 |
| 2026-09-27 20:02:54Z | origin change | AS806 → AS2675 | 3333127357726752675 |
| 2026-09-27 19:57:18Z | origin change | AS2675 → AS806 | 333311036509376806 |
| 2026-09-27 17:10:57Z | origin change | AS806 → AS2675 | 3333127357726752675 |
| 2026-09-27 16:58:42Z | origin change | AS2675 → AS806 | 3822924490115376509376806 |
| 2026-09-25 17:14:43Z | origin change | AS806 → AS2675 | 85257726752675 |
| 2026-09-25 17:00:14Z | origin change | AS2675 → AS806 | 3822924490115376509376806 |