103.11.68.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 |
|---|---|---|---|---|---|
| AS3561 Lumen (ex. Savvis) | no ROA | 30 | 5062833563561 | 2026-09-18 | 2026-09-21 |
| AS60117 Host Sailor Ltd | no ROA | 11 | 34549900960117 | 2026-09-18 | 2026-09-21 |
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
- 103.11.68.0/22
- RIR
- APNIC
- Country
- 🇵🇰 PK
- Status
- allocated
- Allocated
- 2011-10-17
Less specific routes
Announced prefixes that contain this one
Nothing less specific is announced.
More specific routes
1 announced prefixes inside this one
| Prefix | Origin | RPKI | Peers | First seen |
|---|---|---|---|---|
| 103.11.70.0/24 v4 | AS3319 User Association of Ukrainian Research and Academic Network URAN | RPKI valid | 41 | 2026-09-18 |