Garmin Connect app service down which then blocked connectiq webrequests

So here's something that surprised me today. My datafields that use makewebrequest stopped working mid-ride today. Ignored it for awhile thinking i was just in bad spots for phone signal, then finally checked it toward the end of the ride by opening Garmin Connect. And saw a nice large red box saying "Garmin Connect is currently experiencing an outage"

I know that the the garmin connects to Garmin Connect and Connect has to be running in the background, but I didn't realize that Garmin is apparently forwarding the api requests to their own servers somehow. I was expecting any request we make thru connectiq went directly from the phone to the requested url. but if that was the case, any garmin service outage wouldn't have affected the apps.

anything i'm missing, or does anybody have true knowledge of how the flow works? or am i just putting two random things together and making too much of an assumption they are related?

peterdedecker over 4 years ago

I assume it's more likely that Garmin assumes that there's no internet connectivity when the Garmin Server can not be reached and disable all functionality which needs internet. Of course that shouldn't be the case, internet calls should remain working when the Garmin Server is down for maintenance.

(Slightly unrelated but preferably I would even like to see that you're still able to send settings with the cached setting definitions when there's no internet connection).

windfield over 2 years ago

Connect is down again today and i'm getting flooded with customer questions. I've done everything I can to make my app's backend as stable as possible and have even built out a status page. But there's nothing I can do if webrequests are routed via Garmins own servers which are down. Unfortunately, this one outage today is more downtime than all my own server issues combined for this year.