HubSpot is down: what we know so far
This page is live and updates as StatusBird re-checks HubSpot, every 2 minutes. First non-operational reading 16:33 UTC on October 23, 2026.
StatusBird recorded HubSpot as non-operational from 16:33 UTC on 23 October 2026. We poll every two minutes, and 30 readings in a row came back non-operational, which is one hour of disruption. The worst state we observed was major. HubSpot had already posted an incident at 16:07 UTC, titled "Some HubSpot tools may be unavailable for some users". The issue was still running when this was written.
Incident at a glance
| Service | HubSpot |
|---|---|
| Date | October 23, 2026 |
| StatusBird first saw it | 16:33 UTC |
| Vendor posted an incident | 16:07 UTC |
| Recovery observed | Not yet |
| Duration | 2 hours 21 minutes and counting |
| Worst status observed | major |
| Non-operational readings | 71 |
| Down in the same poll cycle | Vercel |
All times UTC. StatusBird polls HubSpot every 2 minutes from its own infrastructure, so the true start and end sit within 2 minutes of the times above.
Was HubSpot down on October 23, 2026?
Yes. StatusBird recorded HubSpot as major from 16:33 UTC, and it was still non-operational 2 hours 21 minutes later at the most recent reading. 71 consecutive checks came back non-operational.
Marketing automation is partially down.
What caused the HubSpot outage?
The cause is not known. HubSpot has published no root cause statement that StatusBird can read, so we cannot tell you why the tools failed. The only vendor wording available is the incident title posted at 16:07 UTC, which says some HubSpot tools may be unavailable for some users. We will not guess at what sat behind it. One other service we monitor, Vercel, went down in the same poll cycle, but we have no information linking the two.
HubSpot published an incident titled "Some HubSpot tools may be unavailable for some users" at 16:07 UTC. A root cause has not yet been published by the vendor, so nothing on this page attributes one.
How long was HubSpot down?
2 hours 21 minutes so far, measured from the first non-operational reading at 16:33 UTC to the most recent reading, which was still non-operational. StatusBird counts a service down from the first reading it fails, not from the moment the vendor admits it, which is why this number can be larger than the one on the vendor's own incident report.
Timeline, in UTC
| Time (UTC) | Event |
|---|---|
| 16:07 UTC | The vendor posts an incident on its own status page |
| 16:33 UTC | StatusBird records its first non-operational reading |
| 16:36 UTC | A second consecutive non-operational reading confirms the outage, alerts go out and this page is published |
| 18:54 UTC | Still non-operational at the last reading |
Who and what was affected
This hits stores that run marketing automation through HubSpot, and it hits it partially rather than completely, so some tools may work while others do not. Expect trouble with automated email sequences, abandoned basket follow-ups, form submissions feeding into lists, and contact records updating after an order. Sales and support staff who look up a customer in HubSpot before replying may see stale data or no data at all.
Vercel went non-operational in the same poll cycle, so a store seeing several things break at once was not seeing several separate problems.
How StatusBird detected it
StatusBird recorded its first non-operational reading for HubSpot at 16:33 UTC, and HubSpot's own status page confirms the incident, posted at 16:07 UTC. StatusBird polls every 2 minutes from its own infrastructure, so these are two independent records of the same window.
Method: StatusBird reads HubSpot's published status endpoint every 2 minutes and records every reading. Availability figures count major and critical only. The full method is at statusbird.io/methodology.
Lessons for merchants
- Check the vendor status page as well as your own dashboards. HubSpot posted its incident at 16:07 UTC, 26 minutes before our first non-operational reading.
- Keep a record of which marketing automations are revenue critical, so you know within minutes which ones to pause and which can wait.
- Store order confirmation and transactional email on a path that does not depend on your marketing platform.
- Hold a manual list of the day's abandoned baskets and pending follow-ups, so you can send them once the platform returns.
The longer version, with the checks specific to this service, is in the HubSpot outage playbook.
Frequently asked questions
Was HubSpot down on October 23, 2026?
Yes. StatusBird recorded HubSpot as major from 16:33 UTC on October 23, 2026. The incident was still running 2 hours 21 minutes later when this page last updated.
How long was HubSpot down?
2 hours 21 minutes, measured from the first non-operational reading at 16:33 UTC to the most recent reading, which was still non-operational. Readings are taken every 2 minutes, so the true start and end sit within 2 minutes of those times.
What caused the HubSpot outage?
HubSpot published an incident titled "Some HubSpot tools may be unavailable for some users" at 16:07 UTC. A root cause has not yet been published by the vendor, so nothing on this page attributes one.
How was this HubSpot outage detected?
StatusBird recorded its first non-operational reading for HubSpot at 16:33 UTC, and HubSpot's own status page confirms the incident, posted at 16:07 UTC. StatusBird polls every 2 minutes from its own infrastructure, so these are two independent records of the same window.
Was my store affected?
If your store calls HubSpot during checkout or fulfillment, the requests to check are the ones made between 16:33 UTC and now on October 23, 2026. Marketing automation is partially down.
Monitor HubSpot with StatusBird
This page exists because StatusBird was already watching. It checks HubSpot and the rest of the stack an online store runs on every 2 minutes and sends an SMS, email, Slack, Teams or Discord alert the moment a reading goes non-operational, which on this incident was 16:33 UTC.
Start monitoring free Live HubSpot status All HubSpot outages