Network · data from 2026-11-12

AS202228 Krzysztof Klaptocz NetService

Registry name: NETSERVICEPL-AS Krzysztof Jan Klaptocz trading as Netservice, PL · PeeringDB

17IPv4 routes 70.6% RPKI valid · 70.6% with a route object

0IPv6 routes

5RPKI invalid 0 origin · 5 maxLength

0No ROA 5 with no route object for this origin

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

3Route objects not announced registered with origin AS202228, seen from no peer

Announced routes

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


82.146.12.218/32	Invalid: maxLength	Nonecovered by 82.146.12.0/23	4 1%low visibility	11
91.90.164.27/32	Invalid: maxLength	Nonecovered by 91.90.164.0/23	4 1%low visibility	11
91.90.165.46/32	Invalid: maxLength	Nonecovered by 91.90.164.0/23	4 1%low visibility	11
91.202.195.6/32	Invalid: maxLength	Nonecovered by 91.202.192.0/22	4 1%low visibility	11
185.207.148.185/32	Invalid: maxLength	Nonecovered by 185.207.148.0/22	4 1%low visibility	11
79.108.200.0/21	Valid	RIR databaseRIPE	671 100%	68
82.146.12.0/23	Valid	RIR databaseRIPE	671 100%	68
89.35.234.0/24	Valid	RIR databaseRIPE	671 100%	68
89.35.250.0/23	Valid	RIR databaseRIPE	671 100%	68
91.90.164.0/23	Valid	RIR databaseRIPE	671 100%	68
91.189.136.0/21	Valid	RIR databaseRIPE	671 100%	68
91.202.192.0/22	Valid	RIR databaseRIPE	671 100%	68
94.240.16.0/22	Valid	RIR databaseRIPE	671 100%	68
94.240.52.0/22	Valid	RIR databaseRIPE	671 100%	68
185.193.116.0/22	Valid	RIR databaseRIPE	671 100%	68
185.207.148.0/22	Valid	RIR databaseRIPE	671 100%	68
193.46.220.0/24	Valid	RIR databaseRIPE	671 100%	68

82.146.12.218/32

Invalid: maxLength

Nonecovered by 82.146.12.0/23

4 1%low visibility

91.90.164.27/32

Invalid: maxLength

Nonecovered by 91.90.164.0/23

4 1%low visibility

91.90.165.46/32

Invalid: maxLength

Nonecovered by 91.90.164.0/23

4 1%low visibility

91.202.195.6/32

Invalid: maxLength

Nonecovered by 91.202.192.0/22

4 1%low visibility

185.207.148.185/32

Invalid: maxLength

Nonecovered by 185.207.148.0/22

4 1%low visibility

79.108.200.0/21

Valid

RIR databaseRIPE

671 100%

82.146.12.0/23

Valid

RIR databaseRIPE

671 100%

89.35.234.0/24

Valid

RIR databaseRIPE

671 100%

89.35.250.0/23

Valid

RIR databaseRIPE

671 100%

91.90.164.0/23

Valid

RIR databaseRIPE

671 100%

91.189.136.0/21

Valid

RIR databaseRIPE

671 100%

91.202.192.0/22

Valid

RIR databaseRIPE

671 100%

94.240.16.0/22

Valid

RIR databaseRIPE

671 100%

94.240.52.0/22

Valid

RIR databaseRIPE

671 100%

185.193.116.0/22

Valid

RIR databaseRIPE

671 100%

185.207.148.0/22

Valid

RIR databaseRIPE

671 100%

193.46.220.0/24

Valid

RIR databaseRIPE

671 100%

AS-SET

AS202228'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 13 are in fix.csv.

ROA: maxLength5
Route object: none5
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	82.146.12.218/32	ROA 82.146.12.0/23 AS202228 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 82.146.12.218/32.	4 of 673
Route object: none	82.146.12.218/32	No route object for it. A route object for 82.146.12.0/23 with origin AS202228 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202228 in the RIR database for the space.	4 of 673
ROA: maxLength	91.90.164.27/32	ROA 91.90.164.0/23 AS202228 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.90.164.27/32.	4 of 673
Route object: none	91.90.164.27/32	No route object for it. A route object for 91.90.164.0/23 with origin AS202228 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202228 in the RIR database for the space.	4 of 673
ROA: maxLength	91.90.165.46/32	ROA 91.90.164.0/23 AS202228 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.90.165.46/32.	4 of 673
Route object: none	91.90.165.46/32	No route object for it. A route object for 91.90.164.0/23 with origin AS202228 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202228 in the RIR database for the space.	4 of 673
ROA: maxLength	91.202.195.6/32	ROA 91.202.192.0/22 AS202228 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.202.195.6/32.	4 of 673
Route object: none	91.202.195.6/32	No route object for it. A route object for 91.202.192.0/22 with origin AS202228 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202228 in the RIR database for the space.	4 of 673
ROA: maxLength	185.207.148.185/32	ROA 185.207.148.0/22 AS202228 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 185.207.148.185/32.	4 of 673
Route object: none	185.207.148.185/32	No route object for it. A route object for 185.207.148.0/22 with origin AS202228 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202228 in the RIR database for the space.	4 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

82.146.12.218/32

ROA 82.146.12.0/23 AS202228 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 82.146.12.218/32.

4 of 673

Route object: none

82.146.12.218/32

No route object for it. A route object for 82.146.12.0/23 with origin AS202228 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202228 in the RIR database for the space.

4 of 673

ROA: maxLength

91.90.164.27/32

ROA 91.90.164.0/23 AS202228 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.90.164.27/32.

4 of 673

Route object: none

91.90.164.27/32

No route object for it. A route object for 91.90.164.0/23 with origin AS202228 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202228 in the RIR database for the space.

4 of 673

ROA: maxLength

91.90.165.46/32

ROA 91.90.164.0/23 AS202228 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.90.165.46/32.

4 of 673

Route object: none

91.90.165.46/32

4 of 673

ROA: maxLength

91.202.195.6/32

ROA 91.202.192.0/22 AS202228 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.202.195.6/32.

4 of 673

Route object: none

91.202.195.6/32

No route object for it. A route object for 91.202.192.0/22 with origin AS202228 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202228 in the RIR database for the space.

4 of 673

ROA: maxLength

185.207.148.185/32

ROA 185.207.148.0/22 AS202228 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 185.207.148.185/32.

4 of 673

Route object: none

185.207.148.185/32

No route object for it. A route object for 185.207.148.0/22 with origin AS202228 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202228 in the RIR database for the space.

4 of 673

Route objects not announced

Route objects with origin AS202228 whose prefix no peer sees AS202228 announce. Many are kept on purpose (backup routes, space announced only in some places).


77.65.132.0/23	RIPE	Valid
77.65.200.0/22	RIPE	Valid
2a10:f781:10:92cf::/64	RIPE	No ROA

77.65.132.0/23

RIPE

Valid

77.65.200.0/22

RIPE

Valid

2a10:f781:10:92cf::/64

RIPE

No ROA

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.