502 error on container
Resolved
May 23 at 01:18pm CEST
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
Affected services
ping TAGGRS-DE (Germany)
ping TAGGRS-FR (France)
ping TAGGRS-BE (Belgium)
ping TAGGRS-SE (Sweden)
ping TAGGRS-BR (Brazil)
ping TAGGRS-US (United States)
ping TAGGRS-NO (Norway)
Updated
May 23 at 12:31pm CEST
We have identified the root cause of the issue, we are working on a solution to get the containers that are affected back online.
Affected services
ping TAGGRS-DE (Germany)
ping TAGGRS-FR (France)
ping TAGGRS-BE (Belgium)
ping TAGGRS-SE (Sweden)
ping TAGGRS-BR (Brazil)
ping TAGGRS-US (United States)
ping TAGGRS-NO (Norway)
Created
May 23 at 11:52am CEST
At the moment we are seeing on multiple containers some 502 bad gateways messages. We are investigating the issue at the moment.
Affected services
ping TAGGRS-DE (Germany)
ping TAGGRS-FR (France)
ping TAGGRS-BE (Belgium)
ping TAGGRS-SE (Sweden)
ping TAGGRS-BR (Brazil)
ping TAGGRS-US (United States)
ping TAGGRS-NO (Norway)