[Medium] Issue with Multiple Box Services

What to do

• Check whether you use Box Login/SSO, Authentication (OAuth 2.0 / JWT), Box Edit / Tools, 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 27m it lasted.

  Anything that failed between 2026-06-11 00:34 UTC and 2026-06-11 02:01 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. identifiedJun 11, 2026, 12:34 AM UTC

   Our team is investigating an issue with Box API authentication and 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

2. monitoringJun 11, 2026, 1:41 AM UTC

   Our team has taken steps to remediate this issue and is seeing improvement. We are continuing to monitor for any additional impact.

   provider

3. resolvedJun 11, 2026, 2:01 AM UTC

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

   provider

4. postmortemJun 24, 2026, 10:02 PM UTC

   We recently addressed issues affecting Box Public API. 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 5:10 PM PDT and 6:40 PM PDT on June 10, 2026, some users may have experienced difficulties accessing or working within Box. During this period, there was a noticeable degradation affecting Public API request processing. This issue occurred as a result of a recent software change to our authentication infrastructure in our ongoing effort to improve performance and stability of Public API service. We were able to resolve the issue by scaling up the service, correcting its resource allocation, and rolling back the change. In addition, we are working to improve our resource provisioning to prevent similar issues from occurring in the future. **Analysis** We recently began rolling out an update to our authentication infrastructure designed to improve performance and stability of Public API service. Following the gradual rollout, an increase in resource utilization during peak traffic led to unexpected resource utilization on our authentication infrastructure. As a result, those servers became unresponsive, preventing them from processing Public API requests. We were able to resolve the issue by temporarily scaling up and adjusting the resource allocations of the authentication service. **Corrective Actions** Box has initiated the following corrective actions: * Rebalancing the resource allocations of the authentication service to accommodate higher traffic volumes * Tuning server timeouts across Public API components to ensure consistent, predictable API response times * Establishing processes and automation to reduce time to mitigation 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.