Skip to main content
Unit

Sandbox Timeouts

Degraded Lasted 3h 47m · started · Unit's page

Level
confirmed
Worst impact
Degraded
Components
Onboarding
Down Index
22of 100

What to do

  • Check whether you use Unit Onboarding. 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 47m it lasted.

    Anything that failed between 2024-11-15 18:57 UTC and 2024-11-15 22:44 UTC may need a replay.
  • Subscribe to Unit's feed to hear about the next one first. RSS feed

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

Updates from Unit 4

  1. investigating

    We are currently investigating an issue causing some requests to timeout.

    provider

  2. identified

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

    provider

  3. monitoring

    A fix has been implemented and we are monitoring the results.

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

Is Unit still down?

No, this incident was resolved 2024-11-15 22:44 UTC. For Unit's live state, see https://down.guide/unit.

How long did it last?

3h 47m, from 2024-11-15 18:57 UTC to 2024-11-15 22:44 UTC, by the times Unit posted.

What was affected?

Unit named Onboarding.

What caused it?

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

Where does this come from?

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