Current status

History

Product Availability

99.98%

80%90%100%1 Feb6 Feb11 Feb16 Feb21 Feb26 Feb

Past Events

28 Feb 2018

No incidents reported.

27 Feb 2018

No incidents reported.

26 Feb 2018

No incidents reported.

25 Feb 2018

No incidents reported.

24 Feb 2018

No incidents reported.

23 Feb 2018

No incidents reported.

22 Feb 2018

No incidents reported.

21 Feb 2018

No incidents reported.

20 Feb 2018

No incidents reported.

19 Feb 2018

No incidents reported.

18 Feb 2018

MaintenanceScheduled database maintenance

  • CompletedThe updates are completed and full service is restored.

  • CompletedThe scheduled maintenance has been completed.

  • In progressScheduled maintenance has begun as announced and is expected to last for up to two hours. Some features will be working in read-only mode during the upgrade, but expect for the service to be unavailable for intervals during this time.

  • ScheduledWe will be updating of the database systems behind the TwentyThree platform during the night between Saturday Feb 17th and Sunday February 18th. Some features will be working in read-only mode during the upgrade, but expect for the service to be unavailable for intervals during the time between 6am-8am CEST/midnight-2am EST/9pm-11pm PST.

17 Feb 2018

No incidents reported.

16 Feb 2018

No incidents reported.

15 Feb 2018

No incidents reported.

14 Feb 2018

No incidents reported.

13 Feb 2018

No incidents reported.

12 Feb 2018

No incidents reported.

11 Feb 2018

No incidents reported.

10 Feb 2018

No incidents reported.

9 Feb 2018

No incidents reported.

8 Feb 2018

No incidents reported.

7 Feb 2018

No incidents reported.

6 Feb 2018

No incidents reported.

5 Feb 2018

No incidents reported.

4 Feb 2018

No incidents reported.

3 Feb 2018

No incidents reported.

2 Feb 2018

No incidents reported.

1 Feb 2018

Degraded performance on the TwentyThree Platform

  • ResolvedThis incident has been resolved.

  • MonitoringAround 3.08pm CEST we saw an elevated error rate on the core TwentyThree platform. The issue was triggered when one of the front-end web servers responsible for delivering the core service started cycling off- and online. By 3.23pm the core issue was resolved and service restored to normal. For the duration of the incident, most requests were returned correctly to clients, but we apologize for any disturbance and will continue to monitor the service.

  • InvestigatingWe are currently investigating this issue.

Availability is (seconds up + seconds unmonitored) ÷ all seconds in the Europe/Copenhagen calendar month; only measured downtime counts against it, Maintenance included.