Skip to content

Incident detail

[Minor] Issue affecting Logins

[Minor] Issue affecting Logins

Resolved incidentMinor0 affected services

Timeline window

to

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. Investigating

    Our team is investigating reports of issues affecting Logins. Some customers may be experiencing errors or delays when attempting to log in to their Box accounts. We are working to identify the cause and will provide another update as soon as more information is available.

  2. Identified

    We have identified the cause of the issue. Our team is now actively working on implementing a solution.

  3. Monitoring

    A fix has been implemented to address the issue, and we are observing recovery. Customers should now be seeing improvement when attempting to log in. Our team will continue to monitor the service to ensure full stability is restored. We will provide another update once the incident is resolved or if the status changes.

  4. Monitoring

    After a period of monitoring, we have confirmed that the issues affecting Login are now resolved. Service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

  5. Resolved

    This incident has been resolved.

  6. Resolved

    We recently addressed an issue affecting logins to Box. We would like to take the opportunity to further explain this issue and the steps we have taken to keep it from happening in the future. Between **4:46 PM PDT** and **5:32 PM PDT** on **March 9, 2026**, some users may have experienced difficulties logging in to Box leading to disruptions when using some Box features. This issue occurred when a service involved in the login process did not have sufficient resources to handle an uneven spike in traffic, which caused a portion of login-related requests to time out. We resolved this by increasing resources for the affected service and expanding its capacity. We also took additional steps to reduce the likelihood that this type of issue could affect the login experience in the future. ## **Analysis** The incident surfaced opportunities to further refine how we size and distribute capacity across services that support login-related traffic. It also underscored the value of strengthening earlier detection of traffic imbalances and simplifying dependencies within critical login flows. ## **Corrective Actions** Box has initiated the following corrective actions: * **Strengthen resource allocation and scaling:** We are tuning resource allocation and scaling behavior so services can better absorb unusual traffic patterns without degradation. * **Improve traffic distribution and monitoring:** We are refining how traffic is distributed across service instances and strengthening monitoring so we can identify and address unhealthy capacity patterns sooner. * **Reduce login path dependencies:** We are simplifying the login flow so fewer background checks are required for most users, reducing the potential impact of issues in supporting services. ‌ 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