Threads help and reporting
Use the Threads-related help/reporting path; business-only status components may not describe consumer Threads.
Live Domain Check
Run a live reachability check for threads.com. Compare the regional responses with the problem you see in Threads.
Find Threads help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Threads feeds, replies and posting can fail independently of Instagram or Meta business APIs.
The checker above requests threads.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Threads action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
If more than one Meta service is failing for you, compare its own observations rather than extending this result to every app: Messenger status check, Meta Status status check, Facebook status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse social app checks.
Use the Threads-related help/reporting path; business-only status components may not describe consumer Threads.
Open the website in your browser and compare it with the result above. This link opens the service, not its status page.
We have not linked a separate status page for this service. Check the official help page for current notices.
Open Threads 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.
Threads feature, post/profile link privately, app/OS, error and time.
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 Threads.
These are troubleshooting comparisons, not claims that Threads is currently experiencing a particular incident.
Compare a public Threads post in a browser with the failing action in the app.
Keep the draft before refreshing and use Threads/Instagram's official help route for technical or account problems.
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 Threads seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open threads.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 Threads 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 Threads support.
Run the threads.com check and compare its original timestamps and responses with your actual error. Threads feeds, replies and posting can fail independently of Instagram or Meta business APIs.
Use the official help/reporting resource linked above. Use the Threads-related help/reporting path; business-only status components may not describe consumer Threads.
Compare a public Threads post in a browser with the failing action in the app. Keep the draft before refreshing and use Threads/Instagram's official help route for technical or account problems.
Threads feature, post/profile link privately, app/OS, error and time.