Network · data from 2026-11-12

AS215133 JAKUB-WITKOWSKI

Registry name: JAKUB-WITKOWSKI Jakub Witkowski, PL · PeeringDB

9IPv4 routes 66.7% RPKI valid · 66.7% with a route object

0IPv6 routes

3RPKI invalid 3 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 AS215133, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS215133, 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.


13.141.64.0/24	Invalid: origin	Other origin only	2 0%low visibility	1
13.141.35.0/24	Invalid: origin	Other origin only	1 0%low visibility	1
79.182.27.0/24	Invalid: origin	Other origin only	0 0%low visibility	1
201.4.72.0/24	Valid	RIR databaseRIPE	672 100%	66
31.57.12.0/24	Valid	RIR databaseRADB, RIPE	671 100%	67
48.103.142.0/24	Valid	RIR databaseRIPE	671 100%	67
77.216.4.0/24	Valid	RIR databaseRADB, RIPE	670 100%	67
130.78.11.0/24	Valid	RIR databaseRIPE	669 99%	67
191.44.90.0/24	Valid	RIR databaseRIPE	669 99%	67

13.141.64.0/24

Invalid: origin

Other origin only

2 0%low visibility

13.141.35.0/24

Invalid: origin

Other origin only

1 0%low visibility

79.182.27.0/24

Invalid: origin

Other origin only

0 0%low visibility

201.4.72.0/24

Valid

RIR databaseRIPE

672 100%

31.57.12.0/24

Valid

RIR databaseRADB, RIPE

671 100%

48.103.142.0/24

Valid

RIR databaseRIPE

671 100%

77.216.4.0/24

Valid

RIR databaseRADB, RIPE

670 100%

130.78.11.0/24

Valid

RIR databaseRIPE

669 99%

191.44.90.0/24

Valid

RIR databaseRIPE

669 99%

AS-SET

AS215133'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 6 are in fix.csv.

ROA: origin3
Route object: none3

Change	Prefix or set	Detail	Full-table peers
ROA: origin	13.141.64.0/24	ROAs covering it name AS834, AS7029, not AS215133. If AS215133 should announce it, add a ROA for AS215133.	2 of 673
Route object: none	13.141.64.0/24	Route objects for it name AS834. Add a route object with origin AS215133 in the RIR database for the space.	2 of 673
ROA: origin	13.141.35.0/24	ROAs covering it name AS834, not AS215133. If AS215133 should announce it, add a ROA for AS215133.	1 of 673
Route object: none	13.141.35.0/24	Route objects for it name AS834. Add a route object with origin AS215133 in the RIR database for the space.	1 of 673
ROA: origin	79.182.27.0/24	ROAs covering it name AS137410, not AS215133. If AS215133 should announce it, add a ROA for AS215133.	0 of 673
Route object: none	79.182.27.0/24	Route objects for it name AS137410. Add a route object with origin AS215133 in the RIR database for the space.	0 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

13.141.64.0/24

ROAs covering it name AS834, AS7029, not AS215133. If AS215133 should announce it, add a ROA for AS215133.

2 of 673

Route object: none

13.141.64.0/24

Route objects for it name AS834. Add a route object with origin AS215133 in the RIR database for the space.

2 of 673

ROA: origin

13.141.35.0/24

ROAs covering it name AS834, not AS215133. If AS215133 should announce it, add a ROA for AS215133.

1 of 673

Route object: none

13.141.35.0/24

Route objects for it name AS834. Add a route object with origin AS215133 in the RIR database for the space.

1 of 673

ROA: origin

79.182.27.0/24

ROAs covering it name AS137410, not AS215133. If AS215133 should announce it, add a ROA for AS215133.

0 of 673

Route object: none

79.182.27.0/24

Route objects for it name AS137410. Add a route object with origin AS215133 in the RIR database for the space.

0 of 673

Route objects not announced

Every route object with origin AS215133 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.