Thursday, 24 March, 2016 UTC


Summary

Mar 24, 19:20 UTC
Resolved - We've confirmed that the issue is now fixed, and that publishes work across the board again. Our apologies.
Mar 24, 19:00 UTC
Monitoring - We've updated configuration on affected servers and are now monitoring the situation further.
Mar 24, 18:40 UTC
Identified - We've identified the problem to be a configuration file pointing at a server that no longer exists. We're reconfiguring our servers in order to fix the issue.
Mar 24, 18:33 UTC
Investigating - We're investigating increased rates of 502 responses to publishes from our servers in the US East datacenter.