Dec 5, 20:56 UTC
Resolved – Our monitors and logging point to our Image CDN no longer responding with 502s.
Dec 5, 20:50 UTC
Monitoring – A fix has been made to address the issue causing the 502 response and are monitoring to make sure the change has resolved the issue completely.
Dec 5, 20:37 UTC
Identified – We have identified the cause of the 502s and are working towards a fix.
Dec 5, 20:23 UTC
Investigating – We are currently investigating reports of issues with our ImageCDN.