bgpreport

Network · data from 2026-11-12

AS199723 Strzyzowski.Net

Registry name: STRZYZOWSKI-NET Michal Gomolka trading as Strzyzowski.Net Spolka Komandytowa, PL · PeeringDB

23IPv4 routes 95.7% RPKI valid · 95.7% with a route object
0IPv6 routes
1RPKI invalid 0 origin · 1 maxLength
0No ROA 1 with no route object for this origin
15Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS199723, seen from no peer

Announced routes

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

185.41.128.0/32 Invalid: maxLength Nonecovered by 185.41.128.0/24 2 0%low visibility 6
45.157.12.0/22 Valid RIR databaseRIPE 671 100% 68
185.41.128.0/22 Valid RIR databaseRIPE 671 100% 68
185.252.180.0/22 Valid RIR databaseRIPE 671 100% 68
193.160.33.0/24 Valid RIR databaseRIPE 671 100% 68
45.157.12.0/23 Valid RIR databaseRIPE 116 17% 40
45.157.14.0/23 Valid RIR databaseRIPE 116 17% 40
185.41.128.0/23 Valid RIR databaseRIPE 116 17% 40
185.41.130.0/23 Valid RIR databaseRIPE 116 17% 40
45.157.12.0/24 Valid RIR databaseRIPE 22 3%low visibility 23
45.157.13.0/24 Valid RIR databaseRIPE 22 3%low visibility 23
45.157.14.0/24 Valid RIR databaseRIPE 22 3%low visibility 23
45.157.15.0/24 Valid RIR databaseRIPE 22 3%low visibility 23
185.41.128.0/24 Valid RIR databaseRIPE 22 3%low visibility 23
185.41.129.0/24 Valid RIR databaseRIPE 22 3%low visibility 23
185.41.130.0/24 Valid RIR databaseRIPE 22 3%low visibility 23
185.41.131.0/24 Valid RIR databaseRIPE 22 3%low visibility 23
185.252.180.0/23 Valid RIR databaseRIPE 22 3%low visibility 23
185.252.180.0/24 Valid RIR databaseRIPE 22 3%low visibility 23
185.252.181.0/24 Valid RIR databaseRIPE 22 3%low visibility 23
185.252.182.0/23 Valid RIR databaseRIPE 22 3%low visibility 23
185.252.182.0/24 Valid RIR databaseRIPE 22 3%low visibility 23
185.252.183.0/24 Valid RIR databaseRIPE 22 3%low visibility 23

AS-SET

PeeringDB's irr_as_set for AS199723: AS199723. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS199723 isn't in the set, or no route object for AS199723 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS199723 in itNot covered
AS199723 A single AS number, not a set: AS199723 (this network), 26 route objects.

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: maxLength1
  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: maxLength185.41.128.0/32ROA 185.41.128.0/22 AS199723 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.41.128.0/32.2 of 673
Route object: none185.41.128.0/32No route object for it. A route object for 185.41.128.0/24 with origin AS199723 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS199723 in the RIR database for the space.2 of 673

Route objects not announced

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

2a01:59a0::/29RIPEValid
2a05:8580::/29RIPEValid
2a0f:3880::/29RIPEValid
2a10:f781:10:3beb::/64RIPENo 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.