Perhaps this is along the lines of what you mean?
https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/...
When you browse to the cloud you connect to a "shard" that's denoted by the "nxxx" number in the URL. That shard is made up of two mirrored sets of hardware at two different Meraki data centres. Assuming Meraki has to do any work on one set of infrastructure they would simply change the DNS resolution on your shard to point to the alternate DC.
This changing of DNS can actually happen at any time, and probably has to you but you never noticed.
To illustrate, let's pick a random shard, say N45, and look at the DNS:
You can see that N45 is actually just a CNAME for SDG194. SDG194 is the DC and actual hardware where this shard currently points to. If, for any reason SDG194 was undesirable for use Meraki can alter that DNS CNAME record to point to another DC, like maybe DAL.
I know DAL is another DC because that's where N46 is actually pointing to right now:
Hopefully that helps 🙂