Skip to main content
Hex

Upstream Snowflake Incident

Degraded Lasted 3h 27m · started · Hex's page

Level
confirmed
Worst impact
Degraded
Down Index
20of 100

What to do

  • Check whether your product depends on Hex. 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 3h 27m it lasted.

    Anything that failed between 2026-08-03 15:23 UTC and 2026-08-03 18:50 UTC may need a replay.
  • Subscribe to Hex's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=hex works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Hex 2

  1. investigating

    Snowflake customers should be aware of an ongoing Snowflake incident that may impact your experience in Hex. Follow Snowflake's status page for updates: https://status.snowflake.com/incidents/xfv4kdj30rcb

    provider

  2. resolved

    This incident has been resolved.

    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-cfb1a7ad60

Is Hex still down?

No, this incident was resolved 2026-08-03 18:50 UTC. For Hex's live state, see https://down.guide/hex.

How long did it last?

3h 27m, from 2026-08-03 15:23 UTC to 2026-08-03 18:50 UTC, by the times Hex posted.

What caused it?

Hex hasn't published a root cause. If it does, it shows here.

Where does this come from?

Hex's official status page, https://status.hex.tech, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.