Box favicon

Box outage on 2026-10-20

box.com
October 2026 20 Major incident

Box's Public API, Box Sign and Downloads broke for 1h 32m on 20 October, starting at 02:19 UTC. The fault sat on Box's side, affecting its Content API and Uploads/Downloads components.

Started

02:19 UTC

Duration

Lasted 1h 32m

Source

IsDown

Next time

Box is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

Affected components: Content API, Uploads/Downloads

What happened?

Box opened the incident at 02:19 UTC, saying it was investigating an issue with the Public API and Box Sign, with users possibly seeing errors or timeouts. By 02:33 the scope had widened: Box added Downloads to the list of affected services, still under investigation. At 03:11 Box said the issue had been identified and a fix was being implemented. The incident was marked resolved at 03:47, with Box stating all services had been restored to full functionality and pointing anyone still having trouble to its support page. That puts the total outage at 1h 32m, affecting the Content API and Uploads/Downloads components on Box's own status page. Box labelled this incident "Medium" severity, a vendor grading that describes their internal triage, not the impact on your integration. No user reports were filed during this window on record, so there's no first-hand account of what the errors or timeouts looked like from outside Box. Box's status page is the only public record of this event, and it only ran to four updates across the full lifecycle. No post-mortem has been published, so the underlying cause of the Public API, Box Sign and Downloads failures is not on the record beyond "an issue" being identified and fixed. In the past 90 days Box has logged 21 incidents with a median duration of 1 hour 15 minutes, so this one ran a bit longer than typical for Box.

Learning

Box's own status updates describe a backend fault: the Public API, Box Sign and Downloads path broke while the files themselves presumably sat untouched in storage. That's a server-side failure, the kind an uptime check against your own application wouldn't catch, because your app's health depends on Box responding correctly, not on whether your database or frontend are up. UptimeRobot's own 30-day figures for Box show 8 incidents, all resolved, with a median duration of 1h 50m, which is a independent read on how often Box's API layer misbehaves regardless of what Box's own status page says. When a provider's API returns errors or times out, your own monitoring can stay green the whole time if it's only checking that your service is listening, not that Box is answering correctly. That's not a contradiction, it just means the two checks are watching different halves of the same transaction. Days like this are why a provider-facing check matters as much as a self-facing one. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.