[Medium] Issue with multiple Box Services

What to do

• Check whether you use Box Content API, Uploads/Downloads, Box Sign, 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 1h 29m it lasted.

  Anything that failed between 2026-10-20 02:19 UTC and 2026-10-20 03:47 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.

Root cause

The impact was caused by a focused traffic spike that resulted in increased latencies when accessing some data assets.

Category: Capacity

Updates from Box 5

1. investigatingOct 20, 2026, 2:19 AM UTC

   Our team is investigating an issue with the Public API and Box Sign. Users may see errors or timeouts when attempting to use the Public API or Box Sign. We will provide additional information as it becomes available.

   provider

2. investigatingOct 20, 2026, 2:33 AM UTC

   Our team is continuing to investigate an issue with the Public API, Box Sign, and Downloads. We will provide additional information as it becomes available.

   provider

3. identifiedOct 20, 2026, 3:11 AM UTC

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

   provider

4. resolvedOct 20, 2026, 3:47 AM UTC

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

   provider

5. postmortemOct 27, 2026, 9:28 PM UTC

   _Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed._ On October 19, 2026 between 6:44 PM and 8:32 PM PDT, some customers may have experienced degradation when interacting with our Public API, Downloads, and Box Sign. The impact was caused by a focused traffic spike that resulted in increased latencies when accessing some data assets. We mitigated the impact by enabling additional targeted caching to relieve the stress on our datastores. Performance of our services returned to normal levels by 8:32 PM PDT. 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. Sincerely, The Box Team

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.