[Minor] User May Encounter Issues Accessing Marketing Page box.com

Update timeline

1. investigating Feb 20, 2026, 07:11 PM UTC

   Our team is investigating an issue with the marketing site box.com. Users may see errors when attempting to access Box.

2. identified Feb 20, 2026, 07:14 PM UTC

   Our team has identified the underlying cause of this issue and is working to take remediating steps. The issue is due to an outage within Cloudflare at this time: https://www.cloudflarestatus.com/incidents/kwy3dt82bwbt As we work on remediation steps users can workaround this issue by access box through app.box.com instead of box.com

3. monitoring Feb 20, 2026, 07:30 PM UTC

   Our team has taken steps to remediate this issue and is seeing improvement for our marketing page box.com. We are continuing to monitor for any additional impact.

4. resolved Feb 20, 2026, 08:37 PM UTC

   This incident has now been resolved. Box will continue to monitor CloudFlare: https://www.cloudflarestatus.com/incidents/kwy3dt82bwbt

5. postmortem Jul 09, 2026, 07:16 PM UTC

   We recently addressed issues affecting Box web access. 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 10:50 AM PST and 11:25 AM PST on February 20, 2026, some users may have experienced difficulties accessing Box via web browser, including failed page loads and intermittent connectivity. During this time, requests to our site that relied on a third-party network service did not route reliably for affected networks, causing DNS resolution and connectivity failures for that hostname. We were able to restore service after the third-party re-advertised the affected network prefixes, at which point we safely re-enabled the dependent routing configuration, restoring normal service behavior. In addition, we are working with the third-party provider and updating our procedures and monitoring to reduce the risk of recurrence and improve detection and recovery. # Analysis This incident highlighted a dependency risk on third-party network prefix advertisement and revealed opportunities to improve early detection and customer-facing communication. It also reinforced the importance of clear playbooks for safely changing routing configurations during third-party outages and ensuring monitoring captures customer-impacting DNS and connectivity failures quickly. # Corrective Actions Box has initiated the following corrective actions: * Work with the third-party provider to complete follow-up and incorporate their post-incident findings * Update our routing and operational runbooks to clarify safe, pre-approved steps for toggling routing configurations during third-party network incidents * Enhance external-facing monitoring and alert thresholds for DNS and site availability to detect and communicate customer impact more quickly ‌ 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