Past incidents Return to status page

All Systems Operational

About This Site

Welcome to HubSpot's home for real-time information on system status and security. Here you'll find live and historical data on system performance. If there are any interruptions in service, a note will be posted here.

CRM Operational
Marketing Tools Operational
Website Operational
Sales Tools Operational
Service Tools Operational
Chat & Automation Operational
Reports Operational
HubSpot APIs Operational
Integrations Operational
Mobile Operational
Developer Tools Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
May 15, 2026

No incidents reported today.

May 14, 2026

No incidents reported.

May 13, 2026

No incidents reported.

May 12, 2026
Resolved - Between 02:47 PM (UTC +01:00) and 03:15 PM (UTC +01:00), some customers in all affected regions experienced issues with all impaired tools. This was caused by a database impairment. As of 03:15 PM (UTC +01: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.

May 12, 10:55 EDT
Investigating - We're investigating reports that HubSpot may be unavailable for some users. We'll update this page when we have more information.
May 12, 09:57 EDT
May 11, 2026

No incidents reported.

May 10, 2026

No incidents reported.

May 9, 2026

No incidents reported.

May 8, 2026

No incidents reported.

May 7, 2026
Resolved - Between 05:23 PM  (UTC -07:00) and 07:56 PM  (UTC -07:00), HubSpot experienced degradation in portals in the U.S. . This was related to an AWS outage. HubSpot is now working properly and the incident has been 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

May 7, 23:14 EDT
Update - We are experiencing degradation in portals in the U.S. which is related to AWS outage. We are working with AWS on the full resolution.

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.

May 7, 22:07 EDT
Identified - We are experiencing degradation in portals in the U.S. which we believe is related to AWS outage.

We are working with AWS to resolve the issue. 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.

May 7, 21:36 EDT
May 6, 2026

No incidents reported.

May 5, 2026

No incidents reported.

May 4, 2026

No incidents reported.

May 3, 2026

No incidents reported.

May 2, 2026
Resolved - HubSpot has continued to monitor the fix and believe we have addressed the underlying issue. Some messages deployed before May 1, 5 pm EDT may still experience delayed deliveries or failures over the next ~48 hours as retries and queues fully clear.
May 2, 15:31 EDT
Update - In April, some customers may have experienced intermittent DMARC failures on messages to Microsoft-hosted inboxes. Impact was most visible for senders with a DMARC policy of p=reject or p=quarantine. The root cause was related to how certain email headers were being handled.

We have implemented a fix and will continue to monitor closely. While there may still be some residual impact to messages with elongated headers and as outstanding retries and queue delays clear over the next ~72 hours, we expect impact to remain limited.

May 1, 12:34 EDT
Monitoring - In April, some customers may have experienced intermittent DMARC failures on messages to Microsoft-hosted inboxes. Impact was most visible for senders with a DMARC policy of p=reject or p=quarantine. The root cause was related to how certain email headers were being handled.

We have implemented a fix and will continue to monitor closely. While there may still be some residual impact to messages as outstanding retries and queue delays clear over the next ~72 hours, we expect impact to remain limited.

May 1, 11:52 EDT
May 1, 2026