[Medium] Issues with Box Hubs Shared Links
We recently addressed issues affecting Hubs shared-link access in Box. 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 August 27, 2026 at 11:18 PM PDT and August 28, 2026 at 2:48 AM PDT, some customers may have been unable to access Box Hubs using shared links. Other Box functionality, such as file and folder access, was not broadly affected. The issue occurred as a result of a recent code change in our ongoing effort to improve performance. We were able to resolve the issue by rolling back the change, and traffic returned to the previous behavior. # Analysis During a routine deployment, a configuration change intended exclusively for a pre-production environment was inadvertently applied to the production environment. The incident highlighted opportunities to strengthen deployment-time configuration validation and pre-deployment checks designed to catch environment-specific confi
The latest update from Box.
State
Resolved
Started
66 d ago
2026-08-28 08:20 UTC
Lasted
1 h 40 min
until 2026-08-28 10:00 UTC
Worst impact
Partial outage
Timeline
4 updatesInvestigating
1 h 24 min 84%
Identified
16 min 16%
Updates
Times in UTCAs posted by Box
We recently addressed issues affecting Hubs shared-link access in Box. 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 August 27, 2026 at 11:18 PM PDT and August 28, 2026 at 2:48 AM PDT, some customers may have been unable to access Box Hubs using shared links. Other Box functionality, such as file and folder access, was not broadly affected. The issue occurred as a result of a recent code change in our ongoing effort to improve performance. We were able to resolve the issue by rolling back the change, and traffic returned to the previous behavior. # Analysis During a routine deployment, a configuration change intended exclusively for a pre-production environment was inadvertently applied to the production environment. The incident highlighted opportunities to strengthen deployment-time configuration validation and pre-deployment checks designed to catch environment-specific confi
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.
Box continues remediation efforts to restore full functionality to Box Hubs access via Shared Link. The underlying cause of the issue has been identified and efforts are underway to restore stability.
We are investigating an ongoing issue affecting Box Hubs shared links. Users may face issues with accessing Box Hubs using Shared Links. We will provide more information as soon as it is available.
Affected components
1Box in the last 90 days
Full historyIncidents in 90 days
17
Days with an incident
19
Median duration
53 min
This incident
1.9× the median
Other Box incidents
All incidentsBox·[Medium] Issue with multiple Box Services
_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
Box·[Major] Issue with Box Drive
We recently addressed issues affecting Events and Box Drive. We would like to take the opportunity to further explain these issues and the steps we have taken to prevent recurrence. Between October 14, 2026 at 3:00 PM PDT and October 15, 2026 at 5:10 AM PDT, some customers may have experienced delayed Events delivery and Box Drive synchronization. # Analysis The incident was caused by an unexpected workload surge. We remediated the issue by deploying a targeted filter for the workload and adding capacity. During the mitigation, some Events and Drive synchronizations may have been delayed. # Corrective Actions Box has initiated the following corrective actions: * Adding monitoring and improved workload filtering tools to respond to future incidents quicker. * Exploring ways to automatically handle unexpected workload changes across our event processing systems. We are continuously working to improve Box and want to make sure we are delivering the best product and user experien
Box·[Critical] Issues with Multiple Box Services
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.
Box·[Medium] Issue with Enterprise Event Reports
After further monitoring, this incident is now considered resolved. Event-based reports and Insights in the Admin Console, results from the Enterprise Events API, and Box AI unit usage have been restored to full functionality and are showing up-to-date information. If you continue to experience any issues, please contact Support at https://support.box.com.
Box·[Medium] Issue with multiple reports
After further monitoring, this incident is now considered resolved. The Report Service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.
Follow Box
Your coding agent knows when Box is down, and tells you when a failure is theirs, not yours. You can also get Box incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "box" and tell me if Box has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=box/feed subscribe https://outages.cc/feed.xml?providers=boxFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane