Skip to main content
Unit

Alloy API errors

Degraded Lasted 4h 38m · started · Unit's page

Level
confirmed
Worst impact
Degraded
Components
Onboarding
Down Index
23of 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 4h 38m it lasted.

    Anything that failed between 2025-10-20 21:06 UTC and 2025-10-21 01: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 2

  1. investigating

    We are having issues in our onboarding process due to elevated API errors with Alloy, caused by the ongoing AWS outage.

    provider

  2. resolved

    Alloy has confirmed that normal operations have been fully restored across all components. System latencies and performance metrics have returned to expected levels and no further API errors are observed.

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

Is Unit still down?

No, this incident was resolved 2025-10-21 01:44 UTC. For Unit's live state, see https://down.guide/unit.

How long did it last?

4h 38m, from 2025-10-20 21:06 UTC to 2025-10-21 01: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.