We became aware of an increased number of errors between 12:54 and 13:10 on Wednesday 2rd September 2020. Due to a unexpected spike in CPU load on a back-end service, API responses were delayed. This led to consultations not being shown in the Admin Portal during periodic refreshes. Existing consultations taking place were not affected.
We are conducting a root-cause analysis to identify the reason for the CPU spike. As a temporary measure, we are increasing capacity to mitigate the effect of this happening again.