JeremyNicoll Posted January 1, 2019 Report Share Posted January 1, 2019 I'm seeing things like this in the log Update started: 01/01/2019 10:36:46 Update ended: 01/01/2019 11:10:09 Time elapsed: 0:33:23 Unable to retrieve update information from server -- see that 33 minute time? And the systray throbber is still doing it. Link to comment Share on other sites More sharing options...
HazBeen Posted January 1, 2019 Report Share Posted January 1, 2019 Popup notification from EAM saying it is unable to contact its update server, here in USA too. Using staff member GT500's cmd_update.bat to perform an update, signatures begin to download, then are interrupted... Link to comment Share on other sites More sharing options...
stapp Posted January 1, 2019 Report Share Posted January 1, 2019 Mine in UK is working fine now after missing 2 updates this morning. Probably the server was drunk (It is New Year after all ) Link to comment Share on other sites More sharing options...
Cister Posted January 1, 2019 Report Share Posted January 1, 2019 It is working fine here in Québec, Canada. Link to comment Share on other sites More sharing options...
JeremyNicoll Posted January 1, 2019 Author Report Share Posted January 1, 2019 Thank-you; fine here now too. Link to comment Share on other sites More sharing options...
GT500 Posted January 1, 2019 Report Share Posted January 1, 2019 It looks like our CDN had some "degraded performance" issues at 12:00 UTC (7:00 AM EST). This could have lasted anywhere from one to three hours after that, and appears to have been fixed by 14:41 UTC (9:41 AM EST). As for issues outside of the UK, I am not aware of any. Those could have simply been routing issues at the ISP, or stability issues with backbone providers who's networks the data was being sent/received over. Link to comment Share on other sites More sharing options...
atPatakasCausewayside-91x140.thumb.jpg.1e5d52f67095c1ab79c72ae33f54bcdc.jpg)
Recommended Posts