bgpreport

Network · data from 2026-11-12

AS197256 RENEWINKLER-AS Rene Winkler

Registry name: RENEWINKLER-AS Rene Winkler, CZ · not in PeeringDB

7IPv4 routes 28.6% RPKI valid · 28.6% with a route object
0IPv6 routes
2RPKI invalid 2 origin · 0 maxLength
3No ROA 5 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS197256, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS197256, 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.
108.186.193.0/24 Invalid: origin Other origin only 2 0%low visibility 2
191.44.65.0/24 Invalid: origin None 1 0%low visibility 1
94.183.169.0/24 No ROA None 671 100% 67
151.242.238.0/24 No ROA None 671 100% 67
151.247.170.0/24 No ROA Other origin only 671 100% 67
177.3.199.0/24 Valid RIR databaseRIPE 673 100% 67
201.8.83.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS197256 isn't in PeeringDB, where networks name their 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 10 are in fix.csv.

  • ROA: origin2
  • ROA: none3
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: origin108.186.193.0/24ROAs covering it name AS834, not AS197256. If AS197256 should announce it, add a ROA for AS197256.2 of 673
Route object: none108.186.193.0/24Route objects for it name AS834. Add a route object with origin AS197256 in the RIR database for the space.2 of 673
ROA: origin191.44.65.0/24ROAs covering it name AS34346, not AS197256. If AS197256 should announce it, add a ROA for AS197256.1 of 673
Route object: none191.44.65.0/24No route object for it. Add a route object with origin AS197256 in the RIR database for the space.1 of 673
ROA: none94.183.169.0/24No ROA covers it. Add a ROA for AS197256, maxLength 24.671 of 673
Route object: none94.183.169.0/24No route object for it. Add a route object with origin AS197256 in the RIR database for the space.671 of 673
ROA: none151.242.238.0/24No ROA covers it. Add a ROA for AS197256, maxLength 24.671 of 673
Route object: none151.242.238.0/24No route object for it. Add a route object with origin AS197256 in the RIR database for the space.671 of 673
ROA: none151.247.170.0/24No ROA covers it. Add a ROA for AS197256, maxLength 24.671 of 673
Route object: none151.247.170.0/24Route objects for it name AS834. Add a route object with origin AS197256 in the RIR database for the space.671 of 673

Route objects not announced

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