Is Box Down?

No — Box is up

Reachable from all 8 checked regions

Average response time: 200ms

Last checked 55 minutes ago · checks run every 6 hours

Official status page: https://status.box.com

Box uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

70ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 55 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

55-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

117ms

DNS 54ms TCP 2ms TLS 12ms TTFB 108ms

arn

238ms

DNS 179ms TCP 1ms TLS 9ms TTFB 227ms

nrt

420ms

DNS 380ms TCP 1ms TLS 7ms TTFB 413ms

ord

97ms

DNS 56ms TCP 2ms TLS 6ms TTFB 84ms

sin

230ms

DNS 160ms TCP 1ms TLS 12ms TTFB 215ms

sjc

90ms

DNS 46ms TCP 1ms TLS 9ms TTFB 82ms

syd

330ms

DNS 299ms TCP 1ms TLS 5ms TTFB 323ms

yyz

82ms

DNS 40ms TCP 1ms TLS 7ms TTFB 72ms

What Box does

Box is a cloud content platform used by enterprises to store, share and govern documents, with retention rules, legal holds and e-signature built in. It is usually the system of record for contracts and regulated files, so an outage blocks not just file access but approval workflows that legal and finance teams depend on.

What an outage looks like

The web application fails to load or sits at the login screen when Login and SSO are affected. Uploads and downloads stall midway. Shared links sent to people outside the company return errors, which is the failure customers notice first. Box Drive and Box Sync stop reconciling local folders, and Box Sign requests fail to send or complete.

What to do about it

Check status.box.com, which lists Login/SSO, Uploads/Downloads, Sharing, Box Sign, the Platform API and desktop clients as separate components across regional zones, so identify which one your failure touches. Files already synced by Box Drive stay on disk and remain usable. Avoid re-sending Box Sign requests that appeared to fail, since duplicates confuse the signing audit trail.

Is it down for everyone, or just you?

If this page says Box is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Box outage FAQ

Is Box down or is it my company's SSO?

Box lists Login/SSO as a component distinct from the web application, and identity problems frequently originate with your own provider rather than with Box. If colleagues on the same identity provider are also stuck at login while status.box.com is green, the issue is more likely your provider. Check both status pages before raising a ticket with either.

Can I reach files already synced to my computer during an outage?

Yes. Box Drive and Box Sync keep local copies of files you have opened or marked for offline use, and those stay readable while the service is unreachable. What fails is anything needing the server: new downloads, sharing, search and version history. Avoid heavy local edits to synced files until sync recovers, to reduce conflicts.

Do Box shared links keep working when Box is down?

Not usually. Shared links resolve through Box, so external recipients see an error rather than the file. Sharing is reported as its own component, so it can fail while internal access works, or the reverse. If a customer needs the file urgently, sending it another way is faster than waiting for a link to start resolving.

Does an outage affect Box Sign signature requests?

Box Sign is listed separately from the core web application, so it can fail on its own. Requests already signed are recorded and are not lost. Requests in flight may not deliver, and the signer sees a broken link rather than a queued document. Re-sending duplicates the request in the audit trail, so confirm the original state first.

Why does Box work for some colleagues but not others?

Box reports status by regional zone, and enterprise accounts are pinned to a zone. Colleagues in a different region can be unaffected by an incident that stops your office entirely. Component-level failures produce the same pattern: someone using only the web application may see nothing wrong while a team relying on the API is blocked.

How we measure this

We request Box's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Box publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Box goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required