Skip to main content
HubSpot

Performance Degradation (Latin America Region)

Degraded Lasted 0m · started · HubSpot's page

Level
confirmed
Worst impact
Degraded

What to do

  • Check whether your product depends on HubSpot. 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-07-14 16:42 UTC and 2026-07-14 16:42 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.

Updates from HubSpot 1

  1. resolved

    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 restored to the optimal path and performance has returned to expected levels. We sincerely apologize for the inconvenience and thank you for your patience.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-396d95fbac

Is HubSpot still down?

No, this incident was resolved 2026-07-14 16:42 UTC. For HubSpot's live state, see https://down.guide/hubspot.

How long did it last?

0m, from 2026-07-14 16:42 UTC to 2026-07-14 16:42 UTC, by the times HubSpot posted.

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.