Engineering took measures to remediate by moving to alternate proxy configuration that did not use traffic director. "In its malfunction, it caused our internal load balancing layer to not have a valid configuration, which caused a loss of availability of the API. "Engineering has root-caused this issue to a Google Cloud component called 'Traffic Director' which is responsible for configuring our load balancing layer," the chat, voice and video-communications service explained. This was because of the same issue suffered by Spotify. Were the Spotify and Discord outages connected?ĭiscord also experienced some technical difficulties on Tuesday night. "You've been logged out, log back in to start listening," was another message that appeared, even when users entered the correct login details. "We're all mixed up, refresh this page or try again later," was one of the error messages seen on Spotify on Tuesday night. During the technical issues, users were faced with a variety of error messages from Spotify.
0 kommentar(er)
