- You are not the only one having issues if you are unable to connect to Spotify or Discord. On Tuesday afternoon, both services recognized that they had issues. However, it doesn’t seem like a major DNS or Amazon Web Services (AWS) failure is to blame this time. But even if Apple’s event servers are still running, as well as security cameras and robot vacuums, the synchronicity is nonetheless rare.
- When Discord restarted its streaming service to solve one problem, a new problem caused its API to fail, and they were still investigating as recently as 30 minutes ago, according to the service. In a tweet at 1:22 p.m. ET, the Spotify Status account said “we’re looking into it,” but provided no other information on what was going on.
- Things appear much better now, according to the Spotify Status tweet at 2:39 p.m. ET, and there have been indications that the majority of customers are back online. Work has started to restore service on Discord’s status page, and as of around 4:01 p.m. ET, that service has been restored, connecting the difficulties to a broken Google Cloud component that they had to route around.
- However, a Google Cloud case study shows that Spotify is also a client, which might explain the unexpected troubles that both services have been experiencing. Both Discord and the Google Cloud status page identified an issue with the Traffic Director component, which was later reverted back to its previous functional version. No, it wasn’t AWS or DNS this time; it was just Google this time around.
Google Cloud status:
- There was a recent version that had created a problem with Traffic Director. This was rolled back, and users may now use Traffic Director normally again. Within the next several days, we’ll be releasing an Incident Report detailing our findings.
- For all impacted projects, the problem with Cloud Networking, Cloud Load Balancing and Traffic Director has now been rectified.
- While we worked to fix the problem, we appreciate your patience.
