BGMI login failure? Krafton has a message for you! Read here

Battlegrounds Mobile India (BGMI) login failure has hit players across the country forcing Krafton to react.

BGMI login failure have been reported in India. (BGMI)

Battlegrounds Mobile India (BGMI) login failure has been reported across the country today. According to reports, the game's servers were refreshed in the morning today at 5:30 am IST, but ever since several issues started popping up on the users' app that made playing the game difficult. Players, in fact, started complaining about the same. The first error message to show up read, "Server is busy. Please try again later. Error code:db-error." Later, when a few were able to log in to the game, they found their in-game friend list is showing (0/0) or unable to see the friend list.

Ultimately, Krafton, the developer of the game, reacted. It said, "Dear BATTLEGROUNDS MOBILE INDIA fans, We have identified some players are experiencing login failure from 07:57, 7/8 with an error message showing "Server is busy. Please try again later. Error code:db-error"." Krafton further added that the developers are currently trying to find the cause of the issue and will get back to gamers as soon as possible when the issue is fixed. "We apologize for the inconvenience," Krafton wrote in the public notice for the login failure issue of BGMI.

This comes just a week later when Krafton announced a new milestone with BGMI having surpassed 100 million registered users while being one of the most popular battle royale games in India. Login failure issues and in-game friends list errors surely disheartened such a massive fanbase of gamers who actively log in to BGMI on the daily basis.

However, Krafton is working to fix the issue, but players will have to be patient until it is resolved. The issue looks to be quite complicated as it has taken a long time to fix.

Once the BGMI login failed issue is resolved, make sure you have an active internet connection to access the game. In case you face problems, try to remove browser cache and login again.