162.128.193.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 |
|---|---|---|---|---|---|
| AS4229 Zenlayer Inc | no ROA | 39 | 176394229 | 2026-09-18 | 2026-10-14 |
| AS21859 Zenlayer Inc | no ROA | 3 | 2448221859 | 2026-09-18 | 2026-10-14 |
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
- 162.128.0.0/16
- RIR
- APNIC
- Country
- 🇸🇬 SG
- Status
- allocated
- Allocated
- 1992-11-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-10-14 18:06:07Z | origin change | AS4229 → AS21859 | 5572021859 |
| 2026-10-14 18:04:01Z | origin change | AS21859 → AS4229 | 2162858280676229144229 |
| 2026-10-14 03:32:35Z | origin change | AS21859 → AS4229 | 3798956300132132465764534229 |
| 2026-10-14 02:25:51Z | origin change | AS4229 → AS21859 | 46081221463721859 |
| 2026-10-08 22:36:35Z | origin change | AS21859 → AS4229 | 5805717464534229 |
| 2026-10-08 22:34:41Z | origin change | AS4229 → AS21859 | 46081221463721859 |
| 2026-10-08 11:58:36Z | origin change | AS4229 → AS21859 | 46081221463721859 |
| 2026-10-08 11:57:57Z | origin change | AS21859 → AS4229 | 4818529144229 |
| 2026-10-02 13:38:05Z | origin change | AS21859 → AS4229 | 32884032772717464534229 |
| 2026-10-02 11:34:55Z | origin change | AS4229 → AS21859 | 46081221463721859 |