Network · data from 2026-11-12

AS218243 EPICJUMP-SYSTEMS

Registry name: EPICJUMP-SYSTEMS Dominik Andreas Jetten trading as EpicJump Systems, DE · PeeringDB

0IPv4 routes

5IPv6 routes 60.0% RPKI valid · 40.0% with a route object

2RPKI invalid 2 origin · 0 maxLength

0No ROA 3 with no route object for this origin

3Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS218243, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS218243, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


2a14:7581:5136::/48	Invalid: origin	None	2 0%low visibility	2
2a14:7581:5710::/44	Invalid: origin	None	2 0%low visibility	2
2a10:fa81:2c00::/40	Valid	None	635 100%	69
2a0f:6280:2200::/40	Valid	RIR databaseRIPE	635 100%	69
2a06:9801:1597::/48	Valid	RIR databaseRIPE	2 0%low visibility	2

2a14:7581:5136::/48

Invalid: origin

None

2 0%low visibility

2a14:7581:5710::/44

Invalid: origin

None

2 0%low visibility

2a10:fa81:2c00::/40

Valid

None

635 100%

2a0f:6280:2200::/40

Valid

RIR databaseRIPE

635 100%

2a06:9801:1597::/48

Valid

RIR databaseRIPE

2 0%low visibility

AS-SET

AS218243's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 5 are in fix.csv.

ROA: origin2
Route object: none3

Change	Prefix or set	Detail	Full-table peers
ROA: origin	2a14:7581:5136::/48	ROAs covering it name AS204464, not AS218243. If AS218243 should announce it, add a ROA for AS218243.	2 of 636
Route object: none	2a14:7581:5136::/48	No route object for it. Add a route object with origin AS218243 in the RIR database for the space.	2 of 636
ROA: origin	2a14:7581:5710::/44	ROAs covering it name AS204464, not AS218243. If AS218243 should announce it, add a ROA for AS218243.	2 of 636
Route object: none	2a14:7581:5710::/44	No route object for it. Add a route object with origin AS218243 in the RIR database for the space.	2 of 636
Route object: none	2a10:fa81:2c00::/40	No route object for it. Add a route object with origin AS218243 in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: origin

2a14:7581:5136::/48

ROAs covering it name AS204464, not AS218243. If AS218243 should announce it, add a ROA for AS218243.

2 of 636

Route object: none

2a14:7581:5136::/48

No route object for it. Add a route object with origin AS218243 in the RIR database for the space.

2 of 636

ROA: origin

2a14:7581:5710::/44

ROAs covering it name AS204464, not AS218243. If AS218243 should announce it, add a ROA for AS218243.

2 of 636

Route object: none

2a14:7581:5710::/44

No route object for it. Add a route object with origin AS218243 in the RIR database for the space.

2 of 636

Route object: none

2a10:fa81:2c00::/40

No route object for it. Add a route object with origin AS218243 in the RIR database for the space.

635 of 636

Route objects not announced

Every route object with origin AS218243 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.