ResolvedOn 24th of January between 9:00 and 9:05 UTC the TwentyThree platform responded with latency going up to 25 seconds in some parts of the platform. The higher latency was caused by a large amount of traffic we were receiving at the moment.
We noticed higher load at 8:57 UTC and provisioned more resources to the TwentyThree platform to alleviate the issue.
We will be looking into provisioning more resources to appropriate components of our infrastructure to prevent similar issues in the future.
ResolvedOn 19th of January between 14:56 and 14:58 UTC the TwentyThree platform was not responding. Our users would experience long loading time or getting error screens.
The outage was caused by an update on infrastructure, which disrupted connectivity between components, leading to a disruption of service. The update was previously tested and we did not expect any issues. We will investigate why the update did not go as expected, and adopt changes to prevent similar issues in the future.
21 Jan 2024
No incidents reported.
20 Jan 2024
No incidents reported.
19 Jan 2024
No incidents reported.
18 Jan 2024
No incidents reported.
17 Jan 2024
No incidents reported.
16 Jan 2024
No incidents reported.
15 Jan 2024
No incidents reported.
14 Jan 2024
No incidents reported.
13 Jan 2024
No incidents reported.
12 Jan 2024
No incidents reported.
11 Jan 2024
No incidents reported.
10 Jan 2024
No incidents reported.
9 Jan 2024
No incidents reported.
8 Jan 2024
No incidents reported.
7 Jan 2024
No incidents reported.
6 Jan 2024
No incidents reported.
5 Jan 2024
No incidents reported.
4 Jan 2024
No incidents reported.
3 Jan 2024
No incidents reported.
2 Jan 2024
No incidents reported.
1 Jan 2024
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.