Meraki has completed maintenance to restore dashboard services. All dashboard functions are working normally. Thank you for your patience, the team is reviewing options for communicating service changes in the future.
The TTL was only 60 seconds so I'm sure they were implementing a manual change, and it lasted much longer than a fail-over should. I suspect that they just forgot to use a FQDN on a temporary CNAME record, and the short name they used, sdg327, wasn't resolvable by anyone except if you were using one of their domain joined computers.
A status page sounds like a good idea though, given Meraki is cloud based it should be able for users to determine quickly if there is a problem or not.
If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.
Yes https://account.meraki.com is having DNS issues like others have pointed out. Mobile app also experiencing same issue. Luckily I had a saved URL that goes direct to one of my networks which brought up an authentication page that did allow me in.
Meraki is aware of and actively working to correct the service degradation seen in our dashboard. During this period our engineers have been performing critical maintenance and some services related to account and organisation administration were unavailable. Meraki networking devices have been functional and configurable throughout this whole period. At this time our services are nearly fully restored and we will provide another update when this is complete.
Meraki has completed maintenance to restore dashboard services. All dashboard functions are working normally. Thank you for your patience, the team is reviewing options for communicating service changes in the future.