Dropbox help and reporting
Keep local unsynced files safe and choose the correct account/support plan.
Live Domain Check
Run a live reachability check for dropbox.com. Compare the regional responses with the problem you see in Dropbox.
Find Dropbox help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Dropbox website access, desktop sync and shared-link permissions can fail separately.
The checker above requests dropbox.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Dropbox action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Keep local unsynced files safe and choose the correct account/support plan.
Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.
No separate incident dashboard is linked here. Use the official product help and any current announcements it links to; this does not mean that no outage is possible.
Keep local unsynced files safe and choose the correct account/support plan.
Open Dropbox help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
File type/size, sync/share action, client/version, storage state and time without private file contents.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Dropbox.
These are troubleshooting comparisons, not claims that Dropbox is currently experiencing a particular incident.
Compare a file online with its local sync state and note whether one file or the entire folder is affected.
Preserve unsynced local files; check storage/account selection and the sync error before unlinking the client.
A 403 or 429 means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Dropbox seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open dropbox.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Dropbox issue.
Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Dropbox support.
Run the dropbox.com check and compare its original timestamps and responses with your actual error. Dropbox website access, desktop sync and shared-link permissions can fail separately.
Use the official help/reporting resource linked above. Keep local unsynced files safe and choose the correct account/support plan.
Compare a file online with its local sync state and note whether one file or the entire folder is affected. Preserve unsynced local files; check storage/account selection and the sync error before unlinking the client.
File type/size, sync/share action, client/version, storage state and time without private file contents.