Box incident

[Critical] Issue with Box API

Critical Resolved View vendor source →
Started
Feb 24, 2026, 11:32 PM UTC
Resolved
Feb 25, 2026, 12:15 AM UTC
Duration
43m
Detected by Pingoru
Feb 24, 2026, 11:32 PM UTC

Affected components

Content API

Update timeline

  1. identified Feb 24, 2026, 11:32 PM UTC

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

  2. identified Feb 24, 2026, 11:32 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Feb 24, 2026, 11:42 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Feb 25, 2026, 12:02 AM UTC

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

  5. resolved Feb 25, 2026, 12:15 AM UTC

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

  6. postmortem Mar 05, 2026, 10:31 PM UTC

    _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 February 24, 2026 between 1:15 PM PST and 3:59 PM PST, some users may have experienced difficulties while working in Box. The most significant impact occurred from 1:42 PM PST to 1:59 PM PST, when Uploads, Downloads, Logins, APIs, and Notes saw elevated latency and errors. A small subset of functionality continued to experience some degradation through 3:59 PM PST. The issue occurred due to our cache cluster becoming temporarily overloaded due to a traffic spike concentrated on a single hot key. We were able to resolve the majority of the impact by rate limiting peripheral workloads and fully resolve the issue by stopping the offending traffic source. We are now implementing automated hot key detection and introducing dynamic rate limiting at the caching layer to prevent similar issues from occurring in the future. ‌ 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. 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

Looking to track Box downtime and outages?

Pingoru polls Box's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Box reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Box alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Box for free

5 free monitors · No credit card required