Earlier today a network partition event occurred that caused some applications to intermittently return HTTP 502 errors when they should have been available - this was for some applications running on the "shared" revproxy/routing service (non SSL applications).
These issues are normally routed around and resolved before hitting applications and causing errors, but in this case we did not detect and resolve this in time.
This is now been resolved and we are looking at ways of preventing this.
