HubSpot: Activity and Event Reads Impaired

What to do

Check whether you use HubSpot CRM, Sales Tools, Service Tools in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-04-08 20:51 UTC and 2026-04-08 20:51 UTC may need a replay.
Subscribe to HubSpot's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=hubspot works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

resolvedApr 8, 2026, 8:51 PM UTC
Between 04:35 PM (UTC -04:00) and 04:50 PM (UTC -04:00), some customers in North America experienced issues with event processing delays. This was caused by a server impairment. As of 04:50 PM (UTC -04:00), event processing 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.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is HubSpot still down?

No, this incident was resolved 2026-04-08 20:51 UTC. For HubSpot's live state, see https://down.guide/hubspot.

How long did it last?

0m, from 2026-04-08 20:51 UTC to 2026-04-08 20:51 UTC, by the times HubSpot posted.

What was affected?

HubSpot named CRM, Sales Tools, Service Tools in us.

What caused it?

HubSpot hasn't published a root cause. If it does, it shows here.

Where does this come from?

HubSpot's official status page, https://status.hubspot.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.