159.100.58.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 |
|---|---|---|---|---|---|
| AS205019 G1SAT B.V. | no ROA | 40 | 6939205019 | 2026-09-18 | 2026-09-30 |
| AS26857 TrustComm, Inc. | no ROA | 6 | 34549646126857 | 2026-09-18 | 2026-09-30 |
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
- 159.100.58.0/23
- RIR
- RIPENCC
- Country
- 🇳🇱 NL
- Status
- assigned
- Allocated
- 1992-03-31
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-26 02:35:51Z | origin change | AS26857 → AS205019 | 328840327727174205019 |
| 2026-09-26 01:27:10Z | origin change | AS205019 → AS26857 | 48185646126857 |
| 2026-09-23 04:47:09Z | origin change | AS26857 → AS205019 | 349276939205019 |
| 2026-09-23 04:45:44Z | origin change | AS205019 → AS26857 | 7018646126857 |
| 2026-09-21 11:08:16Z | origin change | AS26857 → AS205019 | 50300174205019 |
| 2026-09-21 11:08:04Z | origin change | AS205019 → AS26857 | 503002914646126857 |
| 2026-09-18 09:17:50Z | origin change | AS26857 → AS205019 | 20236550673174205019 |
| 2026-09-18 09:17:00Z | origin change | AS205019 → AS26857 | 132825174646126857 |
| 2026-09-18 09:16:56Z | origin change | AS26857 → AS205019 | 5805718366939205019 |
| 2026-09-18 09:16:52Z | origin change | AS205019 → AS26857 | 20236550673174646126857 |