connection issue (medtronic EU)

[raferg]

I'm seeing the following in my heroku logs:

2020-12-07T01:22:00.305636+00:00 app[web.1]: tick 2020-12-07T01:22:00.305Z
2020-12-07T01:22:05.428919+00:00 app[web.1]: Load Complete:
2020-12-07T01:22:05.428928+00:00 app[web.1]: 	 sgvs:473, profiles:1, devicestatus:265
2020-12-07T01:22:05.428941+00:00 app[web.1]: data loaded: reloading sandbox data and updating plugins
2020-12-07T01:22:07.850928+00:00 app[web.1]: MiniMed Connect error: Error: connect ETIMEDOUT 144.15.107.20:443
2020-12-07T01:22:07.850959+00:00 app[web.1]: stack: Error: connect ETIMEDOUT 144.15.107.20:443
2020-12-07T01:22:07.850960+00:00 app[web.1]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)

Any ideas if something has changed recently?
I wasn't seeing updates this morning - so I redeployed on heroku, then realised i was a bit behind master, so I rebased and redeployed again - and now see the above error. (and I'm not seeing any updates on my heroku site)

[raferg]

It has been suggested that medtronic has blocked my heroku site - but I don't know how to diagnose this.

[raferg]

... And I've managed to redeploy nightscout (from the same got repo) in the US heroku, no issues. It seems I did get onto the ban list. I hope this isn't new operating procedure at medtronic!

[jhuang234]

Hi @raferg , thanks for your information. It works for me after switch to US heroku after 2-3 dyno restarts.
Really appreciated.