- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Dropbox Sign. 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 0m it lasted.
Anything that failed between 2023-07-06 21:00 UTC and 2023-07-06 21:00 UTC may need a replay.Subscribe to Dropbox Sign's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=dropbox-sign works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Dropbox Sign 1
- resolved
From 15:00 to 16:30 UTC, certain GET endpoints were operating with high latency for some users. This issue is now mitigated.
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-2f4685ff80
Is Dropbox Sign still down?
No, this incident was resolved 2023-07-06 21:00 UTC. For Dropbox Sign's live state, see https://down.guide/dropbox-sign.
How long did it last?
0m, from 2023-07-06 21:00 UTC to 2023-07-06 21:00 UTC, by the times Dropbox Sign posted.
What caused it?
Dropbox Sign hasn't published a root cause. If it does, it shows here.
Where does this come from?
Dropbox Sign's official status page, https://status.hellosign.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.