- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-east-1
- Down Index
- 16of 100
What to do
Check whether you use Hightouch in us, us-east-1. 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 2025-02-06 14:55 UTC and 2025-02-06 03:00 UTC may need a replay.Subscribe to Hightouch's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=hightouch works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Hightouch 1
- resolved
From 10pm ET on Feb 5 to 7am ET on Feb 6, Cloudflare blocked requests to HubSpot from our us-east-1 region. During that period, customers in that region may have seen rejected rows or connection failures with "error code: 1006." The issue was resolved by HubSpot, and we're working with the HubSpot team to ensure it doesn't happen again. The issue was possibly related to other recent HubSpot and Cloudflare networking issues: https://status.hubspot.com/incidents/vbhbbgpcp150, https://www.cloudflarestatus.com/incidents/m90shgg0k4dd
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-bebdd361f1
Is Hightouch still down?
No, this incident was resolved 2025-02-06 03:00 UTC. For Hightouch's live state, see https://down.guide/hightouch.
How long did it last?
0m, from 2025-02-06 14:55 UTC to 2025-02-06 03:00 UTC, by the times Hightouch posted.
What was affected?
Hightouch named in us, us-east-1.
What caused it?
Hightouch hasn't published a root cause. If it does, it shows here.
Where does this come from?
Hightouch's official status page, https://status.hightouch.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.