HubSpot incident

HubSpot may be unavailable for some users

Notice Resolved View vendor source →

HubSpot experienced a notice incident on April 9, 2026, lasting 31m. The incident has been resolved; the full update timeline is below.

Started
Apr 09, 2026, 03:48 PM UTC
Resolved
Apr 09, 2026, 04:20 PM UTC
Duration
31m
Detected by Pingoru
Apr 09, 2026, 03:48 PM UTC

Update timeline

  1. investigating Apr 09, 2026, 03:48 PM UTC

    We're investigating reports that HubSpot may be unavailable for some users. We'll update this page when we have more information.

  2. investigating Apr 09, 2026, 04:00 PM UTC

    commerce tools, content tools, customer platform tools, hubspot APIs, marketing tools, operations tools, sales tools, service tools have been unavailable in North America since 11:44 AM (UTC -04:00). We are investigating the cause and will update this page when we have more information. We will be back with an update within 15 minutes. The information on this page reflects our understanding of the incident and impact at the time of the update.

  3. identified Apr 09, 2026, 04:15 PM UTC

    We estimate that we will restore service in the next half an hour. We are mitigating impact from a database impairment which we believe is caused by a bad production configuration change. We are failing over to a healthy node. We will be back with an update within 15 minutes. The information on this page reflects our understanding of the incident and impact at the time of the update.

  4. resolved Apr 09, 2026, 04:20 PM UTC

    Between 11:44 AM (UTC -04:00) and 12:18 PM (UTC -04:00), all customers in North America experienced issues with all impaired tools. This was caused by a database impairment. As of 12:18 PM (UTC -04:00), our all impaired tools are working properly and the incident has been fully resolved. HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability. The information on this page reflects our understanding of the incident and impact at the time of the update.