31.217.128.0/19 RPKI valid MOAS

Announced by 3 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
AS4455 IX Reach Ltd RPKI valid 37 345494455 2026-09-18 2026-09-18
AS31216 BSO Network Solutions SAS RPKI valid 5 2040922076631216 2026-09-18 2026-09-18
AS43531 BSO Network Solutions SAS RPKI valid 1 55720693943531 2026-09-18 2026-09-18

RPKI

3 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
31.217.128.0/19 /24 AS4455 ripe authorises it
31.217.128.0/19 /24 AS31216 ripe wrong origin
31.217.128.0/19 /24 AS43531 ripe wrong origin

Registry

Who this address space is delegated to, regardless of whether it is routed

Delegated block
31.217.128.0/19
RIR
RIPENCC
Country
🇫🇷 FR
Status
allocated
Allocated
2011-08-11

Less specific routes

Announced prefixes that contain this one

Nothing less specific is announced.

More specific routes

6 announced prefixes inside this one

Prefix Origin RPKI Peers First seen
31.217.129.0/24 v4 AS4455 IX Reach Ltd RPKI valid 34 2026-09-18
31.217.129.0/24 v4 AS43531 BSO Network Solutions SAS RPKI valid 7 2026-09-18
31.217.130.0/24 v4 AS4455 IX Reach Ltd RPKI valid 41 2026-09-18
31.217.131.0/24 v4 AS4455 IX Reach Ltd RPKI valid 43 2026-09-18
31.217.135.0/24 v4 AS4455 IX Reach Ltd RPKI valid 28 2026-09-18
31.217.135.0/24 v4 AS31216 BSO Network Solutions SAS RPKI valid 14 2026-09-18