← Back to HubSpot's live status
We started measuring HubSpot on August 20, 2026, which is 15 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what HubSpot's own status page declared. Below it, any public chatter we saw about HubSpot and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what HubSpot's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about HubSpot in the last 24 hours, which is not evidence that nothing is wrong.
HubSpot's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is HubSpot's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention HubSpot next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Availability by region
Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
03
Monthly summary
Tracking HubSpot since Aug 20, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.
Uptime here is the share of each month in which our probes had no outage open for HubSpot: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and HubSpot's own status page contribute nothing to these figures.
04
Our incident log
Every outage our own probes detected for HubSpot in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: HubSpot's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.
No outages detected for HubSpot since we started measuring it on August 20, 2026. We show nothing from before that date.
Their declared record
HubSpot's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.
Some Workflow actions may currently be delayed.All systems operational
Aug 21, 2026, 9:57 AM UTC to Aug 21, 2026, 12:27 PM UTC (2h 30m)resolved
their latest update (Aug 21, 2026, 12:27 PM UTC): Between 08:45 AM GMT+1 (UTC +01:00) and 02:30 PM GMT+1 (UTC +01:00), some customers in North America experienced issues with workflow actions. This was caused by a data integrity issue. As of 02:30 PM GMT+1 (UTC +01:00), workflow actions are working as expected and the incident i…
HubSpot is experiencing issuesAll systems operational
Aug 13, 2026, 7:56 PM UTC to Aug 13, 2026, 10:10 PM UTC (2h 14m)resolved
their latest update (Aug 13, 2026, 10:10 PM UTC): Between 02:05 PM EDT (UTC -04:00) and 05:47 PM EDT (UTC -04:00), some customers experienced issues with marketing tools related to Form Submissions that trigger Workflow enrollment.
This was caused by resource exhaustion. As of 05:47 PM EDT (UTC -04:00), our marketing tools are …
Some HubSpot tools may be unavailable for some usersAll systems operational
Aug 11, 2026, 7:31 PM UTC to Aug 11, 2026, 7:45 PM UTC (14 min)resolved
their latest update (Aug 11, 2026, 7:45 PM UTC): Between 03:16 PM EDT (UTC -04:00) and 03:25 PM EDT (UTC -04:00), many customers in all affected regions experienced issues accessing the CRM Record page. This was caused by a server impairment from a configuration update. As of 03:25 PM EDT (UTC -04:00), our CRM Record page are w…
Event ingestion and retrieval delays for some North America customersAll systems operational
Jul 28, 2026, 5:41 PM UTC to Jul 28, 2026, 7:40 PM UTC (2h)resolved
their latest update (Jul 28, 2026, 7:40 PM UTC): Between 07:41 AM PDT (UTC -07:00) and 12:37 PM PDT (UTC -07:00), some customers in North America experienced event ingestion and retrieval delays affecting Segments, Workflows, Timeline Events, and Report processing. This was caused by an underlying database infrastructure issue …
Some HubSpot tools may be unavailable for some usersAll systems operational
Jul 23, 2026, 4:42 PM UTC to Jul 23, 2026, 5:26 PM UTC (44 min)resolved
their latest update (Jul 23, 2026, 5:26 PM UTC): Between 11:17 AM EDT (UTC -04:00) and 12:14 PM EDT (UTC -04:00), some customers in all affected regions experienced issues with service tools. This was caused by a data fetching issue. As of 12:14 PM EDT (UTC -04:00), our service tools are working properly and the incident has be…
HubSpot is experiencing issuesAll systems operational
Jul 22, 2026, 7:47 AM UTC to Jul 22, 2026, 11:13 AM UTC (3h 26m)resolved
their latest update (Jul 22, 2026, 11:13 AM UTC): Between 08:21 AM GMT+1 (UTC +01:00) and 11:30 AM GMT+1 (UTC +01:00), many customers in Europe experienced issues with customer platform tools. This was caused by a server impairment. As of 11:30 AM GMT+1 (UTC +01:00), our customer platform tools are working properly and the incid…
Performance Degradation (Latin America Region)All systems operational
Jul 14, 2026, 4:42 PM UTC to Jul 14, 2026, 4:42 PM UTC (0 min)resolved
their latest update (Jul 14, 2026, 4:42 PM UTC): We have resolved a performance issue that was causing elevated latency for some users in Latin American regions between July 3rd and July 14th, 2026.
Our infrastructure team identified the root cause and the network routing configuration has been corrected. Traffic has been rest…
Content previews are unavailable for some customers in North AmericaAll systems operational
Jul 14, 2026, 4:31 PM UTC to Jul 21, 2026, 5:50 PM UTC (7d 1h)resolved
their latest update (Jul 21, 2026, 5:50 PM UTC): Some customers in North America experienced issues with Content previews. This was caused by hubspotpreview-na2.com being blocked by some internet providers. As of 06:40 PM GMT+1 (UTC +01:00), our preview domain is loading correctly and the incident has been fully resolved.
HubS…
Some HubSpot tools may be unavailable for some usersAll systems operational
Jun 23, 2026, 8:17 PM UTC to Jun 23, 2026, 8:55 PM UTC (38 min)resolved
their latest update (Jun 23, 2026, 8:55 PM UTC): Between 03:48 PM (UTC -04:00) and 04:46 PM (UTC -04:00), many customers in all regions experienced issues with the Files tool. This was caused by a configuration issue. As of 04:46 PM (UTC -04:00), our Files tool is working properly and the incident has been fully resolved.
H…
Some HubSpot tools may be unavailable for some usersAll systems operational
Jun 22, 2026, 2:22 PM UTC to Jun 22, 2026, 2:48 PM UTC (26 min)resolved
their latest update (Jun 22, 2026, 2:48 PM UTC): Between 09:34 AM (UTC -04:00) and 10:25 AM (UTC -04:00), some customers in North America experienced issues with hubspot APIs. This was caused by a load balancer impairment. As of 10:25 AM (UTC -04:00), our hubspot APIs are working properly and the incident has been fully reso…
Showing the 10 most recent of 51 incidents HubSpot has declared in the history we hold.
These entries are HubSpot's own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
The scorecard
How HubSpot's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.
We started recording HubSpot's own status page on August 20, 2026, 13 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.
We have not measured an outage for HubSpot since we started recording their status page, so there is nothing to compare. That is a short measurement window, not a track record.
HubSpot decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If HubSpot believes a figure here is wrong, we publish corrections as prominently as the original.
Full detail on what a probe does and does not prove is in the methodology page.