- Aug 18, 2014
- 4,662
- 5
- 16,965
Many apologies for the issues over the weekend!
We had some server-related problems and, it being a weekend at the time, we were not able to respond to it as well as we should have. Once we were made aware of the issue (by early Sunday afternoon), we worked to address it as quickly as we could; however, it had already been ongoing for quite a few hours and it took quite a few more to resolve.
All in all, we were down for ~24 hours, with varying degrees of accessibility before and after the incident. As of earlier this morning (March 7), these issues should be resolved. A temporary fix has been implemented while we work on a more permanent solution. Should anything of this sort reoccur, please don't hesitate to send an email to community@tomshardware.com to alert us to the matter.
Best regards,
Kevin Ng
Assistant Community Manager
We had some server-related problems and, it being a weekend at the time, we were not able to respond to it as well as we should have. Once we were made aware of the issue (by early Sunday afternoon), we worked to address it as quickly as we could; however, it had already been ongoing for quite a few hours and it took quite a few more to resolve.
All in all, we were down for ~24 hours, with varying degrees of accessibility before and after the incident. As of earlier this morning (March 7), these issues should be resolved. A temporary fix has been implemented while we work on a more permanent solution. Should anything of this sort reoccur, please don't hesitate to send an email to community@tomshardware.com to alert us to the matter.
Best regards,
Kevin Ng
Assistant Community Manager
Facebook
Twitter
Instagram