Snowflake

Cloud data platform that enables organizations to store, process, and analyze large-scale data workloads across multiple clouds.

Primary category: software

Visit Snowflake

About this data

This page reflects public online discussion, collected and scored by automated systems and summarized using AI. It is not a statement of fact, not an audit, and not our own opinion of the product. Automated analysis can be incomplete or wrong, and scores carry the limitations described in our methodology. Companies can respond with their own perspective. See how this is calculated.

Updated June 22, 2026

Overall Pulse Score

Pulse Score

+16 over this period

A 0-100 index summarizing the tone of 336 relevant public mentions gathered from public online communities across 9 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.

Weekly Sentiment Trend

Pulse Score by week over the selected period. Each point is one complete week of mentions.

This week in public discussion

Snowflake discussion over the recent period carried a heavily negative tone, with bug reports and reliability complaints dominating the conversation by a wide margin across 276 mentions. Commenters raised specific frustrations around driver incompatibilities, connection failures via JDBC and Go drivers, and significant delays in usage data population. A smaller share of mentions praised certain features and integration capabilities, and several requests called for expanded support such as Snowflake as an external data source. Overall sentiment appeared largely critical, with reliability concerns drawing the most attention.

AI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.

Sentiment mix by week

How the tone of public discussion splits each week.

PositiveMixedNeutralNegative

Most-discussed praise

Strong features37

Good integrations31

Feature requests16

New releases12

Performance7

Most-discussed complaints

Bugs161

Reliability85

Missing features65

Lacking integrations46

Feature requests22

Themes across the selected period, with mention counts.

Sample public mentions

Showing 5 of 336 analyzed public mentions in this period, with links to the original source. We do not reproduce full threads.

“SNOW-3651566: QueryContext/Close can block far past the callers context deadline — post-cancellation cleanup uses an unbounded, uncancellable context.Background(). > 1. What version of GO driver are you using? github.com/snowflakedb/gosnowflake/v2 v2.0.0 2. What operating system ...”

githubJun 12, 2026

“dbt-snowflake==1.10.5 installs incompatible dbt-core 2.0.0-alpha.1 due to unbounded >=1.10.0rc0 constraint, causing hard errors on dbt run-operation. ### Is this a new bug? - [x] I believe this is a new bug - [x] I have searched the existing issues — closest match is #1992 (same ...”

githubJun 1, 2026

“Unexpected snowflake.log appearing in my home directory. ## System details: Positron and OS details: Version: Positron Version: 2026.06.0 build 211 Code - OSS Version: 1.111.0 Commit: d5f94f072b1083b8237930739cb6525c6e12e1da Date: 2026-05-28T01:04:13+02:00 Commit: 39.6.0 Date: 14...”

githubJun 4, 2026

“Error when connecting to Snowflake via JDBC. ### Description When trying to connect to Snowflake via the JDBC driver, I am getting the following error: JDBC driver encountered communication error. Message: Exception encountered for HTTP request: (server info redacted). Unknown ho...”

githubJun 1, 2026

“st.connection(conn_name, type='snowflake') doesn't use named connection.. ### Checklist - [x] I have searched the existing issues for similar issues. - [x] I added a very descriptive title to this issue. - [x] I have provided sufficient information below to help reproduce this is...”

githubMay 28, 2026

331+ more analyzed mentions, full history, and theme breakdowns are part of Pro.

Get Pro

Deeper analysis

Bug reports and reliability complaints dominated discussion by a wide margin over the four-week window.
Sentiment declined steadily from late April through early June before plateauing at a low level with no clear recovery.
Opinion was divided between commenters frustrated by unresolved integration and driver issues and those expressing genuine feature praise or optimistic feature requests.
A spike in mention volume in late May did not lift sentiment, pointing to that surge being driven largely by negative experiences.

Praise theme	Mentions
Strong features	37
Good integrations	31
Feature requests	16
New releases	12
Performance	7

Complaint theme	Mentions
Bugs	161
Reliability	85
Missing features	65
Lacking integrations	46
Feature requests	22

Public discussion around Snowflake over the past four weeks has been dominated by frustration, with bug reports accounting for the single largest cluster of mentions by a wide margin. Commenters raised issues spanning driver-level problems, dependency conflicts, and unexpected file system behavior, and several mentions pointed to integration breakdowns across tooling like dbt, JDBC, and the Go driver. The sheer volume of complaint-side themes relative to praise themes suggests that negative sentiment has been setting the tone for the overall conversation during this window.

The score trajectory tells a clear story of deterioration followed by stabilization at a low level. Discussion started the window in a noticeably more positive position in late April, then slid steadily through May before hitting a floor in early June. A brief uptick in late May coincided with a surge in mentions, but that higher volume did not translate into improved sentiment, suggesting the influx of conversation was itself complaint-driven. Scores in the most recent two weeks appear to have plateaued rather than recovered, reinforcing a picture of settled dissatisfaction rather than active crisis or rebound.

Reliability concerns drew substantial attention, with commenters describing delays, blocking behaviors, and context-handling failures that had practical consequences for their workflows. The mention of a usage-data delay tied to a backend data source change attracted particular frustration, as several commenters framed it as a financial visibility problem rather than a minor inconvenience.

Where opinion was more divided was around feature direction. A meaningful number of mentions expressed genuine praise for specific capabilities and integrations that were working well, and there were also enthusiastic feature requests suggesting commenters see potential worth advocating for. The tension between that forward-looking interest and the weight of unresolved bugs created a split tone, where a vocal subset of the discussion remained constructively engaged even as the broader sentiment stayed negative.

AI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.