Resolved -
This incident has been resolved.
Jun 18, 16:32 BST
Monitoring -
The issue was caused by a node rotation of the underlying infrastructure.
A fix has been implemented and we are monitoring the results.
Jun 18, 15:12 BST
Investigating -
We are currently investigating this issue.
Jun 18, 15:06 BST