From about 1 week ago, the cloud server that passes user commands to Tag Managers had experienced performance issue. During that time, motion event/temperature information upload from tag to the cloud server (via Tag Managers) was not affected, however, user who tried to beep, arm or disarm tags may have experienced very slow response and server timeout error. 

This was due to an change we made to server configuration (locally run our "user command" forwarding server that used to run on a separate Linux server on the same Windows web server) intended to reduce service down-time, but turns out the Windows port of the server software originally written for UNIX caused performance problems. 

We have recently restored the old server configuration and have confirmed that these issues are now resolved. We apologize for any inconvenience these issues have caused.

‹ Go back to the blog


Leave a comment

comments have to be approved before showing up