The Wall Street Journal help and reporting
Select subscriber/account or the digital product involved.
Live Domain Check
Run a live reachability check for wsj.com. Compare the regional responses with the problem you see in The Wall Street Journal.
Find The Wall Street Journal 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
Wall Street Journal articles, apps and subscription authentication can fail independently.
The checker above requests wsj.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual The Wall Street Journal action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse streaming and media checks.
Select subscriber/account or the digital product involved.
Open the website in your browser and compare it with the result above.
Open The Wall Street Journal 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.
Article/product, device/app, subscription route, failed step and error/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 The Wall Street Journal.
These are troubleshooting comparisons, not claims that The Wall Street Journal is currently experiencing a particular incident.
Compare a public page with the paid article/app action and note any sign-in or entitlement message.
Use WSJ's subscriber/customer support for the account and billing provider involved.
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 The Wall Street Journal seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open wsj.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 The Wall Street Journal 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 The Wall Street Journal support.
Run the wsj.com check and compare its original timestamps and responses with your actual error. Wall Street Journal articles, apps and subscription authentication can fail independently.
Use the community buttons on this page to share whether the service works for you. For help from The Wall Street Journal, use the official help/reporting resource linked above. Select subscriber/account or the digital product involved.
Compare a public page with the paid article/app action and note any sign-in or entitlement message. Use WSJ's subscriber/customer support for the account and billing provider involved.
Article/product, device/app, subscription route, failed step and error/time.