192.176.242.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
AS8473 Bahnhof AB	no ROA	38	34549 1299 8473	2026-09-18	2026-10-12
AS65534	no ROA	3	3333 8473 65534	2026-09-18	2026-10-12

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: 192.176.0.0/16
RIR: RIPENCC
Country: 🇸🇪 SE
Status: assigned
Allocated: 2000-03-17

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-09-29 08:46:59Z	origin change	AS65534 → AS8473	204092 34019 25091 8473
2026-09-29 08:43:29Z	origin change	AS8473 → AS65534	24482 8473 65534
2026-09-29 08:42:26Z	origin change	AS8473 → AS65534	34927 56655 8473 65534
2026-09-29 08:42:26Z	origin change	AS65534 → AS8473	208972 5405 5405 5405 8473