Geo redundancies? Discord is all in us-east-1 gcp. Unless you Meant AZ redundancy?

> We are running more than 850 voice servers in 13 regions (hosted in more than 30 data centers) all over the world. This provisioning includes lots of redundancy to handle data center failures and DDoS attacks. We use a handful of providers and use physical servers in their data centers. We just recently added a South Africa region. Thanks to all our engineering efforts on both the client and server architecture, we are able to serve more than 2.6 million concurrent voice users with egress traffic of more than 220 Gbps (bits-per-second) and 120 Mpps (packets-per-second).

I don't see anything on their messaging specifically, just assuming they would have something similar.

https://discord.com/blog/how-discord-handles-two-and-half-mi...

Our messaging stack is not currently multi-regional, unfortunately. This is in the works, though, but it's a fairly significant architectural evolution from where we are today.

Data storage is going to be multi-regional soon, but that's just from a redundancy/"data is safe in case of us-east1 failure" scenario -- we're not yet going to be actively serving live user traffic from outside of us-east1.

You may consider regioning guilds by the region of the guild owner's ToS/billing address.

I don’t think discord needs geo redundancy :)