The issue has been resolved. The containers are now running again. The problem occurred following a server upgrade aimed at enhancing performance. Our load balancers were still directing traffic to the old servers instead of the new, upgraded ones. If there are any questions about this, feel free to reach out to support@taggrs.io

We have identified the root cause of the issue, we are working on a solution to get the containers that are affected back online.

At the moment we are seeing on multiple containers some 502 bad gateways messages. We are investigating the issue at the moment.