Partial Global Search Results for Some Customers

Final update

Between 10:30 AM EST (UTC -05:00) on Nov 5, 2025, and 8:32 AM EST (UTC -05:00) on Nov 6, 2025, some customers experienced issues with global search. This was caused by a database impairment. As of 9:32 AM EST (UTC -05:00) on Nov 6, 2025, our global search is 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 · Nov 7, 10:15 UTC
   Between 10:30 AM EST (UTC -05:00) on Nov 5, 2025, and 8:32 AM EST (UTC -05:00) on Nov 6, 2025, some customers experienced issues with global search. This was caused by a database impairment. As of 9:32 AM EST (UTC -05:00) on Nov 6, 2025, our global search is 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 · Nov 6, 16:19 UTC
   We have mitigated the issue that caused global search to return partial search results since 10:30 AM EST (UTC -05:00) on Nov 5, 2025. Global contact search is now operational again. Further object indices are continuing to recover. We are closely monitoring performance and search result completeness. If you still experience missing results while search indices are recovering, please use the dedicated search on each CRM object page as a temporary workaround. The information on this page reflects our understanding of the incident and impact at the time of the update.
3. Identified · Nov 6, 15:53 UTC
   We are working to fully restore the search service and expect recovery to complete within the next several hours. We are mitigating the impact of a database issue that we believe was caused by a recent production code change. We have reverted this change and are restoring the correct database state. Global contact search has been restored. We are monitoring the roll-out as we bring back all remaining object indices. In the meantime, please use the dedicated search on each CRM object page to find the records you need. We will be back with an update within 3 hours. The information on this page reflects our understanding of the incident and impact at the time of the update.
4. Identified · Nov 6, 14:56 UTC
   We are working to fully restore the search service and expect recovery to complete within the next several hours. We are mitigating the impact of a database issue that we believe was caused by a recent production code change. We have reverted this change and are restoring the correct database state. Global contact search has been restored. We are monitoring the roll-out as we bring back all remaining object indices. In the meantime, please use the dedicated search on each CRM object page to find the records you need. We will be back with an update within 1 hour. The information on this page reflects our understanding of the incident and impact at the time of the update.
5. Identified · Nov 6, 14:01 UTC
   We estimate that we will restore the full search service in the next several hours. We are mitigating the impact from a database impairment, which we believe is caused by a bad production code change. We are reverting the change and restoring the correct database state. The global contact search has been restored. We are monitoring the roll-out to restore all object indices. As a workaround, use the dedicated search functionality of the CRM object page. We will be back with an update within 1 hour. The information on this page reflects our understanding of the incident and impact at the time of the update.
6. Identified · Nov 6, 13:32 UTC
   We estimate that we will restore service in the next several hours. We are mitigating impact from a database impairment which we believe is caused by a bad production code change. We are reverting the change and restoring the correct database state. The global contact search has been restored. We are monitoring the roll-out to restore all object indices. 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.
7. Identified · Nov 6, 13:03 UTC
   We estimate that we will restore service in the next several hours. We are mitigating impact from a database impairment which we believe is caused by a bad production code change. We are reverting the change and restoring the correct database state. The global contact search should be partially restored in Europe. As a workaround, use the dedicated search functionality of the CRM object page. 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.
8. Identified · Nov 6, 12:32 UTC
   We estimate that we will restore service in the next several hours. We are mitigating the impact of a database impairment, which we believe is caused by a bad production code change. We are reverting the change. As a workaround, use the dedicated search functionality of the CRM object page. 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.
9. Identified · Nov 6, 12:03 UTC
   We estimate that we will restore service in the next hour. We are mitigating impact from a database impairment which we believe is caused by a bad production code change. We are reverting the change and restoring the correct database state. As a workaround, use the dedicated search functionality of the CRM object page. 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.
10. Identified · Nov 6, 11:49 UTC
    We estimate that we will restore service in the next hour. We are mitigating impact from a database impairment which we believe is caused by a bad production code change. We are reverting the change. We will be back with an update within 15 minutes. As a workaround, use the dedicated search functionality of the CRM object page. The information on this page reflects our understanding of the incident and impact at the time of the update.