Skip to main content
Hex

Issues using 3.11 custom images

Partial outage Lasted 4h 21m · started · Hex's page

Level
confirmed
Worst impact
Partial outage
Components
Kernels
Down Index
35of 100

What to do

  • Check whether you use Hex Kernels. 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 4h 21m it lasted.

    Anything that failed between 2025-11-07 15:07 UTC and 2025-11-07 19:28 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 4

  1. investigating

    We are currently investigating an issue using 3.11 custom images. It is expected that projects using customer images are able to acquire a kernel, but are not able to query data sources.

    provider

  2. identified

    The issue has been identified and a fix is being implemented.

    provider

  3. identified

    We are continuing to work on a fix for this issue.

    provider

  4. 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-fb074caa62

Is Hex still down?

No, this incident was resolved 2025-11-07 19:28 UTC. For Hex's live state, see https://down.guide/hex.

How long did it last?

4h 21m, from 2025-11-07 15:07 UTC to 2025-11-07 19:28 UTC, by the times Hex posted.

What was affected?

Hex named Kernels.

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.