- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 12of 100
What to do
Check whether you use Box in us. 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 2026-08-24 17:30 UTC and 2026-08-24 17:30 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 2
- resolved
From approximately 10:28 AM to 10:35 AM US Pacific time, we observed an issue intermittently impacting some Logins and the Files page view. Our systems automatically detected and corrected the underlying issue. There is no current impact and no further updates will be provided here. If you continue to experience any issues, please contact Box Support at https://support.box.com.
provider
- postmortem
Between 3:44 PM and 4:27 PM PDT on August 19, 2026 and 10:28 AM and 11:21 AM PDT on August 24, 2026, some users may have experienced intermittent errors with some Box features, including Logins, Uploads, Downloads, and Box Sign. The issues occurred after a rapid surge of external Box client connections overwhelmed front-end capacity in the affected region, which caused an increase in server-side error rates and prevented some requests from reaching our back-end services. We restored service by working with our cloud provider and applying operational mitigations until front-end error rates returned to normal and user requests succeeded again. # Analysis This incident highlighted opportunities to improve our detection and correlation of frontend/load balancer health signals with our application telemetry and to strengthen joint monitoring and mitigation processes with our cloud provider during large-scale client connection events. It also underscored the importance of clearer detection thresholds and runbook steps for frontend degradations, so we can escalate and remediate faster without over or under communicating impact to customers. # Corrective Actions Box has initiated the following corrective actions: * Improving monitoring and observability for large-scale client connection events and working with our cloud provider on coordinated mitigation strategies. * Coordinating with our cloud provider to ensure connection rates are within expected thresholds. 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-b3a05ec8eb
Is Box still down?
No, this incident was resolved 2026-08-24 17:30 UTC. For Box's live state, see https://down.guide/box.
How long did it last?
0m, from 2026-08-24 17:30 UTC to 2026-08-24 17:30 UTC, by the times Box posted.
What was affected?
Box named in us.
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.