WhatsApp Was Down For Millions Of Users Across The US & UK, Issue Fixed

The most popular Facebook-owned messaging app was down for millions of users. As per hundreds of users on Twitters the issue had started on May 3 after 9pm. That's not all, the DownDetector also showed the app was down in several parts of the world such as Europe, parts of Latin America as well as Brazil. However, as per updates, the issue later spread to the US, it was earlier down on the East Coast, but later spread to other parts.

According to The Next Web, right after the app went down, WhatsApp confirmed the issue, but it didn't comment on when the problem would be fixed. However, several Twitter users claimed that the latest update might have caused the issue. At around 6:45am several users claimed the issue got fixed. But again, there were hundred of users who still couldn't text using the app.

"Showing Connecting.... Looks like an issue with the service," one of the users wrote on a forum claimed. While another WhatsApp user mentioned that the messaging app stopped working at around 9:15pm. Now, the outage has come at a time when the Facebook owned app has been working on a major update. As reports suggested the new update would allow users to pin conversations at the top of the menu within the app.

The DownDetector showed there were hundreds of outages since the morning across the UK, Express reported. Again at around 11:40PM, the updates claim that users were still suffering from connection issues, with the app not working for many users. Also, there were no ETA as to when the app would be back to normal in the UK. Through the support came up with an initial update to the issue. "WhatsApp is aware of the issue and working to fix it as soon as possible," said WhatsApp spokesperson.

Even though the actual reason for a sudden issue was unknown. The users across the globe also claimed that the service was resume. However, it was unclear as how long it would take for all the servers to resume the same. According to a later update, the issue was fixed around 7PM ET or 4PM PT.