bgpreport

Network · data from 2026-11-12

AS51164 Knowit Solutions Oy

Registry name: KNOWIT-FI Knowit Solutions Oy, FI · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51164, 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.
157.94.0.0/16 No ROA RIR databaseRIPE 673 100% 67
192.26.111.0/24 No ROA RIR databaseRIPE 671 100% 67
178.217.128.0/21 Valid RIR databaseRIPE 673 100% 67
185.93.48.0/22 Valid RIR databaseRIPE 671 100% 67
2001:67c:224::/48 Valid RIR databaseRIPE 636 100% 67
2a0b:8880::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS51164'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 2 are in fix.csv.

  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: none157.94.0.0/16No ROA covers it. Add a ROA for AS51164, maxLength 16.673 of 673
ROA: none192.26.111.0/24No ROA covers it. Add a ROA for AS51164, maxLength 24.671 of 673

Route objects not announced

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