192.160.103.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
AS14265 TPx Communications	no ROA	37	34549 1299 14265	2026-09-18	2026-10-05
AS65011	no ROA	1	55720 6939 14265 65011	2026-09-18	2026-10-05

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.160.103.0/24
RIR: ARIN
Country: 🇺🇸 US
Status: allocated
Allocated: 1992-05-18

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-01 08:33:45Z	origin change	AS65011 → AS14265	852 1299 14265
2026-10-01 07:59:34Z	origin change	AS14265 → AS65011	55720 6939 14265 65011
2026-09-29 17:59:17Z	origin change	AS65011 → AS14265	852 1299 14265
2026-09-29 17:08:15Z	origin change	AS14265 → AS65011	55720 6939 14265 65011
2026-09-29 03:48:42Z	origin change	AS65011 → AS14265	852 1299 14265
2026-09-28 21:21:48Z	origin change	AS14265 → AS65011	55720 6939 14265 65011
2026-09-22 11:38:29Z	origin change	AS65011 → AS14265	852 1299 14265
2026-09-22 11:29:19Z	origin change	AS14265 → AS65011	55720 6939 14265 65011