Between 15:15 and 16:50hs (UTC-3) there was an internal error in a backoffice instance, which caused the system to respond with HTTP 502 error in approximately 2% of the received requests during that time frame. The instance was taken out of service and the problem was resolved.