102.176.92.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 ASRPKI Peers seeing itSample path First seenLast seen
AS29614 TELECEL GHANA AS INTERNATIONAL TRANSIT no ROA 38 345491299865729614 2026-09-18 2026-09-23
AS64513 no ROA 2 333386572961464513 2026-09-18 2026-09-23

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
102.176.0.0/17
RIR
AFRINIC
Country
🇬🇭 GH
Status
allocated
Allocated
2017-12-15

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
102.176.64.0/18 v4 AS29614 TELECEL GHANA AS INTERNATIONAL TRANSIT no ROA 47 345493761329614 2026-09-18
102.176.0.0/17 v4 AS29614 TELECEL GHANA AS INTERNATIONAL TRANSIT no ROA 40 34549865729614 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-18 07:14:29Z origin change AS64513 → AS29614 57381503041299865729614