Skip to main content
Box

[Critical] Issues with Box Sign

Major outage Lasted 4h 5m · started · Box's page

Level
confirmed
Worst impact
Major outage
Components
Box Sign
Down Index
43of 100

What to do

  • Check whether you use Box Box 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 4h 5m it lasted.

    Anything that failed between 2026-04-03 04:04 UTC and 2026-04-03 08:09 UTC may need a replay.
  • Subscribe to Box's feed to hear about the next one first. RSS feed

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

Updates from Box 4

  1. investigating

    We are investigating an ongoing issue affecting Box Sign. We will provide more information as soon as it is available.

    provider

  2. identified

    Our team has identified the underlying cause of this issue and is working to take remediating steps. We will provide additional updates as they become available.

    provider

  3. resolved

    After further monitoring, this incident is now considered resolved. Box Sign services have been restored to full functionality. Please contact Box Support at https://support.box.com/ if you continue to experience any issues.

    provider

  4. postmortem

    On April 2, 2026 between 8:19 PM PDT and 11:56 PM PDT, some users may have experienced difficulties while working in Box. During this time, Box Sign users might have experienced errors while creating new signature requests, accessing existing signature requests, or attempting ~~been unable~~ to access the service. The issue occurred as a result of an erroneous change made by a third-party infrastructure provider. We were able to resolve the issue by escalating it to the provider. In addition, we are working to improve the reliability of the Box Sign service by enhancing our disaster recovery processes to prevent similar issues from occurring in the future.  ‌ We are conducting a full engineering postmortem and our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem. We are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.  Sincerely, The Box Team

    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-50311c4376

Is Box still down?

No, this incident was resolved 2026-04-03 08:09 UTC. For Box's live state, see https://down.guide/box.

How long did it last?

4h 5m, from 2026-04-03 04:04 UTC to 2026-04-03 08:09 UTC, by the times Box posted.

What was affected?

Box named Box Sign.

What caused it?

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

Where does this come from?

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