Skip to content

Incident detail

[Major] Issues with Box AI

Resolved incidentMajor

Timeline window

to

Get alerted the next time Box breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    We are investigating an ongoing issue affecting Box AI. Users may experience latency while using Box AI. We will provide more information as soon as it is available.

  2. Monitoring

    A fix has been implemented and we are monitoring the results.

  3. Resolved

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

  4. Resolved

    We recently addressed issues affecting Box AI in Notes, Preview and Hubs. We would like to take the opportunity to further explain these issues and share the steps we have taken to prevent future occurrences.

    ‌

    Between 5:00 PM PT and 6:30 PM PT on May 19, 2025, users may have experienced difficulties while using Box AI. During this time, many users experienced errors when trying to make queries on Box AI and were unable to receive query results. Other users experienced unusually high latencies in responses during this period. The disruption was caused by a bug in a code change deployed to one of our Box AI services. We quickly identified the problem and resolved it by rolling back the faulty release. The underlying issue has since been fixed. Additionally, we have increased testing coverage and plan to implement more latency monitoring to prevent similar issues from occurring in the future.

    ‌

    Analysis

    At Box, we are always striving to improve the resilience of our services. The AI team implemented a code change intended to support automatic fallbacks for large language model (LLM) providers during outages. A bug in this change temporarily resulted in AI query failures, which we were able to resolve by rolling back the faulty release. This incident highlighted gaps in our latency monitoring systems and internal integration test coverage. We are committed to improving these areas to enhance system resilience and reliability.

    ‌

    Corrective Actions

    Box has initiated the following corrective actions:

    • Enhancing latency monitoring to detect issues earlier
    • Making our unit testing process stronger before releasing updates
    • Strengthening our integration tests to catch this class of issues before it goes out

    ‌

    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

Keep exploring

More from Box

Neighboring incidents on Box's timeline and the rest of their record on OutageDeck.