We've resolved the second half of yesterday's incident which involved an single member of our application server cluster being reported as connectable and available to handle requests but internally the connections were being dropped by the heroku routing layer. This resulted in the a client-facing 503 error in approximately 4% of requests when contacting urls with the prefix https://fast.chameleon.io/observe/*.