WhatsApp Web help and reporting
WhatsApp documents technical reporting; business API status alone does not establish consumer messaging availability.
Live Domain Check
Run a live reachability check for web.whatsapp.com. Compare the regional responses with the problem you see in WhatsApp Web.
Find WhatsApp Web 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
WhatsApp Web linking, browser loading and message synchronisation are separate from the phone app.
The checker above requests web.whatsapp.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual WhatsApp Web action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Compare the web, business and main WhatsApp entrypoints when describing which client or workflow is affected: WhatsApp Business status check, WhatsApp status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse messaging checks.
WhatsApp documents technical reporting; business API status alone does not establish consumer messaging availability.
Open the website in your browser and compare it with the result above.
Open WhatsApp Web 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.
Browser/OS, linking or sync stage, phone-app result, error and time with QR codes omitted.
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 WhatsApp Web.
These are troubleshooting comparisons, not claims that WhatsApp Web is currently experiencing a particular incident.
Check whether the phone app works while the linked browser fails, and record whether linking or sync is the first problem.
Inspect browser/network access and official linked-device guidance; do not remove working linked sessions without preserving what you need.
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 WhatsApp Web seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open web.whatsapp.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 WhatsApp Web 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 WhatsApp Web support.
Run the web.whatsapp.com check and compare its original timestamps and responses with your actual error. WhatsApp Web linking, browser loading and message synchronisation are separate from the phone app.
Use the community buttons on this page to share whether the service works for you. For help from WhatsApp Web, use the official help/reporting resource linked above. WhatsApp documents technical reporting; business API status alone does not establish consumer messaging availability.
Check whether the phone app works while the linked browser fails, and record whether linking or sync is the first problem. Inspect browser/network access and official linked-device guidance; do not remove working linked sessions without preserving what you need.
Browser/OS, linking or sync stage, phone-app result, error and time with QR codes omitted.