ResolvedWe have resolved the issue and are monitoring for any out-of-place activity. We are working on rolling out a mitigation plan in the coming weeks to prevent any issues such as these from arising again.
IdentifiedWe have identified some intermittent errors on some of our webservers and have found the root cause. We are acting to mitigate the issue as fast as possible.
History
Product Availability
99.87%
Past Events
31 May 2016
30 May 2016
No incidents reported.
29 May 2016
No incidents reported.
28 May 2016
No incidents reported.
27 May 2016
ResolvedWe have identified and mitigated the source of the issue and everything should be running correctly again.
InvestigatingWe are having issues with some of our web delivery servers and are investigating.
26 May 2016
No incidents reported.
25 May 2016
No incidents reported.
24 May 2016
No incidents reported.
23 May 2016
No incidents reported.
22 May 2016
No incidents reported.
21 May 2016
No incidents reported.
20 May 2016
No incidents reported.
19 May 2016
No incidents reported.
18 May 2016
No incidents reported.
17 May 2016
ResolvedAt around 19:00 this evening a master database server behind the TwentyThree service failed, and as we were working to bring the service back online we identified a hardware malfunction (on a RAM block) on the server responsible for delivering the service. We quickly tried a quick recovery using the same hardware, but determined within a few minutes that the best viable option was to switch to using new hardware. The switch was made and all service restored at 19:44. During this interim the service was unavailable for a total of 25 minutes.
ResolvedThis incident has been resolved.
IdentifiedWe have identified an issue on a core database server that require the service to be switche to different hardware. This will cause emergency downtime over the next 10 minutes. This page will be kept up to date.
ResolvedAll service has been restored after 16 minutes of effective downtime on the core service. We sincerely apologise for the inconvenience caused.
ResolvedService has been restored to the database servers and we are monitoring server health to ensure everything is running smoothly.
MonitoringA fix has been implemented and we are monitoring the results.
InvestigatingThe TwentyThree service is unavailable due to an outage on a central database server. We're bringing services back online, and expect service to be restored momentarily.
16 May 2016
No incidents reported.
15 May 2016
No incidents reported.
14 May 2016
No incidents reported.
13 May 2016
No incidents reported.
12 May 2016
No incidents reported.
11 May 2016
No incidents reported.
10 May 2016
No incidents reported.
9 May 2016
No incidents reported.
8 May 2016
No incidents reported.
7 May 2016
No incidents reported.
6 May 2016
No incidents reported.
5 May 2016
No incidents reported.
4 May 2016
No incidents reported.
3 May 2016
No incidents reported.
2 May 2016
No incidents reported.
1 May 2016
No incidents reported.
Availability is (seconds up + seconds unmonitored) รท all seconds in the Europe/Copenhagen calendar month; only measured downtime counts against it, Maintenance included.