Skip to main content
Hightouch

Elevated rate of 401 errors for REST API

Degraded Lasted 1h 34m · started · Hightouch's page

Level
confirmed
Worst impact
Degraded
Components
Customer API
Down Index
19of 100

What to do

  • Check whether you use Hightouch Customer API. 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 1h 34m it lasted.

    Anything that failed between 2025-08-28 09:54 UTC and 2025-08-28 11:28 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 2

  1. investigating

    We are investigating an issue causing REST API calls to fail with 401 error codes for a subset of customers.

    provider

  2. resolved

    We have traced the issue back to a small number of API keys created by Hightouch users with invalid or expired Google auth. Affected users can reactivate their account (and associated API keys) by logging in to their workspace.

    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-5cbd7559e1

Is Hightouch still down?

No, this incident was resolved 2025-08-28 11:28 UTC. For Hightouch's live state, see https://down.guide/hightouch.

How long did it last?

1h 34m, from 2025-08-28 09:54 UTC to 2025-08-28 11:28 UTC, by the times Hightouch posted.

What was affected?

Hightouch named Customer API.

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.