HubSpot is experiencing issues

Final update

Between 04:32 PM EDT (UTC -04:00) and 07:21 PM EDT (UTC -04:00), some customers in North America experienced issues with customer platform tools, marketing tools, sales tools. This was caused by a bad production configuration change. As of 07:21 PM EDT (UTC -04:00), our customer platform tools, marketing tools, sales 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.

1. Resolved · Oct 2, 23:22 UTC
   Between 04:32 PM EDT (UTC -04:00) and 07:21 PM EDT (UTC -04:00), some customers in North America experienced issues with customer platform tools, marketing tools, sales tools. This was caused by a bad production configuration change. As of 07:21 PM EDT (UTC -04:00), our customer platform tools, marketing tools, sales 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.
2. Monitoring · Oct 2, 23:03 UTC
   We've addressed the issue that caused customer platform tools, marketing tools, sales tools to be partially unavailable in North America since 04:32 PM EDT (UTC -04:00). We're monitoring performance closely to ensure the tools recover properly. The information on this page reflects our understanding of the incident and impact at the time of the update.
3. Identified · Oct 2, 22:28 UTC
   We estimate that we will restore service in the next half an hour. We are mitigating impact from a server impairment which we believe is caused by a bad production configuration change. We are reverting the change. We will be back with an update within 30 minutes. The information on this page reflects our understanding of the incident and impact at the time of the update.
4. Identified · Oct 2, 21:58 UTC
   We estimate that we will restore service in the next hour. We are mitigating impact from a server impairment which we believe is caused by a bad production configuration change. We are reverting the change. We will be back with an update within 30 minutes. The information on this page reflects our understanding of the incident and impact at the time of the update.
5. Identified · Oct 2, 21:44 UTC
   We estimate that we will restore service in the next several hours. We are mitigating impact from a server impairment which we believe is caused by a bad production configuration change. We are reverting the change. 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.
6. Identified · Oct 2, 21:30 UTC
   We estimate that we will restore service in the next several hours. We are mitigating impact from a server impairment which we believe is caused by a bad production configuration change. We are reverting the change. 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.