Incidents reported on status page for Leapsome GmbH https://status.leapsome.tech/ https://d1lppblt9t2x15.cloudfront.net/logos/b272876dda80209681287b5472269e24.png https://status.leapsome.tech/ en https://status.leapsome.tech/ Tue, 03 Jun 2025 14:37:37 +0000 https://status.leapsome.tech/#d9091a8d89484a8cfe4662f61bf18b5e40dc49e6d00dcba517a14ee6be083455 Leapsome APIs recovered https://status.leapsome.tech/ Tue, 03 Jun 2025 14:35:37 +0000 https://status.leapsome.tech/#d9091a8d89484a8cfe4662f61bf18b5e40dc49e6d00dcba517a14ee6be083455 Leapsome APIs went down https://status.leapsome.tech/ Tue, 18 Mar 2025 09:48:09 +0000 https://status.leapsome.tech/#1c3ad002297e42a8dacd2cbcbc1732fc1ee1e965995607ebce3267b02e2db8bb Leapsome APIs recovered https://status.leapsome.tech/ Tue, 18 Mar 2025 09:46:08 +0000 https://status.leapsome.tech/#1c3ad002297e42a8dacd2cbcbc1732fc1ee1e965995607ebce3267b02e2db8bb Leapsome APIs went down https://status.leapsome.tech/incident/529656 Mon, 17 Mar 2025 17:55:00 -0000 https://status.leapsome.tech/incident/529656#24c24e68ac49fb3697321338a08b6a6207b59b780eab095c1dd5c689ba4fe493 All services remain operational and no additional performance degradation was observed after our initial fixes got deployed. We are closing this incident as fully resolved now. https://status.leapsome.tech/incident/529656 Mon, 17 Mar 2025 14:28:00 -0000 https://status.leapsome.tech/incident/529656#ba828d73d27f1581f0d0a19a4efe7cd26d5b2e75cd1f749892bbc0d94259e39d The team disabled application maintenance mode after stabilising all services. We continue to monitor and mitigate slowness of individual APIs but the Leapsome application is back to regular operations. https://status.leapsome.tech/incident/529656 Mon, 17 Mar 2025 14:20:00 -0000 https://status.leapsome.tech/incident/529656#38d5537b3f47212e8e4a3b94008d5aa8699382daf365130bd3692e458128cc8d We are seeing degraded API performance across the platform. The teams started to investigate and might be required to go into an unscheduled maintenance mode for a brief period to allow full system recovery. https://status.leapsome.tech/incident/529688 Mon, 17 Mar 2025 09:23:00 -0000 https://status.leapsome.tech/incident/529688#f06576188b697616c33c2f56f7530d189cbd790e7cf49771a3e2df161eebab34 All services recovered and the processing queue is back to regular load after catching up with pending tasks. https://status.leapsome.tech/incident/529688 Mon, 17 Mar 2025 09:05:00 -0000 https://status.leapsome.tech/incident/529688#a42d2944406df3e6161c1a6227c7475b853d19450c75ae3b7aab88defb5ee452 While deploying a fix to mitigate the performance overhead the team is required to force restart certain services which will result in processing queue build-up and a short period of downtime for specific module operations. https://status.leapsome.tech/incident/529688 Mon, 17 Mar 2025 08:40:00 -0000 https://status.leapsome.tech/incident/529688#46bad0cfb2c839edaa30de792041d1ced1971d5563089f93d50459a7f2642659 The team started investigating API response times that are below our usual service level objectives for individual modules. https://status.leapsome.tech/ Thu, 13 Mar 2025 13:28:28 +0000 https://status.leapsome.tech/#09c43dad5403f26293e183e6213a6d65252c8d869a4f4b92ae77ddfb36523128 Leapsome APIs recovered https://status.leapsome.tech/ Thu, 13 Mar 2025 13:23:22 +0000 https://status.leapsome.tech/#09c43dad5403f26293e183e6213a6d65252c8d869a4f4b92ae77ddfb36523128 Leapsome APIs went down https://status.leapsome.tech/ Fri, 07 Mar 2025 17:11:05 +0000 https://status.leapsome.tech/#79928ad11663afc67d2f9c7488cbab7690655eaf13c65244be2b6a893e62e09e Leapsome APIs recovered https://status.leapsome.tech/ Fri, 07 Mar 2025 17:06:05 +0000 https://status.leapsome.tech/#79928ad11663afc67d2f9c7488cbab7690655eaf13c65244be2b6a893e62e09e Leapsome APIs went down https://status.leapsome.tech/incident/498808 Wed, 22 Jan 2025 18:30:00 -0000 https://status.leapsome.tech/incident/498808#bb756c033d81fb431c83874d6c7a6ede04eca440508818e0aa5d4dd4da61bdc0 *Incident Summary & Timeline* On January 20, 2025, starting at 14:47 CET, our platform experienced a major disruption when a malfunction in an AWS infrastructure process blocked auto-scaling, hardware rotation, and deployment tasks. Our monitoring and alerting systems worked as intended, notifying our on-call team promptly. However, because our usual rapid-response mechanisms were unavailable, the team performed manual intervention and a partial rebuild of key infrastructure components in parallel to restore operations. Full services were reactivated by 16:25 CET. *Maintenance Mode* To protect data integrity and maintain system reliability, we placed the platform in maintenance mode once it became clear a quick fix was not feasible. A status page link on the maintenance screen informed about updates while we worked on the repairs. *Recovery & Post‐Maintenance* Even after resolving the primary issue, we had to process a backlog of tasks that had accumulated during the downtime. This required traffic shaping, cluster/service scaling, and other performance optimisations, resulting in slower response times for up to 45 minutes following service restoration. We prioritised minimising any impact on your workflows, and all systems returned to normal shortly thereafter. *Looking Ahead* We continue to refine our infrastructure configurations and will maintain a full standby environment to allow for swifter recovery in the future and when regular procedures fail. In addition, we’re coordinating closely with AWS to prevent a repeat of these issues. We appreciate your patience and partnership as we focus on providing a performant and robust platform for your employees. https://status.leapsome.tech/incident/498808 Mon, 20 Jan 2025 15:34:00 -0000 https://status.leapsome.tech/incident/498808#3987d30b62478cba20ad8a16e88e685a2ff32ec3f290222a5ed0c1f326324eab Our platform has been restored after experiencing a complex infrastructure incident that required Leapsome to go into unplanned maintenance mode. We understand this disruption impacted your operations and sincerely apologize for any inconvenience caused. We continue to monitor the situation. https://status.leapsome.tech/incident/498808 Mon, 20 Jan 2025 15:01:00 -0000 https://status.leapsome.tech/incident/498808#4b15663ef36cf699b24b9ca9f1870dfd5b249004378e751627364e5766e78474 We want to inform you that we continue experiencing some technical difficulties with parts of our infrastructure. Our team is working diligently to resolve the issue as quickly as possible and ensure everything is back to normal soon. We deeply apologize for any inconvenience this may cause and appreciate your understanding and patience. We’ll provide updates as they become available. https://status.leapsome.tech/incident/498808 Mon, 20 Jan 2025 14:08:00 -0000 https://status.leapsome.tech/incident/498808#a95757e2bed69b36deaab8478d49a5e1167ff8b3080a72f831f2a3bf21544f10 The team investigating decided to move the platform into a temporary maintenance mode to ensure data integrity and accelerate system recovery. https://status.leapsome.tech/incident/498808 Mon, 20 Jan 2025 13:55:00 -0000 https://status.leapsome.tech/incident/498808#bb65af12355a720351f99c3d6698b22b59c6f7fd468d306aa98babe646820a63 We are aware of individual customers experiencing degraded platform performance and internal teams started to investigate. https://status.leapsome.tech/ Tue, 12 Nov 2024 23:23:06 +0000 https://status.leapsome.tech/#aef2751a8917b2e32ae7579be560297d3b082c420d0b147c15c2e96e86e951d7 Leapsome APIs recovered https://status.leapsome.tech/ Tue, 12 Nov 2024 23:21:06 +0000 https://status.leapsome.tech/#aef2751a8917b2e32ae7579be560297d3b082c420d0b147c15c2e96e86e951d7 Leapsome APIs went down https://status.leapsome.tech/ Mon, 21 Oct 2024 13:31:30 +0000 https://status.leapsome.tech/#88aa11ccafcb01f94eff5f10d0050ba09ad8d292b791f05752197900f6addc0a Leapsome APIs recovered https://status.leapsome.tech/ Mon, 21 Oct 2024 13:29:29 +0000 https://status.leapsome.tech/#88aa11ccafcb01f94eff5f10d0050ba09ad8d292b791f05752197900f6addc0a Leapsome APIs went down https://status.leapsome.tech/incident/302895 Wed, 20 Dec 2023 12:48:00 -0000 https://status.leapsome.tech/incident/302895#a56306ff1890058a149c90487beacb6fad4df319aa33a193a358881b77a0cf3b We are back online and performance issues are resolved completely. We have experienced an(other) issue with our database provider, which is unfortunately out of our direct control. Together with our provider, we're continuing to monitor the situation and working on a durable safeguard. Our highest priority to continue to provide the platform stability you are used to. https://status.leapsome.tech/incident/302895 Wed, 20 Dec 2023 11:50:00 -0000 https://status.leapsome.tech/incident/302895#0ac8a7c19d6241fc430a9ab7989ccff4ee3b781068abccf6db71cba4de8207c4 We could resolve issues together with our upstream provider and continue to bring back services slowly. https://status.leapsome.tech/incident/302895 Wed, 20 Dec 2023 11:03:00 -0000 https://status.leapsome.tech/incident/302895#eb1254f077931df4c0334729286f88f5b6888518c7b7e35a7cd8230844c557be We are working with one of our upstream providers to resolve a critical issue in our database engine that triggered this incident. https://status.leapsome.tech/incident/302895 Wed, 20 Dec 2023 10:30:00 -0000 https://status.leapsome.tech/incident/302895#9ed0f2c689e78817beb3b9f046032b3824a92f8e020831b009735d0b806292f3 The initial issue was identified but triggered a chain reaction of connected services. We are working on a recovery of all affected systems and have to put Leapsome into maintenance mode temporarily. https://status.leapsome.tech/incident/302895 Wed, 20 Dec 2023 10:24:00 -0000 https://status.leapsome.tech/incident/302895#c41ea7837fcc8f0648293d9ee2f2ea9856804003563f5df3da9edf753a86fefa Our teams were notified about degraded platform performance automatically and we are investigating with highest priority. https://status.leapsome.tech/incident/300989 Fri, 15 Dec 2023 15:40:00 -0000 https://status.leapsome.tech/incident/300989#7867dd6339bf9818c4d34b821fd5a289d737476bebc55f29107a6c9749973f27 The application is back online which had the highest priority for the teams. We continue to work with our upstream provider and tackling the root cause that lead to this outage. https://status.leapsome.tech/incident/300989 Fri, 15 Dec 2023 14:55:00 -0000 https://status.leapsome.tech/incident/300989#35182776dd798e1cdff4d6adf4b2565a5d3c9730771f45ce2d1cf8ab3d2adf4f We are working with one of our upstream infrastructure providers to resolve this issue. https://status.leapsome.tech/incident/300989 Fri, 15 Dec 2023 14:38:00 -0000 https://status.leapsome.tech/incident/300989#dc9be6923e5ae3f0339f4bb2b16c54e5e84664cf45053a7b2bb375bb8b4b3a88 We are investigating degraded application performance for most tenants. https://status.leapsome.tech/incident/291186 Thu, 23 Nov 2023 13:56:00 -0000 https://status.leapsome.tech/incident/291186#7b777468f0fb164322b6fde86dae6cd2098b4770941c973a1789be1d2d520b1b All services have been fully restored. https://status.leapsome.tech/incident/291186 Thu, 23 Nov 2023 13:44:00 -0000 https://status.leapsome.tech/incident/291186#a6ae83ee9091076af33a38d7bd3e505e660e84a5a92902d7f96b294647a8d8f0 We recovered multiple systems and fixed the root cause with one of our upstream providers. The main application is running and our teams monitor the stability. Scheduled notifications, jobs and workflows will resume processing shortly. https://status.leapsome.tech/incident/291186 Thu, 23 Nov 2023 13:22:00 -0000 https://status.leapsome.tech/incident/291186#e08d9fa95c74a1da9e9696817a10989665ef8900a09086873394ae18f411c845 The fix is taking longer than expected originally and covers multiple systems. It is the top priority for the teams to recover services for all customers. As soon as we have a concrete ETA, we will share it on our status page. https://status.leapsome.tech/incident/291186 Thu, 23 Nov 2023 12:15:00 -0000 https://status.leapsome.tech/incident/291186#162b31a87d3546428f5f1e5e1e1e9cd508a3045c93b801e1f0f9713e628e7a0b The relevant team identified the root cause and is preparing a fix to stabilise the environment for all tenants. https://status.leapsome.tech/incident/291186 Thu, 23 Nov 2023 12:02:00 -0000 https://status.leapsome.tech/incident/291186#7179088609419392b0618742d7110aedd23576e8be9825ccf590e337583df6ab We identified an unexpected failure on one of our core API's. The team is investigating and moved the main application into maintenance mode. We'll share updates as soon as they become available. https://status.leapsome.tech/incident/236674 Mon, 24 Jul 2023 10:30:00 -0000 https://status.leapsome.tech/incident/236674#712ef1fa77835b7a5675209a67601ed0fd9e0b938a1b34d9a6ef4e4ed003e487 Performance is recovering for affected tenants after the team identified the cause and deployed a fix. https://status.leapsome.tech/incident/236674 Mon, 24 Jul 2023 10:10:00 -0000 https://status.leapsome.tech/incident/236674#4244fc45a36378bc4db2b8f077ed5480a0cd046083e00f88f39fdd54eadc85be We are investigating bursts of short platform performance degradations where load times appear slower than usual for some tenants.