Skip to main content
Unit

List Payments timeouts

Degraded Lasted 50m · started · Unit's page

Level
confirmed
Worst impact
Degraded
Components
Payments
Down Index
19of 100

What to do

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

    Anything that failed between 2023-11-26 15:48 UTC and 2023-11-26 16:38 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 5

  1. investigating

    We are currently investigating this issue.

    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. monitoring

    We are continuing to monitor for any further issues.

    provider

  5. 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-16c810e06f

Is Unit still down?

No, this incident was resolved 2023-11-26 16:38 UTC. For Unit's live state, see https://down.guide/unit.

How long did it last?

50m, from 2023-11-26 15:48 UTC to 2023-11-26 16:38 UTC, by the times Unit posted.

What was affected?

Unit named Payments.

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.