HubSpot EU reporting dashboards restored after Snowflake outage on September 4
HubSpot restored EU reporting and dashboards on September 4, 2026 after a Snowflake outage blocked access to data hosted in Snowflake for the EU reporting service. The incident was narrow, but it touched a high-visibility part of the CRM stack: reports, dashboards, and analytics views that revenue teams use to monitor pipeline, campaigns, and performance.
HubSpot EU reporting outage was tied to Snowflake Data Cloud
HubSpot opened the incident at 4:24 a.m. EDT, saying its reporting service and dashboards were unable to access data hosted in Snowflake in the EU. The affected HubSpot component was Reports, which covers loading reports, dashboards, and analytics event processing in the company’s status taxonomy.
The company linked the issue directly to a Snowflake disruption, and the timeline in HubSpot’s September 4 incident feed shows Reports moving from operational to partial outage when the problem was identified. By 5:14 a.m. EDT, HubSpot had moved the incident to monitoring and said reporting and dashboards were functioning again. The incident was marked resolved at 5:44 a.m. EDT.
In practice, this means the core issue was not a HubSpot-wide CRM outage. The disruption was centered on reporting access for data hosted in Snowflake in the EU, so the most obvious user impact would have been dashboards that failed to load, delayed reporting visibility, or temporarily unavailable analytics views.
Snowflake AWS Europe Frankfurt incident explains the HubSpot dashboard disruption
The upstream Snowflake record gives more detail on the infrastructure layer behind the HubSpot issue. Snowflake listed incident INC20000199 as a resolved critical event on September 4, with affected components in AWS Europe Frankfurt, including databases, tables and views, applications, and developer tools.
Snowflake’s incident data, mirrored in the public Snowflake outage record, places the customer impact window from 7:00 UTC to 8:30 UTC. Snowflake moved to monitoring at 9:04 UTC after rolling back a configuration update, then resolved the incident at 10:10 UTC.
The preliminary cause is important because it was not described as customer-side misconfiguration or a HubSpot reporting build failure. Snowflake attributed the disruption to a configuration update affecting infrastructure components responsible for authorizing incoming network traffic, which caused those components to restrict traffic. That lines up with HubSpot’s narrower status note: HubSpot reporting could not reach the Snowflake-hosted data it depended on.
Keboola status note confirms broader Snowflake EU impact
The incident was not isolated to HubSpot. Keboola also reported on September 4 that Snowflake was experiencing an outage in its AWS Europe Frankfurt region, describing it as an upstream Snowflake failure that could cause jobs, transformations, workspaces, and dependent apps to fail or stall.
Keboola’s Snowflake-related status update said Snowflake acknowledged the incident at 7:34 UTC with an impact start time of 7:00 UTC, then later noted that Snowflake resolved the incident at 10:10 UTC after applying a fix. That external timeline supports HubSpot’s own explanation that the reporting issue came from the Snowflake side rather than a separate HubSpot application incident.
For HubSpot customers, the practical signal is that reporting reliability can depend on more than the HubSpot application layer. When reporting data sits in, or is accessed through, Snowflake-hosted infrastructure, an upstream warehouse incident can surface inside HubSpot as a dashboard problem even when CRM records, sales tools, service tools, APIs, and automation remain otherwise healthy.
HubSpot Reports returned to operational status before the Snowflake incident fully closed
One notable timing detail is that HubSpot restored its Reports component before Snowflake formally closed the upstream incident. HubSpot said dashboards were functioning again at 5:14 a.m. EDT, which is 9:14 UTC, shortly after Snowflake moved to monitoring at 9:04 UTC. HubSpot then closed its own incident at 9:44 UTC, while Snowflake marked the broader incident resolved at 10:10 UTC.
That gap is normal in SaaS incident handling. A downstream platform can recover once the specific service path it relies on is stable, even while the upstream provider continues broader validation. In this case, the immediate market and customer meaning is straightforward: HubSpot’s EU reporting issue lasted roughly 80 minutes from HubSpot’s first incident post to resolution, and the visible customer impact was confined to reporting and dashboards rather than the full CRM platform.
HubSpot reporting dependency matters for revenue operations teams
The September 4 outage is a reminder that reporting layers behave differently from transactional CRM workflows. Sales reps may still be able to work deals, marketers may still be able to manage assets, and support teams may still be able to handle tickets, while dashboards used by managers and executives temporarily lose access to fresh or queryable data.
That distinction matters because HubSpot has been positioning reporting and data access as a central part of its customer platform. HubSpot’s own reporting product messaging emphasizes dashboards that combine marketing, sales, revenue, and service data in one place, with Enterprise data connections extending into warehouses such as Snowflake, BigQuery, Redshift, and Databricks through HubSpot reporting and dashboard software.
For teams running morning pipeline reviews, campaign checks, or executive dashboards in the EU, the operational impact would have been timing rather than data strategy. The platform recovered quickly, but the incident shows how a short upstream warehouse outage can briefly interrupt the reporting layer that many teams treat as the live view of business performance.
Share With Others
Platinum
