Thanks for your patience whilst we fixed this. We're now closing the incident.
Posted Jul 07, 2015 - 14:14 BST
Update
We continue to monitor this situation, but we believe service has returned to normal.
Posted Jul 07, 2015 - 13:37 BST
Monitoring
We've isolated the affected database server and removed it from service, so for approximately 30 minutes now the service has been operating as normal. We're moving this incident to monitoring status now whilst we keep a close eye. Thanks for bearing with us.
Posted Jul 07, 2015 - 13:08 BST
Update
We're still working to resolve this - we'll provide an update in the next 30 minutes or sooner.
Posted Jul 07, 2015 - 12:40 BST
Identified
We've identified the problem and are expecting it to be resolved shortly. In the meantime, if you see slightly outdated data, please either refresh until you see the correct information, or preferably hold off until this problem is fixed.
Note that no data is lost/reverted, users are seeing a slightly outdated version of data for some operations. This will correct itself. We'll update again in the next half hour or sooner. Thanks for your patience.
Posted Jul 07, 2015 - 12:22 BST
Investigating
Some users are reporting seeing cached/outdated data. We're looking into this right now.