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.
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.
Select subscriber/account or the digital product involved.
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.
Select subscriber/account or the digital product involved.
Open The Wall Street Journal 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.
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 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 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.
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 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 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.