On Tuesday, many Spotify and Discord users were struggling to log in to their accounts.

⠀

Both services have acknowledged the issue and explained that there was not any kind of problem with DNS or the Amazon Web Services (AWS) to cause the outage.

⠀

Discord has explained in an incident report that after restarting their streaming service to fix one of its issues, a new issue emerged, which caused a failure of its API. About 30 minutes after the failure of Discord’s API, their team was still investigating the issue.

⠀

Spotify, on the other hand, at 10:22 AM PST, tweeted that they were having an outage and were investigating the issue. Later at 11:39 AM PST, Spotify gave users updates that their system was looking better and had most users back online.

⠀

Discord on their status page noted that their team had begun to “restore its service,” and at about 1:00 PM PST their service system was fully restored.

⠀

The Discord team after conducting their investigation of the issue, tied the outage to a glitch with a malfunctioning Google Cloud component. Spotify had the same issue, according to a case study that Google Cloud posted. Google Cloud’s status page mentioned that there was a glitchy update to its Traffic Director component which they had to roll back to allow their customers to begin using Traffic Director.

⠀

The rollback of the Traffic Director update ultimately allowed Spotify and Discord to restore their services.

⠀

For more from us at Waivly, join our free fun-to-read and to-the-point newsletter enjoyed by hundreds of people across the internet every day of the week 👇