[Medium] Issues with Box Drive

What to do

• Check whether you use Box Box Drive. 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 32m it lasted.

  Anything that failed between 2026-05-22 08:46 UTC and 2026-05-22 09:18 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. investigatingMay 22, 2026, 8:46 AM UTC

   Our team is investigating an issue with Logins for Box Drive. Users attempting to log in to Box Drive may see errors or timeouts. Users encountering this issue can log in to the Box Web Application as a temporary workaround. We will provide additional information as it becomes available.

   provider

2. monitoringMay 22, 2026, 9:15 AM UTC

   We have resolved the issue impacting Box Drive. We are continuing to monitor to ensure no further impact is observed

   provider

3. resolvedMay 22, 2026, 9:18 AM UTC

   After further monitoring, this incident is now considered resolved. Box 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. postmortemMay 29, 2026, 12:41 AM UTC

   We recently addressed issues affecting Box Drive login and Single Sign-On \(SSO\) configuration. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future. Between 10:56 PM PDT on May 21, 2026 and 2:07 AM PDT on May 22, 2026, some users may have experienced difficulties while working in Box. During this time, enterprise customers with Intune Mobile Application Management \(MAM\) enabled experienced SSO login failures when attempting to access Box Drive, and administrators were unable to view, update, or manage SSO configurations in the Admin Console. The issue occurred as a result of an unintended configuration change where our primary, active identity provider administration console region was inadvertently flipped to passive mode. We were able to resolve the issue by restoring the primary administration console region back to active status, which immediately restored normal API and login flows. In addition, we are making updates to improve monitoring and alerting for related operational workflows to prevent similar issues from occurring in the future.  **Analysis** The active and standby regions were unintentionally reversed, causing the live production region to be switched into standby mode. As a result, the administrative API, which was used in for Intune MAM login flow, began rejecting requests for customers using Intune MAM-protected accounts and temporarily blocked certain SSO management actions in the Admin Console. End users affected by this saw login errors until the regions were restored to their correct state. We have since added safeguards to prevent unintended region switches and improved how our login flow handles this type of upstream failure. **Corrective Actions** Box has initiated the following corrective actions: * Add monitoring to catch certain configuration mismatches that could lead to unintended changes in service routing * Implement additional restrictions for administrative console region-flip 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

Corrections

None so far.

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