Is HubSpot Down?

No — HubSpot is up

HubSpot's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 231 ms

Right now

The verdict is the worse of these two. How we decide

HubSpot's status page

status.hubspot.com · read 4 minutes ago · checked every 3 minutes

Operational

HubSpot's components, as its status page reports them
Component	Status
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

Open their status page

FlareWarden checks

hubspot.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 231 ms
Checked: 2 hours ago

By region

Amsterdam reachable, 313 ms
Dallas reachable, 136 ms
Paris reachable, 272 ms
San Jose reachable, 283 ms
Singapore reachable, 177 ms
Stockholm reachable, 181 ms
Sydney reachable, 177 ms
Toronto reachable, 312 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	39 ms	3 ms	9 ms	297 ms
Dallas	32 ms	1 ms	7 ms	125 ms
Paris	29 ms	3 ms	9 ms	264 ms
San Jose	57 ms	3 ms	12 ms	271 ms
Singapore	82 ms	1 ms	6 ms	169 ms
Stockholm	41 ms	1 ms	6 ms	174 ms
Sydney	7 ms	1 ms	8 ms	166 ms
Toronto	58 ms	1 ms	6 ms	301 ms

We check that hubspot.com loads, not every feature behind it. Test it yourself

History

Incidents HubSpot reported

Since Oct 22, 15 days · from status.hubspot.com

Incidents: 3
Major or critical: 0
Median to resolve: 1h 53m

HubSpot is experiencing issues
Unrated · Nov 2
lasted 22m
Some HubSpot tools may be unavailable for some users
Unrated · Oct 23
lasted 2h 47m
Update on PHP security vulnerability
Unrated · Oct 22
lasted 1h 53m

HubSpot website availability

Measured by FlareWarden · hubspot.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 268ms

Last 30 days

91-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of hubspot.com from multiple regions every 6 hours. HubSpot's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What HubSpot does

HubSpot is a CRM with marketing, sales and customer service tooling attached, including email campaigns, landing pages, forms and live chat. Its forms and chat widgets are embedded directly in customers' own websites, so a HubSpot outage can break parts of a site that is otherwise working perfectly well.

What an outage looks like

During a HubSpot outage the CRM fails to load, workflows and sequences do not fire, and scheduled emails are delayed. Embedded forms and chat widgets on your own site may fail to render or fail to submit, which looks to visitors like your site is broken rather than HubSpot. Reporting dashboards can show stale data.

What to do about it

Check status.hubspot.com, which reports the CRM, marketing tools and the API separately. If forms on your own site are failing, treat that as the urgent part: submissions made during an incident are usually not recoverable, unlike scheduled emails, which normally go out late rather than being dropped once service returns.

Is it down for everyone, or just you?

If this page says HubSpot is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

HubSpot outage FAQ

Are leads lost if HubSpot forms fail?

Submissions that never reached HubSpot are generally not recoverable, because nothing captured them. That is the most expensive part of a HubSpot incident for most teams. If lead capture matters, a fallback form that posts somewhere you control is worth having, even if it is only enabled during incidents.

Does a HubSpot outage break my website?

Only the embedded parts. Pages hosted elsewhere keep serving, but HubSpot forms, chat widgets and tracking scripts embedded in them can fail to load or submit. To a visitor that is indistinguishable from your site being broken, which is why it is worth knowing which of your pages depend on HubSpot before an incident.

Will scheduled emails still send after an outage?

Usually yes, late rather than never. Scheduled sends are normally queued and delivered once service returns, so the practical impact is timing rather than loss. Campaigns tied to a specific moment, like an event reminder, may still arrive too late to be useful even though they were technically delivered.

Do HubSpot workflows catch up on missed triggers?

Not reliably. Enrolments and actions that should have fired during an incident may be skipped rather than replayed, so contacts can end up stuck partway through a sequence. After a significant outage it is worth spot-checking recent enrolments rather than assuming the automation reconciled itself.

How we measure this

We request HubSpot's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where HubSpot publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of HubSpot itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when HubSpot goes down

We check HubSpot every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required