WhatsApp Web users were left confused on May 20 after the browser version of the messaging platform began sending some people to a Facebook login page instead of the usual WhatsApp pairing screen.

The problem appeared to affect users in several countries, including the United States, India, Malaysia and Singapore. Reports suggested the issue was not limited to people trying to open a fresh session. Some users said their active WhatsApp Web sessions ended suddenly, forcing them back to a login flow that unexpectedly displayed Facebook instead of WhatsApp.

For a service used heavily by office workers, students, small businesses and customer support teams, the disruption was more than a minor inconvenience. WhatsApp Web is often kept open throughout the day for quick replies, file sharing and work communication, so an unexplained login error quickly became a wider concern.

Why users were worried

The biggest concern was not just that WhatsApp Web stopped working. It was the page users were seeing. Because WhatsApp and Facebook are both owned by Meta, the sudden redirect made many people question whether Meta was quietly changing the way WhatsApp Web accounts are verified.

Several users online said they did not want to connect Facebook with WhatsApp or create a Facebook account to access their messages. Others treated the redirect as a possible technical mix-up between Meta services rather than a deliberate product change.

At the time of publication, there was no confirmed announcement from Meta saying WhatsApp Web now requires Facebook login. That makes a temporary authentication or routing glitch the more likely explanation, especially because reports appeared suddenly and affected users unevenly across regions.

Outage trackers also showed fresh complaints around WhatsApp access. Users can check live service reports through Downdetector’s WhatsApp status page, although outage platforms rely largely on user reports and may not always reflect Meta’s internal service status in real time.

Some users also reported trouble while scanning passkeys or trying to reconnect through the mobile app. Others said the WhatsApp Desktop app showed similar disruption, suggesting the issue may have affected the way linked devices were being authenticated rather than only the browser page.

What users can try now

The safest step is to avoid entering Facebook credentials into an unexpected login page while attempting to use WhatsApp Web. Users should first confirm they are on the official web.whatsapp.com address and avoid any third-party page that appears during the login process.

If WhatsApp Web keeps redirecting, users can try removing the linked device from the WhatsApp mobile app and pairing it again. Clearing browser cache, opening WhatsApp Web in a private window, or trying another browser may also help if the problem is stored in a local session.

For Windows users on the desktop app, some people reported partial success after going to the app settings, terminating WhatsApp, then using the repair or reset option before reconnecting. However, if the problem is coming from Meta’s servers, local fixes may only work temporarily or not at all.

The incident also comes at a sensitive time for Meta, which is adding more AI and account-linked features across WhatsApp, Facebook and Instagram. Swikblog recently reported on WhatsApp’s private AI chat feature and how Meta is trying to rebuild trust around data handling. You can read that related coverage here: WhatsApp launches private AI chats that even Meta says it cannot read.

For now, the WhatsApp Web Facebook redirect appears to be a service-side glitch rather than a confirmed account policy change. The best approach is to avoid unnecessary login attempts, use only official WhatsApp access points, and wait for Meta to clarify or fully resolve the issue.