We recently addressed issues affecting the Box service. 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 3:58PM PDT and 5:42PM PDT on August 2, 2022, a small subset of our users may have experienced difficulties while working in Box. During this time, some users of Box would have seen high latency or errors using the Box service. The issue occurred as a result of a result of a backend database receiving an increased volume of traffic that caused it to lag in responding to requests. We were able to resolve the issue by temporarily throttling the traffic. In addition, we changed a configuration value to more effectively utilize our caches and prevent similar issues from occurring in the future.
Analysis
One of our internal database clusters experienced increased latency as a result of heavier-than-expected traffic from a subset of users. This may have resulted in latent or failed requests to Box for users who were assigned to this particular database cluster. In order to reduce load and improve latency on this cluster, our database engineers temporarily implemented a targeted throttler to reduce the volume of heavier traffic requests which restored overall service to nominal levels. In addition, our engineers identified and changed a configuration value that increased the effectiveness of our cache utilization when responding to this type of heavy traffic. By utilizing the cache more effectively, we are able to avoid sending such heavy traffic to the database, thus preventing similar issues from occurring in the future.
Corrective Actions
The following corrective actions have been completed or are planned:
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