Incidents reported on status page for LeafCAD https://status.leafcad.com/ en https://status.leafcad.com/ Wed, 25 Jun 2025 23:04:27 +0000 https://status.leafcad.com/#053ac2d272978cd57dc497be2459baa3239bca1edf08ac99aeb3bc82d17374aa OnClock Bot recovered https://status.leafcad.com/ Wed, 25 Jun 2025 23:01:27 +0000 https://status.leafcad.com/#053ac2d272978cd57dc497be2459baa3239bca1edf08ac99aeb3bc82d17374aa OnClock Bot went down https://status.leafcad.com/incident/538274 Thu, 10 Apr 2025 01:00:00 +0000 https://status.leafcad.com/incident/538274#ebd1144e33d81bb2c606a6a7f605fdb415795334330660ac19131df29c5038b4 Maintenance completed https://status.leafcad.com/incident/538274 Thu, 10 Apr 2025 01:00:00 +0000 https://status.leafcad.com/incident/538274#ebd1144e33d81bb2c606a6a7f605fdb415795334330660ac19131df29c5038b4 Maintenance completed https://status.leafcad.com/incident/538274 Thu, 10 Apr 2025 00:30:00 -0000 https://status.leafcad.com/incident/538274#e091320411ff86acbb39d0446668d2d776904897d79115e26fd7019b23699439 Phase 2/2 English version below. Un de nos fournisseurs a prévu une maintenance sur ses serveurs pour le 9 avril, ce qui pourrait nous affecter. Ils envisagent deux phases où les serveurs pourraient être impactés. Dans un souci de précaution, nous avons pris la décision d'avertir nos clients au cas où cette maintenance aurait un impact réel sur nous. Pour ces périodes ayant un potentiel impact, notre fournisseur anticipe une indisponibilité des services de 20 minutes. La plage horaire prévue en UTC est de 11:00 à 11:30 et 20:30 à 21:00. --- One of our providers has scheduled maintenance on their servers for April 9th, which could have an impact on us. They anticipate two phases where servers may be affected. As a precautionary measure, we have decided to warn our customers in case this maintenance actually impacts us. Our provider expects a 20-minute downtime for each of those impacting phases. The expected timeframe in UTC is 11:00-11:30 and 20:30-21:00. https://status.leafcad.com/incident/538274 Thu, 10 Apr 2025 00:30:00 -0000 https://status.leafcad.com/incident/538274#e091320411ff86acbb39d0446668d2d776904897d79115e26fd7019b23699439 Phase 2/2 English version below. Un de nos fournisseurs a prévu une maintenance sur ses serveurs pour le 9 avril, ce qui pourrait nous affecter. Ils envisagent deux phases où les serveurs pourraient être impactés. Dans un souci de précaution, nous avons pris la décision d'avertir nos clients au cas où cette maintenance aurait un impact réel sur nous. Pour ces périodes ayant un potentiel impact, notre fournisseur anticipe une indisponibilité des services de 20 minutes. La plage horaire prévue en UTC est de 11:00 à 11:30 et 20:30 à 21:00. --- One of our providers has scheduled maintenance on their servers for April 9th, which could have an impact on us. They anticipate two phases where servers may be affected. As a precautionary measure, we have decided to warn our customers in case this maintenance actually impacts us. Our provider expects a 20-minute downtime for each of those impacting phases. The expected timeframe in UTC is 11:00-11:30 and 20:30-21:00. https://status.leafcad.com/incident/538272 Wed, 09 Apr 2025 11:30:00 +0000 https://status.leafcad.com/incident/538272#d3fd74ce7652fc9e5182b2d2e03fd8f033d86bea648255f9bbd6a00d85193206 Maintenance completed https://status.leafcad.com/incident/538272 Wed, 09 Apr 2025 11:30:00 +0000 https://status.leafcad.com/incident/538272#d3fd74ce7652fc9e5182b2d2e03fd8f033d86bea648255f9bbd6a00d85193206 Maintenance completed https://status.leafcad.com/incident/538272 Wed, 09 Apr 2025 11:00:00 -0000 https://status.leafcad.com/incident/538272#8f9cba93c4e7d2fc3896829522828e3b98e4fe52d216a0115a7c429157c8700c Phase 1/2 English version below. Un de nos fournisseurs a prévu une maintenance sur ses serveurs pour le 9 avril, ce qui pourrait nous affecter. Ils envisagent deux phases où les serveurs pourraient être impactés. Dans un souci de précaution, nous avons pris la décision d'avertir nos clients au cas où cette maintenance aurait un impact réel sur nous. Pour ces périodes ayant un potentiel impact, notre fournisseur anticipe une indisponibilité des services de 20 minutes. La plage horaire prévue en UTC est de 11:00 à 11:30 et 20:30 à 21:00. --- One of our providers has scheduled maintenance on their servers for April 9th, which could have an impact on us. They anticipate two phases where servers may be affected. As a precautionary measure, we have decided to warn our customers in case this maintenance actually impacts us. Our provider expects a 20-minute downtime for each of those impacting phases. The expected timeframe in UTC is 11:00-11:30 and 20:30-21:00. https://status.leafcad.com/incident/538272 Wed, 09 Apr 2025 11:00:00 -0000 https://status.leafcad.com/incident/538272#8f9cba93c4e7d2fc3896829522828e3b98e4fe52d216a0115a7c429157c8700c Phase 1/2 English version below. Un de nos fournisseurs a prévu une maintenance sur ses serveurs pour le 9 avril, ce qui pourrait nous affecter. Ils envisagent deux phases où les serveurs pourraient être impactés. Dans un souci de précaution, nous avons pris la décision d'avertir nos clients au cas où cette maintenance aurait un impact réel sur nous. Pour ces périodes ayant un potentiel impact, notre fournisseur anticipe une indisponibilité des services de 20 minutes. La plage horaire prévue en UTC est de 11:00 à 11:30 et 20:30 à 21:00. --- One of our providers has scheduled maintenance on their servers for April 9th, which could have an impact on us. They anticipate two phases where servers may be affected. As a precautionary measure, we have decided to warn our customers in case this maintenance actually impacts us. Our provider expects a 20-minute downtime for each of those impacting phases. The expected timeframe in UTC is 11:00-11:30 and 20:30-21:00. https://status.leafcad.com/incident/536154 Fri, 28 Mar 2025 21:00:00 +0000 https://status.leafcad.com/incident/536154#b704b3b3486a64583b3ef31388be00b293543d1510f44d0af90dcdbfca596cc6 Maintenance completed https://status.leafcad.com/incident/536154 Fri, 28 Mar 2025 21:00:00 +0000 https://status.leafcad.com/incident/536154#b704b3b3486a64583b3ef31388be00b293543d1510f44d0af90dcdbfca596cc6 Maintenance completed https://status.leafcad.com/incident/536154 Fri, 28 Mar 2025 21:00:00 +0000 https://status.leafcad.com/incident/536154#b704b3b3486a64583b3ef31388be00b293543d1510f44d0af90dcdbfca596cc6 Maintenance completed https://status.leafcad.com/incident/536154 Fri, 28 Mar 2025 18:15:00 -0000 https://status.leafcad.com/incident/536154#fc551bbe36c6fefd95fd945d6423087e68c6d97b425f4bb298b15d3ea1d5393a We are migrating our database to another provider. It is unlikely that you will be impacted. https://status.leafcad.com/incident/536154 Fri, 28 Mar 2025 18:15:00 -0000 https://status.leafcad.com/incident/536154#fc551bbe36c6fefd95fd945d6423087e68c6d97b425f4bb298b15d3ea1d5393a We are migrating our database to another provider. It is unlikely that you will be impacted. https://status.leafcad.com/incident/536154 Fri, 28 Mar 2025 18:15:00 -0000 https://status.leafcad.com/incident/536154#fc551bbe36c6fefd95fd945d6423087e68c6d97b425f4bb298b15d3ea1d5393a We are migrating our database to another provider. It is unlikely that you will be impacted. https://status.leafcad.com/incident/519375 Wed, 26 Feb 2025 14:15:00 -0000 https://status.leafcad.com/incident/519375#c1edf07f96f0eedd7336a628147252881bbe91ba05664e56c52673fff744e014 Our DNS provider has resolved the issue. We apologize for any inconvenience this may have caused. https://status.leafcad.com/incident/519375 Wed, 26 Feb 2025 14:03:00 -0000 https://status.leafcad.com/incident/519375#c806efb2903cfe4dd63dbe5d0a33aaa54667ba3f2c388ce2585b38583a1ef5be Our DNS provider has published a status update informing us that their technical team is working to fix the issue. You may or may not be affected if your DNS server has received the proper IPs. https://status.leafcad.com/incident/519375 Wed, 26 Feb 2025 13:56:00 -0000 https://status.leafcad.com/incident/519375#6ec4af7e69078c3963a90c6ad6c360910d3e968ae886f9abd3b9e30b673d10bd We are investigating the problem. It seems that our IP address is no longer shared with DNS servers worldwide. https://status.leafcad.com/incident/498391 Tue, 21 Jan 2025 04:00:00 +0000 https://status.leafcad.com/incident/498391#c56a40741eee40424ad44fa544a4e54d301b24c760af06e08a5c79dcb70406bb Maintenance completed https://status.leafcad.com/incident/498391 Tue, 21 Jan 2025 04:00:00 +0000 https://status.leafcad.com/incident/498391#c56a40741eee40424ad44fa544a4e54d301b24c760af06e08a5c79dcb70406bb Maintenance completed https://status.leafcad.com/incident/498391 Tue, 21 Jan 2025 04:00:00 +0000 https://status.leafcad.com/incident/498391#c56a40741eee40424ad44fa544a4e54d301b24c760af06e08a5c79dcb70406bb Maintenance completed https://status.leafcad.com/incident/498391 Tue, 21 Jan 2025 02:00:00 -0000 https://status.leafcad.com/incident/498391#10c060774c91573b0d7aa0a2ba4aee2307c2e628bbee7a9bd352c3af40b7948a With the MDT coming out very soon, we must change our infrastructure to handle the new features that will be available. There shouldn't be any downtime. https://status.leafcad.com/incident/498391 Tue, 21 Jan 2025 02:00:00 -0000 https://status.leafcad.com/incident/498391#10c060774c91573b0d7aa0a2ba4aee2307c2e628bbee7a9bd352c3af40b7948a With the MDT coming out very soon, we must change our infrastructure to handle the new features that will be available. There shouldn't be any downtime. https://status.leafcad.com/incident/498391 Tue, 21 Jan 2025 02:00:00 -0000 https://status.leafcad.com/incident/498391#10c060774c91573b0d7aa0a2ba4aee2307c2e628bbee7a9bd352c3af40b7948a With the MDT coming out very soon, we must change our infrastructure to handle the new features that will be available. There shouldn't be any downtime. https://status.leafcad.com/incident/400919 Sat, 20 Jul 2024 02:55:00 -0000 https://status.leafcad.com/incident/400919#637ce7269ac26f5c78254afec7f56d5674a70f74b4ec2413bdbf204ef2c91f11 The issue has been resolved, we apologize for the inconvenience. https://status.leafcad.com/incident/400919 Sat, 20 Jul 2024 02:49:00 -0000 https://status.leafcad.com/incident/400919#c70cd066a62e2936d9dab746a012f6d05ece0e1507a03b89d4885b8d4fba97c0 We have identified the problem and a fix is being deployed https://status.leafcad.com/incident/400919 Sat, 20 Jul 2024 02:42:00 -0000 https://status.leafcad.com/incident/400919#13a46952ea0b44dc82594c6ebd7d3a7a33085947ce2de4ee1c4dd78458421dca We are aware of the bug making the bot unresponsive, we're working on it. https://status.leafcad.com/incident/392769 Wed, 03 Jul 2024 01:14:00 -0000 https://status.leafcad.com/incident/392769#a26f546762a242f6bad08b4ce8141a79dc851c024b62ba4b7c56cc15488f175c A fix has been deployed, and the issue with the bot has now been resolved. Thank you for your patience. --- Un correctif a été déployé et le problème avec le bot est maintenant résolu. Merci pour votre patience. https://status.leafcad.com/incident/392769 Wed, 03 Jul 2024 01:06:00 -0000 https://status.leafcad.com/incident/392769#86acefb155e8db0f5528667febf813965252082ce72b7167df6e0439ec8f99d5 We have identified the issue and found a solution for the Bot command problem that arose during a recent Discord update. A temporary solution will be implemented while we wait for Discord to fix the bug. --- Nous avons trouvé le problème et nous avons trouvé une solution pour le problème de commandes du Bot, problème soulevé lors d'une mise à jour Discord dernièrement. Une solution temporaire sera appliquée en attendant que Discord règle le bug. https://status.leafcad.com/incident/392769 Wed, 03 Jul 2024 00:42:00 -0000 https://status.leafcad.com/incident/392769#8571754e1469faebd6eacda2a28b4fcbd97074de6e61ee3bb88664a638de6013 We are aware that the bot is having trouble receiving commands. We currently are searching for the cause. --- Nous sommes conscients du problème lié aux commandes envoyées au Bot. Nous sommes présentement à la recherche de la cause. https://status.leafcad.com/incident/389843 Thu, 27 Jun 2024 16:00:00 +0000 https://status.leafcad.com/incident/389843#83ac2c12c038ecd3c7a101a38023ae548ffa924f71935bb351785f3b4bae6122 Maintenance completed https://status.leafcad.com/incident/389843 Thu, 27 Jun 2024 16:00:00 +0000 https://status.leafcad.com/incident/389843#83ac2c12c038ecd3c7a101a38023ae548ffa924f71935bb351785f3b4bae6122 Maintenance completed https://status.leafcad.com/incident/389843 Thu, 27 Jun 2024 14:50:53 -0000 https://status.leafcad.com/incident/389843#c66baf0af246d476748b077a3062c6c67d76ff8bc9f98607d6f5695e5b55514a On June 27, we will be performing an update to our API and databases from 9:00 EDT to 11:00 EDT. You may notice some short delays, we apologize. https://status.leafcad.com/incident/389843 Thu, 27 Jun 2024 14:50:53 -0000 https://status.leafcad.com/incident/389843#c66baf0af246d476748b077a3062c6c67d76ff8bc9f98607d6f5695e5b55514a On June 27, we will be performing an update to our API and databases from 9:00 EDT to 11:00 EDT. You may notice some short delays, we apologize. https://status.leafcad.com/incident/389843 Thu, 27 Jun 2024 13:00:00 -0000 https://status.leafcad.com/incident/389843#c66baf0af246d476748b077a3062c6c67d76ff8bc9f98607d6f5695e5b55514a On June 27, we will be performing an update to our API and databases from 9:00 EDT to 11:00 EDT. You may notice some short delays, we apologize. https://status.leafcad.com/incident/389843 Thu, 27 Jun 2024 13:00:00 -0000 https://status.leafcad.com/incident/389843#c66baf0af246d476748b077a3062c6c67d76ff8bc9f98607d6f5695e5b55514a On June 27, we will be performing an update to our API and databases from 9:00 EDT to 11:00 EDT. You may notice some short delays, we apologize. https://status.leafcad.com/incident/389794 Wed, 26 Jun 2024 15:56:26 -0000 https://status.leafcad.com/incident/389794#78cdfe785ab9fc72b512449d301bb3f4b22117d2d51340de275bfeaf0f67ed87 We are performing an important update to our API and databases. You may notice some delays, we appologize. https://status.leafcad.com/incident/389794 Wed, 26 Jun 2024 15:56:26 -0000 https://status.leafcad.com/incident/389794#78cdfe785ab9fc72b512449d301bb3f4b22117d2d51340de275bfeaf0f67ed87 We are performing an important update to our API and databases. You may notice some delays, we appologize. https://status.leafcad.com/incident/389794 Wed, 26 Jun 2024 15:00:00 +0000 https://status.leafcad.com/incident/389794#7084286fc6b4a40644c7e4ab265d5c9f94faa09f5c765ba463561c2b2d74631d Maintenance completed https://status.leafcad.com/incident/389794 Wed, 26 Jun 2024 15:00:00 +0000 https://status.leafcad.com/incident/389794#7084286fc6b4a40644c7e4ab265d5c9f94faa09f5c765ba463561c2b2d74631d Maintenance completed https://status.leafcad.com/incident/389794 Wed, 26 Jun 2024 13:46:41 -0000 https://status.leafcad.com/incident/389794#78cdfe785ab9fc72b512449d301bb3f4b22117d2d51340de275bfeaf0f67ed87 We are performing an important update to our API and databases. You may notice some delays, we appologize. https://status.leafcad.com/incident/389794 Wed, 26 Jun 2024 13:46:41 -0000 https://status.leafcad.com/incident/389794#78cdfe785ab9fc72b512449d301bb3f4b22117d2d51340de275bfeaf0f67ed87 We are performing an important update to our API and databases. You may notice some delays, we appologize. https://status.leafcad.com/incident/389794 Wed, 26 Jun 2024 13:30:00 -0000 https://status.leafcad.com/incident/389794#78cdfe785ab9fc72b512449d301bb3f4b22117d2d51340de275bfeaf0f67ed87 We are performing an important update to our API and databases. You may notice some delays, we appologize. https://status.leafcad.com/incident/389794 Wed, 26 Jun 2024 13:30:00 -0000 https://status.leafcad.com/incident/389794#78cdfe785ab9fc72b512449d301bb3f4b22117d2d51340de275bfeaf0f67ed87 We are performing an important update to our API and databases. You may notice some delays, we appologize. https://status.leafcad.com/incident/340094 Thu, 14 Mar 2024 15:00:00 +0000 https://status.leafcad.com/incident/340094#ef37dbb014aa818be4260b7ed898e3d632844ff53913d25ea7ddf1458da0b56d Maintenance completed https://status.leafcad.com/incident/340094 Thu, 14 Mar 2024 15:00:00 +0000 https://status.leafcad.com/incident/340094#ef37dbb014aa818be4260b7ed898e3d632844ff53913d25ea7ddf1458da0b56d Maintenance completed https://status.leafcad.com/incident/340094 Thu, 14 Mar 2024 15:00:00 +0000 https://status.leafcad.com/incident/340094#ef37dbb014aa818be4260b7ed898e3d632844ff53913d25ea7ddf1458da0b56d Maintenance completed https://status.leafcad.com/incident/340094 Thu, 14 Mar 2024 12:00:00 -0000 https://status.leafcad.com/incident/340094#4c09bc1ae71d9004d998ca3516985d853f4dbe873ed89437a0390391e3e99ac1 We will migrate our database from our current provider to a new one. The migration shouldn't take long and be fairly simple, but we reserved a wide window to ensure everything meets our standards. This window should affect only a very small number of users. Any data saved before March 14th, 8:00 am is going to be transferred. Data generated between the start and the end of the migration might not be transferred properly. Please contact us if that is the case. https://status.leafcad.com/incident/340094 Thu, 14 Mar 2024 12:00:00 -0000 https://status.leafcad.com/incident/340094#4c09bc1ae71d9004d998ca3516985d853f4dbe873ed89437a0390391e3e99ac1 We will migrate our database from our current provider to a new one. The migration shouldn't take long and be fairly simple, but we reserved a wide window to ensure everything meets our standards. This window should affect only a very small number of users. Any data saved before March 14th, 8:00 am is going to be transferred. Data generated between the start and the end of the migration might not be transferred properly. Please contact us if that is the case. https://status.leafcad.com/incident/340094 Thu, 14 Mar 2024 12:00:00 -0000 https://status.leafcad.com/incident/340094#4c09bc1ae71d9004d998ca3516985d853f4dbe873ed89437a0390391e3e99ac1 We will migrate our database from our current provider to a new one. The migration shouldn't take long and be fairly simple, but we reserved a wide window to ensure everything meets our standards. This window should affect only a very small number of users. Any data saved before March 14th, 8:00 am is going to be transferred. Data generated between the start and the end of the migration might not be transferred properly. Please contact us if that is the case. https://status.leafcad.com/incident/299344 Tue, 12 Dec 2023 16:20:38 -0000 https://status.leafcad.com/incident/299344#7d669b615f80cb1d4844c70345581f33699a5403a5ab3454288facf24d2281fa We are performing an update to the API and the Bot to support the new statistics https://status.leafcad.com/incident/299344 Tue, 12 Dec 2023 16:20:38 -0000 https://status.leafcad.com/incident/299344#7d669b615f80cb1d4844c70345581f33699a5403a5ab3454288facf24d2281fa We are performing an update to the API and the Bot to support the new statistics https://status.leafcad.com/incident/299344 Tue, 12 Dec 2023 16:20:38 +0000 https://status.leafcad.com/incident/299344#1a21539fbeb4869aa7654e79a00b690429cd35d35b12894f43c8ad4bd716762f Maintenance completed https://status.leafcad.com/incident/299344 Tue, 12 Dec 2023 16:20:38 +0000 https://status.leafcad.com/incident/299344#1a21539fbeb4869aa7654e79a00b690429cd35d35b12894f43c8ad4bd716762f Maintenance completed https://status.leafcad.com/incident/299344 Tue, 12 Dec 2023 16:15:21 -0000 https://status.leafcad.com/incident/299344#7d669b615f80cb1d4844c70345581f33699a5403a5ab3454288facf24d2281fa We are performing an update to the API and the Bot to support the new statistics https://status.leafcad.com/incident/299344 Tue, 12 Dec 2023 16:15:21 -0000 https://status.leafcad.com/incident/299344#7d669b615f80cb1d4844c70345581f33699a5403a5ab3454288facf24d2281fa We are performing an update to the API and the Bot to support the new statistics https://status.leafcad.com/incident/299344 Tue, 12 Dec 2023 15:57:19 -0000 https://status.leafcad.com/incident/299344#7d669b615f80cb1d4844c70345581f33699a5403a5ab3454288facf24d2281fa We are performing an update to the API and the Bot to support the new statistics https://status.leafcad.com/incident/299344 Tue, 12 Dec 2023 15:57:19 -0000 https://status.leafcad.com/incident/299344#7d669b615f80cb1d4844c70345581f33699a5403a5ab3454288facf24d2281fa We are performing an update to the API and the Bot to support the new statistics https://status.leafcad.com/incident/299344 Tue, 12 Dec 2023 15:55:00 -0000 https://status.leafcad.com/incident/299344#7d669b615f80cb1d4844c70345581f33699a5403a5ab3454288facf24d2281fa We are performing an update to the API and the Bot to support the new statistics https://status.leafcad.com/incident/299344 Tue, 12 Dec 2023 15:55:00 -0000 https://status.leafcad.com/incident/299344#7d669b615f80cb1d4844c70345581f33699a5403a5ab3454288facf24d2281fa We are performing an update to the API and the Bot to support the new statistics https://status.leafcad.com/incident/262764 Fri, 22 Sep 2023 04:32:00 -0000 https://status.leafcad.com/incident/262764#9cd843fd0f2f9e4ace7ac1b9c151b6cb9ecd543856a4d8a977b08128c940ea83 All commands made from 20h onwards have not been recorded in the database. We are sorry for this inconvenience. The app, API and bot are back up and running. The host change will be attempted again this week during less busy hours. --- Toutes les commandes effectuées à partir de 20h n’ont pas été enregistrées dans la base de données. Nous sommes désolés pour ce désagrément. L'application, l'API et le bot sont de nouveau fonctionnels. Le changement d'hébergeur sera retenté cette semaine dans des heures moins achalandées. https://status.leafcad.com/incident/262764 Fri, 22 Sep 2023 04:32:00 -0000 https://status.leafcad.com/incident/262764#9cd843fd0f2f9e4ace7ac1b9c151b6cb9ecd543856a4d8a977b08128c940ea83 All commands made from 20h onwards have not been recorded in the database. We are sorry for this inconvenience. The app, API and bot are back up and running. The host change will be attempted again this week during less busy hours. --- Toutes les commandes effectuées à partir de 20h n’ont pas été enregistrées dans la base de données. Nous sommes désolés pour ce désagrément. L'application, l'API et le bot sont de nouveau fonctionnels. Le changement d'hébergeur sera retenté cette semaine dans des heures moins achalandées. https://status.leafcad.com/incident/262764 Fri, 22 Sep 2023 04:32:00 -0000 https://status.leafcad.com/incident/262764#9cd843fd0f2f9e4ace7ac1b9c151b6cb9ecd543856a4d8a977b08128c940ea83 All commands made from 20h onwards have not been recorded in the database. We are sorry for this inconvenience. The app, API and bot are back up and running. The host change will be attempted again this week during less busy hours. --- Toutes les commandes effectuées à partir de 20h n’ont pas été enregistrées dans la base de données. Nous sommes désolés pour ce désagrément. L'application, l'API et le bot sont de nouveau fonctionnels. Le changement d'hébergeur sera retenté cette semaine dans des heures moins achalandées. https://status.leafcad.com/incident/262764 Fri, 22 Sep 2023 04:18:00 -0000 https://status.leafcad.com/incident/262764#f703af88b99720c2af564b52c435bd083a5369a6ea9f18fc0967104601e73c4d Reverting the database to the old provider. This should be successfully done in 5 minutes. --- Retour à l’ancien fournisseur. Cela devrait être effectué avec succès dans environ 5 minutes. https://status.leafcad.com/incident/262764 Fri, 22 Sep 2023 04:18:00 -0000 https://status.leafcad.com/incident/262764#f703af88b99720c2af564b52c435bd083a5369a6ea9f18fc0967104601e73c4d Reverting the database to the old provider. This should be successfully done in 5 minutes. --- Retour à l’ancien fournisseur. Cela devrait être effectué avec succès dans environ 5 minutes. https://status.leafcad.com/incident/262764 Fri, 22 Sep 2023 04:18:00 -0000 https://status.leafcad.com/incident/262764#f703af88b99720c2af564b52c435bd083a5369a6ea9f18fc0967104601e73c4d Reverting the database to the old provider. This should be successfully done in 5 minutes. --- Retour à l’ancien fournisseur. Cela devrait être effectué avec succès dans environ 5 minutes. https://status.leafcad.com/incident/262764 Fri, 22 Sep 2023 03:38:00 -0000 https://status.leafcad.com/incident/262764#be389e6c36870fca19bc213535da19ab66ca37d41f99687b37910a5862109d27 All requests on /OnClock command end up with a 500 error code. We are currently investigating this issue. This seems to be linked from the database host change done today. --- Toutes les demandes avec la commande /OnClock se terminent par un code d’erreur 500. Nous étudions actuellement ce problème. Cela semble lié au changement d’hôte de base de données effectué aujourd’hui. https://status.leafcad.com/incident/262764 Fri, 22 Sep 2023 03:38:00 -0000 https://status.leafcad.com/incident/262764#be389e6c36870fca19bc213535da19ab66ca37d41f99687b37910a5862109d27 All requests on /OnClock command end up with a 500 error code. We are currently investigating this issue. This seems to be linked from the database host change done today. --- Toutes les demandes avec la commande /OnClock se terminent par un code d’erreur 500. Nous étudions actuellement ce problème. Cela semble lié au changement d’hôte de base de données effectué aujourd’hui. https://status.leafcad.com/incident/262764 Fri, 22 Sep 2023 03:38:00 -0000 https://status.leafcad.com/incident/262764#be389e6c36870fca19bc213535da19ab66ca37d41f99687b37910a5862109d27 All requests on /OnClock command end up with a 500 error code. We are currently investigating this issue. This seems to be linked from the database host change done today. --- Toutes les demandes avec la commande /OnClock se terminent par un code d’erreur 500. Nous étudions actuellement ce problème. Cela semble lié au changement d’hôte de base de données effectué aujourd’hui. https://status.leafcad.com/incident/260929 Thu, 21 Sep 2023 22:45:00 +0000 https://status.leafcad.com/incident/260929#b5335c101cf64a263a77606c7e0b68d46f3b7b64a24b76e06558c04f0bbae300 Maintenance completed https://status.leafcad.com/incident/260929 Thu, 21 Sep 2023 17:00:00 -0000 https://status.leafcad.com/incident/260929#794d865b0614babc374bf6f8260c59241ea2d9ebca2817cf1ab9b4baa746061a ###*(Message en français disponible plus bas)* #Summary Primary server will be affected by this maintenance, this means that the OnClock API will not accept any requests during phase 1 and 3. To mitigate the impact on our customers, the database will be temporarily transferred to our dev server for the first and second phases. Performance could be affected during these phases on traffic peaks but the app, API and bot will be available. #First phase In the first phase, the main server will be offline and no new data will be saved and an error will show up on the app during this time. This should take 10 to 15 minutes to complete. We will be moving the latest data to the dev server. #Second phase During this phase, OnClock will be available at a lower performance. Modifications on the main server will be made during this time. Estimated time for this phase is 2 to 4 hours. Performance degradation will not be visible at all time but could be seen in traffic peaks. #Third phase The main server is now ready to host back OnClock. OnClock will now be back offline during this phase, allowing transfer of new data in the second phase back to the main server. Estimated time for this phase is 15 minutes. #Final phase All OnClock components should now be back online as usual and performances should be optimal. During this phase, we will be monitoring the new changes on the main server. ---- #Sommaire Le serveur principal sera affecté par cette maintenance, ce qui signifie que l’API OnClock n’acceptera aucune demande pendant les phases 1 et 3. Pour atténuer l’impact sur nos clients, la base de données sera temporairement transférée à notre serveur de développement pour la première et deuxième phase. Les performances pourraient être affectées pendant ces phases lors des pics de trafic, mais l’application, l’API et le bot seront disponibles. #Première phase Dans la première phase, le serveur principal sera hors ligne et tous les sites Web et applications hébergés seront indisponibles. Cela devrait prendre de 10 à 15 minutes. Les dernières données des sites Web et des applications seront transférées temporairement vers le serveur de développement. #Deuxième phase Au cours de cette phase, OnClock sera disponible à des performances inférieures. Des modifications seront apportées sur le serveur principal pendant cette période. Le temps estimé pour cette phase est de 2 à 4 heures. La dégradation des performances ne sera pas visible en tout temps, mais pourrait être observée dans les pics de trafic. #Troisième phase Le serveur principal est maintenant prêt à héberger OnClock. OnClock sera de nouveau hors ligne pendant cette phase, permettant le transfert des nouvelles données de la deuxième phase vers le serveur principal. Le temps estimé pour cette phase est de 15 minutes. #Phase finale Tous les composants OnClock devraient maintenant être de retour en ligne comme d’habitude et les performances devraient être optimales. Au cours de cette phase, nous surveillerons les nouveaux changements sur le serveur principal. https://status.leafcad.com/incident/257959 Tue, 12 Sep 2023 18:24:46 +0000 https://status.leafcad.com/incident/257959#ec25c78f8b63fbb835a7d52f3b48ee82b46f5ed3527519d29d4f6236d38414ac Maintenance completed https://status.leafcad.com/incident/257959 Tue, 12 Sep 2023 18:24:46 -0000 https://status.leafcad.com/incident/257959#060d2f4320cde641dfcc5c8faeba592b470050539d1fb093601b1313e862088e We are going to push a new update, no downtime should not be noticable. https://status.leafcad.com/incident/257959 Tue, 12 Sep 2023 18:24:46 +0000 https://status.leafcad.com/incident/257959#ec25c78f8b63fbb835a7d52f3b48ee82b46f5ed3527519d29d4f6236d38414ac Maintenance completed https://status.leafcad.com/incident/257959 Tue, 12 Sep 2023 18:24:46 -0000 https://status.leafcad.com/incident/257959#060d2f4320cde641dfcc5c8faeba592b470050539d1fb093601b1313e862088e We are going to push a new update, no downtime should not be noticable. https://status.leafcad.com/incident/257959 Tue, 12 Sep 2023 18:20:50 -0000 https://status.leafcad.com/incident/257959#060d2f4320cde641dfcc5c8faeba592b470050539d1fb093601b1313e862088e We are going to push a new update, no downtime should not be noticable. https://status.leafcad.com/incident/257959 Tue, 12 Sep 2023 18:20:50 -0000 https://status.leafcad.com/incident/257959#060d2f4320cde641dfcc5c8faeba592b470050539d1fb093601b1313e862088e We are going to push a new update, no downtime should not be noticable. https://status.leafcad.com/incident/257959 Tue, 12 Sep 2023 18:00:00 -0000 https://status.leafcad.com/incident/257959#060d2f4320cde641dfcc5c8faeba592b470050539d1fb093601b1313e862088e We are going to push a new update, no downtime should not be noticable. https://status.leafcad.com/incident/257959 Tue, 12 Sep 2023 18:00:00 -0000 https://status.leafcad.com/incident/257959#060d2f4320cde641dfcc5c8faeba592b470050539d1fb093601b1313e862088e We are going to push a new update, no downtime should not be noticable. https://status.leafcad.com/incident/235915 Sat, 22 Jul 2023 13:30:00 +0000 https://status.leafcad.com/incident/235915#ead8e65d1fd29bc48abe1ced960c86d7fa7bf5b28beba85c7bec821afd5ec936 Maintenance completed https://status.leafcad.com/incident/235915 Sat, 22 Jul 2023 13:30:00 +0000 https://status.leafcad.com/incident/235915#ead8e65d1fd29bc48abe1ced960c86d7fa7bf5b28beba85c7bec821afd5ec936 Maintenance completed https://status.leafcad.com/incident/235915 Sat, 22 Jul 2023 13:30:00 +0000 https://status.leafcad.com/incident/235915#ead8e65d1fd29bc48abe1ced960c86d7fa7bf5b28beba85c7bec821afd5ec936 Maintenance completed https://status.leafcad.com/incident/235915 Sat, 22 Jul 2023 11:52:04 -0000 https://status.leafcad.com/incident/235915#f720d3185a48fb6f99eef8ddf570e65fb1b94cab9281f351d826f80f9c6f8156 We will be performing an overnight infrastructure migration. We will have to point our DNS to our new server and while the DNS servers are updating, the API will not be reachable. Once the switch is complete, we will finish the deployment and migrate traffic of the bot onto the new server. https://status.leafcad.com/incident/235915 Sat, 22 Jul 2023 11:52:04 -0000 https://status.leafcad.com/incident/235915#f720d3185a48fb6f99eef8ddf570e65fb1b94cab9281f351d826f80f9c6f8156 We will be performing an overnight infrastructure migration. We will have to point our DNS to our new server and while the DNS servers are updating, the API will not be reachable. Once the switch is complete, we will finish the deployment and migrate traffic of the bot onto the new server. https://status.leafcad.com/incident/235915 Sat, 22 Jul 2023 11:52:04 -0000 https://status.leafcad.com/incident/235915#f720d3185a48fb6f99eef8ddf570e65fb1b94cab9281f351d826f80f9c6f8156 We will be performing an overnight infrastructure migration. We will have to point our DNS to our new server and while the DNS servers are updating, the API will not be reachable. Once the switch is complete, we will finish the deployment and migrate traffic of the bot onto the new server. https://status.leafcad.com/incident/235915 Sat, 22 Jul 2023 11:00:00 -0000 https://status.leafcad.com/incident/235915#f720d3185a48fb6f99eef8ddf570e65fb1b94cab9281f351d826f80f9c6f8156 We will be performing an overnight infrastructure migration. We will have to point our DNS to our new server and while the DNS servers are updating, the API will not be reachable. Once the switch is complete, we will finish the deployment and migrate traffic of the bot onto the new server. https://status.leafcad.com/incident/235915 Sat, 22 Jul 2023 11:00:00 -0000 https://status.leafcad.com/incident/235915#f720d3185a48fb6f99eef8ddf570e65fb1b94cab9281f351d826f80f9c6f8156 We will be performing an overnight infrastructure migration. We will have to point our DNS to our new server and while the DNS servers are updating, the API will not be reachable. Once the switch is complete, we will finish the deployment and migrate traffic of the bot onto the new server. https://status.leafcad.com/incident/235915 Sat, 22 Jul 2023 11:00:00 -0000 https://status.leafcad.com/incident/235915#f720d3185a48fb6f99eef8ddf570e65fb1b94cab9281f351d826f80f9c6f8156 We will be performing an overnight infrastructure migration. We will have to point our DNS to our new server and while the DNS servers are updating, the API will not be reachable. Once the switch is complete, we will finish the deployment and migrate traffic of the bot onto the new server. https://status.leafcad.com/incident/233966 Mon, 17 Jul 2023 16:42:00 -0000 https://status.leafcad.com/incident/233966#2f08bc7be9839056eaf07ec2ba8bdb004d9cdace5b243ecc8c60d51af518cf61 The issues have been resolved. We are monitoring for other errors, OnClock should be fully available. The downtime and the previous ones were caused by a bad authentication token submitted by a client. We had a bug were we didn't escape this error properly and it would crash the entire API. We apologize for the inconvenience and we will make sure this doesn't happen again. https://status.leafcad.com/incident/233966 Mon, 17 Jul 2023 16:42:00 -0000 https://status.leafcad.com/incident/233966#2f08bc7be9839056eaf07ec2ba8bdb004d9cdace5b243ecc8c60d51af518cf61 The issues have been resolved. We are monitoring for other errors, OnClock should be fully available. The downtime and the previous ones were caused by a bad authentication token submitted by a client. We had a bug were we didn't escape this error properly and it would crash the entire API. We apologize for the inconvenience and we will make sure this doesn't happen again. https://status.leafcad.com/incident/233966 Mon, 17 Jul 2023 16:42:00 -0000 https://status.leafcad.com/incident/233966#2f08bc7be9839056eaf07ec2ba8bdb004d9cdace5b243ecc8c60d51af518cf61 The issues have been resolved. We are monitoring for other errors, OnClock should be fully available. The downtime and the previous ones were caused by a bad authentication token submitted by a client. We had a bug were we didn't escape this error properly and it would crash the entire API. We apologize for the inconvenience and we will make sure this doesn't happen again. https://status.leafcad.com/incident/233966 Mon, 17 Jul 2023 16:23:00 -0000 https://status.leafcad.com/incident/233966#ef2d36fbde1ac0a330011321af8c54e9ed1663bd3c14eb6469afb9d0e4e5f26a API is working again, but the bot doesn't recognize it. We are working on fixing this. https://status.leafcad.com/incident/233966 Mon, 17 Jul 2023 16:23:00 -0000 https://status.leafcad.com/incident/233966#ef2d36fbde1ac0a330011321af8c54e9ed1663bd3c14eb6469afb9d0e4e5f26a API is working again, but the bot doesn't recognize it. We are working on fixing this. https://status.leafcad.com/incident/233966 Mon, 17 Jul 2023 16:23:00 -0000 https://status.leafcad.com/incident/233966#ef2d36fbde1ac0a330011321af8c54e9ed1663bd3c14eb6469afb9d0e4e5f26a API is working again, but the bot doesn't recognize it. We are working on fixing this. https://status.leafcad.com/incident/233966 Mon, 17 Jul 2023 15:20:00 -0000 https://status.leafcad.com/incident/233966#6d41f0b595b95d4bb3226fb916e3ec75f2586c307a07821c24fbae90fa789713 Our API is crashing over and over. We are investigating and have created a fix to solve this issue. https://status.leafcad.com/incident/233966 Mon, 17 Jul 2023 15:20:00 -0000 https://status.leafcad.com/incident/233966#6d41f0b595b95d4bb3226fb916e3ec75f2586c307a07821c24fbae90fa789713 Our API is crashing over and over. We are investigating and have created a fix to solve this issue. https://status.leafcad.com/incident/233966 Mon, 17 Jul 2023 15:20:00 -0000 https://status.leafcad.com/incident/233966#6d41f0b595b95d4bb3226fb916e3ec75f2586c307a07821c24fbae90fa789713 Our API is crashing over and over. We are investigating and have created a fix to solve this issue. https://status.leafcad.com/incident/220686 Fri, 16 Jun 2023 19:34:21 +0000 https://status.leafcad.com/incident/220686#07a1647a1a27412ef5925891dac86f626a622de4bc3c219eea95e2ab2e779ca5 Maintenance completed https://status.leafcad.com/incident/220686 Fri, 16 Jun 2023 19:34:21 -0000 https://status.leafcad.com/incident/220686#5f6f2e91bd06c194f5a57cae1447821abef6e0fc11684ccdf7532938e376b09d # Summary We are planing a maintenance window to perform some changes regarding our URL scheme. We will be deploying a new landing page and moving the web application under /app. We are also introducing the https://onclock.xyz domain. A maintenance window of one hour and a half (1h30) has been scheduled, but we are confident it will require us less time. # Steps The update will be separated into three stages. ## First Stage Update to our DNS records to point our two domains on the new landing page. While the DNS update is underway, we will deploy the web application with it's new path. This transition should be seamless and shouldn't affect your community as the bot will still be fully working. If something prevents us from going forward, we can rollback easily. Once the app is deployed on its new path, **you won't be able to log in until the migration is complete**. ## Second Stage We need to update our edge router to handle incoming traffic from the new domain. This configuration is sensitive and is harder to rollback as we have to do it manually. Up to this point, you shouldn't notice any problem with the bot as it relies on internal networking to communicate with the API. ## Third stage This finale stage requires us to restart the API to updates it settings to recognize the new domain and properly redirect logins to the new path for the app. Although this restart should be quick, if you make any commands using the bot or use the app while this is happening, you will experience timeouts and error messages. https://status.leafcad.com/incident/220686 Fri, 16 Jun 2023 19:34:21 +0000 https://status.leafcad.com/incident/220686#07a1647a1a27412ef5925891dac86f626a622de4bc3c219eea95e2ab2e779ca5 Maintenance completed https://status.leafcad.com/incident/220686 Fri, 16 Jun 2023 19:34:21 -0000 https://status.leafcad.com/incident/220686#5f6f2e91bd06c194f5a57cae1447821abef6e0fc11684ccdf7532938e376b09d # Summary We are planing a maintenance window to perform some changes regarding our URL scheme. We will be deploying a new landing page and moving the web application under /app. We are also introducing the https://onclock.xyz domain. A maintenance window of one hour and a half (1h30) has been scheduled, but we are confident it will require us less time. # Steps The update will be separated into three stages. ## First Stage Update to our DNS records to point our two domains on the new landing page. While the DNS update is underway, we will deploy the web application with it's new path. This transition should be seamless and shouldn't affect your community as the bot will still be fully working. If something prevents us from going forward, we can rollback easily. Once the app is deployed on its new path, **you won't be able to log in until the migration is complete**. ## Second Stage We need to update our edge router to handle incoming traffic from the new domain. This configuration is sensitive and is harder to rollback as we have to do it manually. Up to this point, you shouldn't notice any problem with the bot as it relies on internal networking to communicate with the API. ## Third stage This finale stage requires us to restart the API to updates it settings to recognize the new domain and properly redirect logins to the new path for the app. Although this restart should be quick, if you make any commands using the bot or use the app while this is happening, you will experience timeouts and error messages. https://status.leafcad.com/incident/220686 Fri, 16 Jun 2023 19:18:57 -0000 https://status.leafcad.com/incident/220686#5f6f2e91bd06c194f5a57cae1447821abef6e0fc11684ccdf7532938e376b09d # Summary We are planing a maintenance window to perform some changes regarding our URL scheme. We will be deploying a new landing page and moving the web application under /app. We are also introducing the https://onclock.xyz domain. A maintenance window of one hour and a half (1h30) has been scheduled, but we are confident it will require us less time. # Steps The update will be separated into three stages. ## First Stage Update to our DNS records to point our two domains on the new landing page. While the DNS update is underway, we will deploy the web application with it's new path. This transition should be seamless and shouldn't affect your community as the bot will still be fully working. If something prevents us from going forward, we can rollback easily. Once the app is deployed on its new path, **you won't be able to log in until the migration is complete**. ## Second Stage We need to update our edge router to handle incoming traffic from the new domain. This configuration is sensitive and is harder to rollback as we have to do it manually. Up to this point, you shouldn't notice any problem with the bot as it relies on internal networking to communicate with the API. ## Third stage This finale stage requires us to restart the API to updates it settings to recognize the new domain and properly redirect logins to the new path for the app. Although this restart should be quick, if you make any commands using the bot or use the app while this is happening, you will experience timeouts and error messages. https://status.leafcad.com/incident/220686 Fri, 16 Jun 2023 19:18:57 -0000 https://status.leafcad.com/incident/220686#5f6f2e91bd06c194f5a57cae1447821abef6e0fc11684ccdf7532938e376b09d # Summary We are planing a maintenance window to perform some changes regarding our URL scheme. We will be deploying a new landing page and moving the web application under /app. We are also introducing the https://onclock.xyz domain. A maintenance window of one hour and a half (1h30) has been scheduled, but we are confident it will require us less time. # Steps The update will be separated into three stages. ## First Stage Update to our DNS records to point our two domains on the new landing page. While the DNS update is underway, we will deploy the web application with it's new path. This transition should be seamless and shouldn't affect your community as the bot will still be fully working. If something prevents us from going forward, we can rollback easily. Once the app is deployed on its new path, **you won't be able to log in until the migration is complete**. ## Second Stage We need to update our edge router to handle incoming traffic from the new domain. This configuration is sensitive and is harder to rollback as we have to do it manually. Up to this point, you shouldn't notice any problem with the bot as it relies on internal networking to communicate with the API. ## Third stage This finale stage requires us to restart the API to updates it settings to recognize the new domain and properly redirect logins to the new path for the app. Although this restart should be quick, if you make any commands using the bot or use the app while this is happening, you will experience timeouts and error messages. https://status.leafcad.com/incident/220686 Fri, 16 Jun 2023 18:45:00 -0000 https://status.leafcad.com/incident/220686#5f6f2e91bd06c194f5a57cae1447821abef6e0fc11684ccdf7532938e376b09d # Summary We are planing a maintenance window to perform some changes regarding our URL scheme. We will be deploying a new landing page and moving the web application under /app. We are also introducing the https://onclock.xyz domain. A maintenance window of one hour and a half (1h30) has been scheduled, but we are confident it will require us less time. # Steps The update will be separated into three stages. ## First Stage Update to our DNS records to point our two domains on the new landing page. While the DNS update is underway, we will deploy the web application with it's new path. This transition should be seamless and shouldn't affect your community as the bot will still be fully working. If something prevents us from going forward, we can rollback easily. Once the app is deployed on its new path, **you won't be able to log in until the migration is complete**. ## Second Stage We need to update our edge router to handle incoming traffic from the new domain. This configuration is sensitive and is harder to rollback as we have to do it manually. Up to this point, you shouldn't notice any problem with the bot as it relies on internal networking to communicate with the API. ## Third stage This finale stage requires us to restart the API to updates it settings to recognize the new domain and properly redirect logins to the new path for the app. Although this restart should be quick, if you make any commands using the bot or use the app while this is happening, you will experience timeouts and error messages. https://status.leafcad.com/incident/220686 Fri, 16 Jun 2023 18:45:00 -0000 https://status.leafcad.com/incident/220686#5f6f2e91bd06c194f5a57cae1447821abef6e0fc11684ccdf7532938e376b09d # Summary We are planing a maintenance window to perform some changes regarding our URL scheme. We will be deploying a new landing page and moving the web application under /app. We are also introducing the https://onclock.xyz domain. A maintenance window of one hour and a half (1h30) has been scheduled, but we are confident it will require us less time. # Steps The update will be separated into three stages. ## First Stage Update to our DNS records to point our two domains on the new landing page. While the DNS update is underway, we will deploy the web application with it's new path. This transition should be seamless and shouldn't affect your community as the bot will still be fully working. If something prevents us from going forward, we can rollback easily. Once the app is deployed on its new path, **you won't be able to log in until the migration is complete**. ## Second Stage We need to update our edge router to handle incoming traffic from the new domain. This configuration is sensitive and is harder to rollback as we have to do it manually. Up to this point, you shouldn't notice any problem with the bot as it relies on internal networking to communicate with the API. ## Third stage This finale stage requires us to restart the API to updates it settings to recognize the new domain and properly redirect logins to the new path for the app. Although this restart should be quick, if you make any commands using the bot or use the app while this is happening, you will experience timeouts and error messages.