2001:df3:fc00::/48 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 |
|---|---|---|---|---|---|
| AS134548 DXTL Tseung Kwan O Service | no ROA | 33 | 3800158453134548 | 2026-09-18 | 2026-09-20 |
| AS62325 HUNGTAK International Network Limited | no ROA | 1 | 2448262325 | 2026-09-18 | 2026-09-20 |
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
- 2001:df3:fc00::/48
- RIR
- APNIC
- Country
- ðŸ‡ðŸ‡° HK
- Status
- assigned
- Allocated
- 2015-05-06
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 2000::/6 v6 | AS29632 Netassist International EOOD | no ROA | 1 | 6121829632 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.