Latest update from https://discordstatus.com/ https://discordstatus.com/ : > Engineering has root-caused this issue to a Google Cloud component called "Traffic

Latest update from https://discordstatus.com/ https://discordstatus.com/ : > Engineering has root-caused this issue to a Google Cloud component called "Traffic Director" which is responsible for configuring our load balancing layer. 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 took measures to remediate by moving to alternate proxy configuration that did not use traffic director. It took us a bit to switch to using a different load balancing topology, but we were able to do so to restore service before Traffic Director issues were resolved. And from https://status.cloud.google.com/incidents/LuGcJVjNTeC5Sb9pSJ9o https://status.cloud.google.com/incidents/LuGcJVjNTeC5Sb9pSJ... : > The issue with Traffic Director has been confirmed to be caused by a recent release; the release has been rolled back and customers can now start using Traffic Director. We have identified a probable root cause and will be publishing an Incident Report within the next several days.