Resolved -
A fix was deployed at 15:50. We will monitor this closely, and a report will be attached to this incident after further investigation.
Jan 16, 16:50 GMT
Update -
We identified a recurrence at 15:55 and are actively monitoring the situation.
Jan 16, 16:16 GMT
Monitoring -
Root cause analysis is ongoing, and we are monitoring the recovery.
Jan 16, 14:33 GMT
Update -
We are analysing the root cause. Searches have recovered and are returning results.
Jan 16, 14:16 GMT
Investigating -
We are currently investigating this issue.
Jan 16, 13:05 GMT
Resolved -
System performance is now back to normal, we will continue to monitor this closely, a report will be attached to this incident after further investigation
Jan 14, 16:02 GMT
Update -
A fix has been deployed to resolve this issue, we are currently monitoring to ensure everything is running as normal again
Jan 14, 15:39 GMT
Monitoring -
We have identified the issue and are currently scaling our systems to resolve this, we are actively monitoring this solution at the moment.
Jan 14, 14:58 GMT
Update -
We are continuing to investigate this issue.
Jan 14, 14:39 GMT
Investigating -
We are currently investigating this issue.
Jan 14, 14:39 GMT
Resolved -
Upon investigation, we identified the issue was relating to our database. System performance has since resumed back to normal, and we will continue to monitor this closely. A report will be attached to the incident after further investigation.
Jan 8, 16:46 GMT
Investigating -
We are currently investigating this issue.
Jan 8, 14:53 GMT