Bungie recently got its game "Destiny" back online after a scheduled and announced down time for game maintenance. However, many players reported experiencing "Beaver errors" and were subsequently kicked out of the game. A new report from Express.co.uk states that Bungie has resolved the issue. 

A Beaver error is described as a failure in the game's capability of connecting one console to another player's console, effectively disabling multiplayer and hosting capabilities as well as temporarily kicking a player out of the game session. 

Some reasons for Beaver errors include ISP saturation, Internet congestion, and packet loss. According to the report from Express, the Beaver error in "Destiny" might have occurred due to server congestion as too many players tried to connect immediately after the game went back online following the maintenance period. 

"We're aware of Destiny players receiving intermittent Beaver errors and are currently investigating. Stand by for updates," read Bungie's original response to the complaints from players unable to connect to the game. 

In less than 24 hours, however, the company was able to resolve the issue and posted the update via Twitter, saying, "We have resolved the issue that was causing players to encounter Beaver errors, thanks for your patience."  

From this point on, players should no longer experience the frequent Beaver errors. 

The maintenance was announced to occur from 8 a.m. PST on June 22 and lasted for a scheduled six hours. According to Bungie's original announcement, the maintenance work was to prepare the game for "future plans" although they did not specify what those plans are. 

It is important to note that the next DLC for the game, "The Taken King," will be launched on Sept. 15 and it is possible that the recent maintenance period was to help prepare the game for the upcoming changes that will slowly be implemented until the DLC's main launch date.