Tumblr help and reporting
Separate dashboard/editor failures from one blog's custom-domain issue.
Live Domain Check
Run a live reachability check for tumblr.com. Compare the regional responses with the problem you see in Tumblr.
Find Tumblr help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Tumblr dashboard loading, an individual blog and posting can fail separately.
The checker above requests tumblr.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Tumblr action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse social app checks.
Separate dashboard/editor failures from one blog's custom-domain issue.
Open the website in your browser and compare it with the result above.
Open Tumblr help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Blog/post URL, custom-domain result, editor action, client and time without private draft 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 Tumblr.
These are troubleshooting comparisons, not claims that Tumblr is currently experiencing a particular incident.
Compare another public blog with the dashboard or editor and keep any unpublished draft.
Use Tumblr Help for the exact symptom; compare a blog's custom domain with its Tumblr address if only that blog fails.
A 403 Forbidden or 429 Too Many Requests 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 Tumblr seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open tumblr.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 Tumblr issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Tumblr support.
Run the tumblr.com check and compare its original timestamps and responses with your actual error. Tumblr dashboard loading, an individual blog and posting can fail separately.
Use the community buttons on this page to share whether the service works for you. For help from Tumblr, use the official help/reporting resource linked above. Separate dashboard/editor failures from one blog's custom-domain issue.
Compare another public blog with the dashboard or editor and keep any unpublished draft. Use Tumblr Help for the exact symptom; compare a blog's custom domain with its Tumblr address if only that blog fails.
Blog/post URL, custom-domain result, editor action, client and time without private draft contents.