85.189.120.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 |
|---|---|---|---|---|---|
| AS3257 GTT Communications Inc. | no ROA | 42 | 345493257 | 2026-09-18 | 2026-09-19 |
| AS979 NetLab Global | no ROA | 1 | 443933571010099979 | 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
- 85.189.0.0/16
- RIR
- RIPENCC
- Country
- 🇬🇧 GB
- Status
- allocated
- Allocated
- 2004-12-07
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 85.189.0.0/16 v4 | AS3257 GTT Communications Inc. | no ROA | 43 | 345493257 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.