The API was having database related issues for three hours early this morning (Melbourne time), which were related to the previous incident on March 1st.
To follow up on the planned changes from then: the new alerting worked, wasn't persistent enough to wake me up from an exhausted sleep. The database changes had improved the situation, but not stopped it completely (hence this repeat). The proxy issue didn't return from what I can see (thus, only API requests, not search requests, were impacted).
I've got next steps planned for further database improvements, and will look into making the alerting a little more insistent. The delay in resolving this issue was certainly not acceptable.
Posted about 2 years ago. Mar 22, 2016 - 09:44 AEDT