[Medium] Degradation of Enterprise Events API

Final update

We recently addressed issues affecting **Enterprise Events 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 2:31am and 4:45pm PDT on May 14, 2026, some users may have experienced difficulties while working in Box. During this time, customers using the streaming Enterprise Events API experienced delivery delays of up to 6.5 hours. The issue occurred when an internal indexing service unexpectedly generated events at an unconstrained rate, which caused a significant concentrated spike in the total events volume. We were able to resolve the issue by redirecting those events from our streaming enterprise events pipeline for later processing. In addition, we will exclude events originating from internal services from our enterprise events processing pipelines and proactively deprioritize unexpected surges in events to prevent similar issues from occurring in the future. ‌ **Analysis** ‌ There were a number of contributing factors leading to this incident and a reoccurrence on May 18, 2026 between 11:52am and 2:03pm PDT with delivery delays of up to 1.1 hours: ‌ Our internal searc

1. Postmortem · May 29, 19:26 UTC
   We recently addressed issues affecting **Enterprise Events 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 2:31am and 4:45pm PDT on May 14, 2026, some users may have experienced difficulties while working in Box. During this time, customers using the streaming Enterprise Events API experienced delivery delays of up to 6.5 hours. The issue occurred when an internal indexing service unexpectedly generated events at an unconstrained rate, which caused a significant concentrated spike in the total events volume. We were able to resolve the issue by redirecting those events from our streaming enterprise events pipeline for later processing. In addition, we will exclude events originating from internal services from our enterprise events processing pipelines and proactively deprioritize unexpected surges in events to prevent similar issues from occurring in the future. ‌ **Analysis** ‌ There were a number of contributing factors leading to this incident and a reoccurrence on May 18, 2026 between 11:52am and 2:03pm PDT with delivery delays of up to 1.1 hours: ‌ Our internal search indexing service produced events, which should not have been created, at a rate significantly exceeding enterprise usage. These events were published to a queue to be written to the persistent datastore. Also, these events were concentrated in certain access patterns causing hot spotting in some d
2. Resolved · May 14, 19:30 UTC
   Between 2:31am and 4:45pm PDT on May 14, 2026 we observed an issue impacting streaming Enterprise Events API . Our systems detected and corrected the underlying issue. There is no current impact and no further updates will be provided here. If you continue to experience any issues, please contact Box Support at https://support.box.com.