Box experienced a major incident on December 18, 2025 affecting Box Sign, lasting 23m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Dec 18, 2025, 12:21 AM UTC
We are investigating an ongoing issue affecting Box Sign. We will provide more information as soon as it is available.
- identified Dec 18, 2025, 12:39 AM UTC
Our team has identified the underlying cause of this issue and is working to take remediating steps. We will provide additional updates as they become available.
- resolved Dec 18, 2025, 12:45 AM UTC
After further monitoring, this incident is now considered resolved. The affected services have been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.
- postmortem Feb 24, 2026, 01:10 AM UTC
We recently addressed issues affecting several features of 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. On December 17, 2025, from 11:15 AM PST to 4:46 PM PST, some users may have experienced difficulties while working in Box Sign, Box AI, and Box Doc Gen. During this time, users may have noticed service degradation and delayed email delivery. The issue was caused by a missing schema, which was itself caused by a corrupted schema deployment. We were able to resolve the issue by rolling back the change that temporarily created issues. **Analysis** Box Sign, Box AI, and Box Doc Gen rely on a definition of the schemas that describe the events that they need to process. As we deliver new products, these schemas may occasionally need to be updated, and we have a standard process and pipeline to deploy these schema. As part of a project to upgrade our pipeline infrastructure, the schema deployment pipeline migrated to a new infrastructure. During the migration process, an external library version upgrade introduced a new default behavior that was not compatible with the existing pipeline. This resulted in a temporary degradation of the service. Additionally, the migration process exposed some observability and guardrail gaps in the pipeline that would have prevented this issue from happening and that extended the impact for a longer period of time. Once identified, the incompatible library was reverted to the previous version and the system resumed to normal. **Corrective Actions** Box has initiated the following corrective actions: * Introduce a schema validation step in the deployment pipeline so that incompatible schemas cannot be deployed * Enforce the environment promotion process as part of the schema deployment pipeline * Uplift the observability of the pipeline to enable more visibility around the different phases of the deployment process 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