Intercom Incident Report for 2017-01-19 outage
status.intercom.com
status.intercom.com
It seems like the sort of thing that might happen when the statistics are providing the wrong information for carrying out the query (rather than any sort of change to the server/db engine).
Does anyone know how to best protect your service from this?