Incidents reported on status page for EcoZend https://status.ecozend.cloud/ en https://status.ecozend.cloud/incident/775521 Sat, 06 Dec 2025 23:00:56 -0000 https://status.ecozend.cloud/incident/775521#02a9f9e9c2e0aea7f52f41134cca7a482aa1a8a7d2baa27e74f719157902c09b Maintenance completed https://status.ecozend.cloud/incident/775521 Fri, 05 Dec 2025 23:00:56 -0000 https://status.ecozend.cloud/incident/775521#522ea2b6234f244cef8f5fa7b5cd567d64f67c7b28da46d4c69a21e1e0c1aafe I will most likely be making major changes to EcoZend's infrastructure over those two days. These changes include a server provider switch as well as major changes to how EcoZend is operated, started, maintained and so on. These changes allow EcoZend to operate more cost-effectively while also delivering more performance. However, a long downtime is highly likely, but we are trying to make plans to prevent this as much as possible. https://status.ecozend.cloud/ Tue, 02 Dec 2025 18:25:40 +0000 https://status.ecozend.cloud/#1b379d500d052d167e587db92edd5fa0cd0c96893480cf07df112d48689e76d3 EcoZend API Status recovered https://status.ecozend.cloud/ Tue, 02 Dec 2025 18:15:45 +0000 https://status.ecozend.cloud/#1b379d500d052d167e587db92edd5fa0cd0c96893480cf07df112d48689e76d3 EcoZend API Status went down https://status.ecozend.cloud/ Thu, 27 Nov 2025 22:05:36 +0000 https://status.ecozend.cloud/#667965ae21b683f3d43998bde52faeb7aa04763ca433809de37fff2282bc0053 EcoZend API Status recovered https://status.ecozend.cloud/incident/775490 Thu, 27 Nov 2025 22:05:00 -0000 https://status.ecozend.cloud/incident/775490#0dac41f06ac29a4d31fabdfd5d1134d1c1226ad46c9b9d4f41ddf616d0b8b7ef The Issue is now resolved. I'm extremely Sorry for this long Downtime. I did some System Updates and due to some very unknown and weird reasons our Docker instances booted p everything except the EcoZend ones. And due to another outage I didn't realized that in fact EcoZend is down too. I've learned from this outage and I promise such a long Outage won't happen ever again. https://status.ecozend.cloud/ Thu, 27 Nov 2025 16:25:32 +0000 https://status.ecozend.cloud/#667965ae21b683f3d43998bde52faeb7aa04763ca433809de37fff2282bc0053 EcoZend API Status went down https://status.ecozend.cloud/incident/775490 Thu, 27 Nov 2025 16:25:00 -0000 https://status.ecozend.cloud/incident/775490#289044b0c4121305c130ac3fbc6fde5c9239cc2896c404cd43a0ec5ae3121b07 EcoZend is replying with 503 https://status.ecozend.cloud/ Fri, 21 Nov 2025 22:25:35 +0000 https://status.ecozend.cloud/#ba4e7a54df8fe125ee6feb09a6da2f45dbd36aa41ffa3a1768f9fc8b666827f2 EcoZend API Status recovered https://status.ecozend.cloud/ Fri, 21 Nov 2025 22:10:41 +0000 https://status.ecozend.cloud/#ba4e7a54df8fe125ee6feb09a6da2f45dbd36aa41ffa3a1768f9fc8b666827f2 EcoZend API Status went down https://status.ecozend.cloud/ Mon, 20 Oct 2025 09:45:52 +0000 https://status.ecozend.cloud/#89e4dbcf8a96d6fe937adf866c4c1cebfcd9711d0b5a9f27bafdcd56bec286f8 Mail Server recovered https://status.ecozend.cloud/ Mon, 20 Oct 2025 09:26:11 +0000 https://status.ecozend.cloud/#89e4dbcf8a96d6fe937adf866c4c1cebfcd9711d0b5a9f27bafdcd56bec286f8 Mail Server went down https://status.ecozend.cloud/incident/744315 Wed, 15 Oct 2025 21:03:00 -0000 https://status.ecozend.cloud/incident/744315#79e54e3f710981f7fec5990420e56663ad944ec6d1c0033d36034a4944f47b07 The issue had been resolved. There was another Issue going which required a restart of the EcoZend Systems which is the Reason this Incident had been set to Downtime. https://status.ecozend.cloud/incident/744315 Wed, 15 Oct 2025 20:28:00 -0000 https://status.ecozend.cloud/incident/744315#f5cfc16346b8252df58903838997027fd3617b97c90f742f7ace7e2f4392d38f Our CDN Provider is intercepting the connection trying to create a secure connection. We're working on it.... https://status.ecozend.cloud/incident/744303 Wed, 15 Oct 2025 20:28:00 -0000 https://status.ecozend.cloud/incident/744303#6c799ca95e002bb098754fb02d93a023eb0a9ed76fcc3bb84018bdd9ab33ede5 This issue should be resolved now. https://status.ecozend.cloud/incident/744303 Wed, 15 Oct 2025 20:18:00 -0000 https://status.ecozend.cloud/incident/744303#a74d7dbb8deecc5aa6a8bff4acaa79dbc7ce8b402a5f57859fd626a06d6ab554 We're currently aware of an issue that makes our Systems not connect with our Database. I'm working on it https://status.ecozend.cloud/ Wed, 15 Oct 2025 07:03:38 +0000 https://status.ecozend.cloud/#0f4e6da954e9a4061973d50a78aadce936082b69ce576982bcbb3a51e1daf3b9 Mail Server recovered https://status.ecozend.cloud/ Wed, 15 Oct 2025 06:58:53 +0000 https://status.ecozend.cloud/#0f4e6da954e9a4061973d50a78aadce936082b69ce576982bcbb3a51e1daf3b9 Mail Server went down https://status.ecozend.cloud/ Wed, 01 Oct 2025 04:17:21 +0000 https://status.ecozend.cloud/#f15dee3097a5a435e9e43bc29f5d205ee51341be7eaeb1b75186e79097abb6d2 Mail Server recovered https://status.ecozend.cloud/ Wed, 01 Oct 2025 03:42:17 +0000 https://status.ecozend.cloud/#f15dee3097a5a435e9e43bc29f5d205ee51341be7eaeb1b75186e79097abb6d2 Mail Server went down https://status.ecozend.cloud/ Sun, 21 Sep 2025 21:23:39 +0000 https://status.ecozend.cloud/#aba202990705bdb7290d6daba27130808ac9deaa2e9484e97b2dc41f909cd058 Mail Server recovered https://status.ecozend.cloud/ Sun, 21 Sep 2025 21:19:34 +0000 https://status.ecozend.cloud/#aba202990705bdb7290d6daba27130808ac9deaa2e9484e97b2dc41f909cd058 Mail Server went down https://status.ecozend.cloud/ Sun, 21 Sep 2025 21:03:37 +0000 https://status.ecozend.cloud/#be6b95adb2cf34f5eb7fcc3a89833d51e736082a3da8d1192969eb7118f45a44 Mail Server recovered https://status.ecozend.cloud/ Sun, 21 Sep 2025 20:59:34 +0000 https://status.ecozend.cloud/#be6b95adb2cf34f5eb7fcc3a89833d51e736082a3da8d1192969eb7118f45a44 Mail Server went down https://status.ecozend.cloud/incident/723882 Sun, 14 Sep 2025 02:44:00 -0000 https://status.ecozend.cloud/incident/723882#745f2d9b9ac356d7d238d349e8eea0599793ce9ad96ce26f6107f925413cd79d The problem should be fixed. Restarting the replications worked. https://status.ecozend.cloud/incident/723882 Sun, 14 Sep 2025 02:36:00 -0000 https://status.ecozend.cloud/incident/723882#7f91405382eb6f07f57dafc04146d41d10a180966cd8cc269808ef269df45b4b I restarted the replicas. Let's see how it goes. https://status.ecozend.cloud/incident/723882 Sun, 14 Sep 2025 02:24:00 -0000 https://status.ecozend.cloud/incident/723882#533c0c088d33b45d68f18ecb691de4e664d7e876cbda50f30c7fd4c7bd20b36e I have identified the problem. It involves connection peer resets. I am trying to fix the problem. . https://status.ecozend.cloud/incident/723882 Sun, 14 Sep 2025 01:55:00 -0000 https://status.ecozend.cloud/incident/723882#68f818d602ef352bfc8fb5f487f0796239a750a7e0ffbb92277a05778edd3842 We have been noticing an increased number of missing transactions for some time now. We are currently working to identify and resolve the cause of the problem. https://status.ecozend.cloud/incident/674706 Thu, 31 Jul 2025 15:35:00 -0000 https://status.ecozend.cloud/incident/674706#af7ca74d4cac9f76ee283480aefc30504d2f9ddc5ffe987303ee3c0e9192ff37 Resolved https://status.ecozend.cloud/incident/674706 Thu, 31 Jul 2025 14:40:00 -0000 https://status.ecozend.cloud/incident/674706#80f11e0fa5ab18a048be30295b15f8177d35e7aed4f3d564fae9dd6edadaf374 According to our Heartbeat System, there were isolated problems processing transactions between 4:40 p.m. and 5:35 p.m. today. I have not been able to identify the problem, but will continue to investigate. https://status.ecozend.cloud/incident/601496 Fri, 13 Jun 2025 10:25:00 -0000 https://status.ecozend.cloud/incident/601496#2ed13beeb7c118255e555accd8e609fe4e50217ab1e384a67a15467999cdc127 Maintenance completed https://status.ecozend.cloud/incident/601496 Fri, 13 Jun 2025 09:35:00 -0000 https://status.ecozend.cloud/incident/601496#089c49ecea8605a65ae50833b3bea246e6056e86b60625698f0f3a1ede7bdc5c Our Hosting Provider will carry out software updates. There may be brief outages. https://status.ecozend.cloud/incident/601488 Thu, 12 Jun 2025 11:44:00 -0000 https://status.ecozend.cloud/incident/601488#4e0ea3e4f7c51ae878337be6040d3d2671302899ca20a472eabd9fed37c11e18 Our Service is now running normally again. https://status.ecozend.cloud/incident/601488 Thu, 12 Jun 2025 11:36:00 -0000 https://status.ecozend.cloud/incident/601488#3ad29126be3cdc51cbb7ff030f422648aef0cc4f119a8afb3b0da5472b7bf2df Our hosting provider had to restart some services due to an internal error. https://status.ecozend.cloud/incident/597507 Thu, 05 Jun 2025 10:07:00 -0000 https://status.ecozend.cloud/incident/597507#8d0f360d16c7e3754849b0d941be7ec810916645d3d90680a34544f5b05848db We have now rebuilt the reverse proxy to restore compatibility. The systems should slowly start working again https://status.ecozend.cloud/incident/597507 Thu, 05 Jun 2025 09:48:00 -0000 https://status.ecozend.cloud/incident/597507#1267a3d72ff3bb78a3dac0caa054fe51b7ab388495a4fc8452d4945ae77f4c12 During a security update, a compatibility error occurred which caused the reverse proxy to crash. Our team is working on it https://status.ecozend.cloud/incident/580243 Mon, 26 May 2025 11:11:00 -0000 https://status.ecozend.cloud/incident/580243#958000e48f3e0f4d217198f40b0d0760957ab33bc29bdbed93fcee13dd938840 The error has been fixed. Everything should work again as expected. https://status.ecozend.cloud/incident/580243 Mon, 26 May 2025 10:54:00 -0000 https://status.ecozend.cloud/incident/580243#0d7ec26373b49ccde1f4de1258218c60bc4d26e8ea95ea663f8afc3b062f7f4b We have uploaded a patch and are waiting. https://status.ecozend.cloud/incident/580243 Mon, 26 May 2025 10:00:00 -0000 https://status.ecozend.cloud/incident/580243#8447449554d847e2f96bfda8f5ac9586f1c774e0591f7626fdf39a483857c08f We currently have the problem that wallets cannot be retrieved correctly. Our team is currently working on a fix. https://status.ecozend.cloud/incident/565917 Fri, 16 May 2025 21:30:13 -0000 https://status.ecozend.cloud/incident/565917#f1bd47b17e95e943c10e7f70f0d0463aaf81057069150afd4f7b6d8501cabed3 Maintenance completed https://status.ecozend.cloud/incident/565917 Fri, 16 May 2025 21:00:13 -0000 https://status.ecozend.cloud/incident/565917#632cebba934ec87826a2314a9aa415173d58a75bcc08c0e3d01cbe9605bd694c We will update EcoZend to the latest version (1.1.2) on the specified day. There may be brief outages. https://status.ecozend.cloud/incident/556077 Sun, 04 May 2025 06:18:00 -0000 https://status.ecozend.cloud/incident/556077#21f4386170d325ba700041e0dfc76e135c95a2e655d706e6309bf422c2da86a0 The issue has been fixed https://status.ecozend.cloud/incident/556077 Sun, 04 May 2025 06:18:00 -0000 https://status.ecozend.cloud/incident/556077#21f4386170d325ba700041e0dfc76e135c95a2e655d706e6309bf422c2da86a0 The issue has been fixed https://status.ecozend.cloud/incident/556077 Sun, 04 May 2025 02:19:00 -0000 https://status.ecozend.cloud/incident/556077#fe1c8e2e597ab6d2d5fe6a3def082d5f29ed054b8794b76199ec1be0431caf8d Our Database Provider currently has Database issues https://status.ecozend.cloud/incident/556077 Sun, 04 May 2025 02:19:00 -0000 https://status.ecozend.cloud/incident/556077#fe1c8e2e597ab6d2d5fe6a3def082d5f29ed054b8794b76199ec1be0431caf8d Our Database Provider currently has Database issues https://status.ecozend.cloud/incident/535683 Sun, 06 Apr 2025 21:00:00 -0000 https://status.ecozend.cloud/incident/535683#d68a00fc47dcb99e377f741a10419ed68abe2f52080ac08fdbb6a46f1d58f63d Maintenance completed https://status.ecozend.cloud/incident/535683 Sat, 05 Apr 2025 21:00:00 -0000 https://status.ecozend.cloud/incident/535683#6f2f2ac9f578637933bb52cf4bd07b0a60e3d31f5a33cf17b2b4f40d16a993a6 Read more here: https://status.aki-solutions.net/maintenance/535681 https://status.ecozend.cloud/incident/529014 Fri, 21 Mar 2025 09:23:03 -0000 https://status.ecozend.cloud/incident/529014#f01f13763b528fb0eb137d27e190a562c6ee71040818138098e2da0b6d6c8c2b Maintenance completed https://status.ecozend.cloud/incident/529014 Sun, 16 Mar 2025 08:26:03 -0000 https://status.ecozend.cloud/incident/529014#53583e86da48b81e6adddb7666336d33a28e9a1fa40eb5a6f4c6221dbe67acc8 Due to the fact that our “akami-solutions.cc” domain is currently being transferred to another provider, there may be errors in the delivery of e-mails. We apologize if errors occur. https://status.ecozend.cloud/incident/528729 Sat, 15 Mar 2025 16:50:00 -0000 https://status.ecozend.cloud/incident/528729#dc3ad9014017f723f2d49bb245d416b8cce189ccfd6e3e4ad9145b4bc4201d0b The function of the service should be restored. The reason could have been a Layer7 attack or similar. https://status.ecozend.cloud/incident/528729 Sat, 15 Mar 2025 16:47:00 -0000 https://status.ecozend.cloud/incident/528729#1a54592f02d148f6e72c9961ade3d301700d162f223e7ae4191176379dc1a085 We are currently experiencing a total failure of our server due to a system restart. Due to the fact that our provider has automatically detected an error, we can no longer start the server. Support has been contacted. https://status.ecozend.cloud/incident/518153 Mon, 24 Feb 2025 13:53:00 -0000 https://status.ecozend.cloud/incident/518153#c69c97c8cdeb09ec2221c02e5bbbd6cd712fcc407bc16731fb73aadc98c4363d We were able to find another problem for the outage. The second reason was a faulty update which we have withdrawn for the time being. https://status.ecozend.cloud/incident/518153 Mon, 24 Feb 2025 13:30:00 -0000 https://status.ecozend.cloud/incident/518153#09c1d2c46691d3dfb9c185afe3c45b53df20c2cff79e16902d0bc97be7891782 The error has just been fixed. There were problems with our database. https://status.ecozend.cloud/incident/518153 Mon, 24 Feb 2025 13:23:00 -0000 https://status.ecozend.cloud/incident/518153#238d3588a4fecc80e928ab2aab16dd15250f623e3d3ac6c05e846e9bac7d74f4 We are currently observing serious problems in our API. We are looking into what is going on https://status.ecozend.cloud/incident/515248 Wed, 19 Feb 2025 03:02:00 -0000 https://status.ecozend.cloud/incident/515248#bd86943c3b8fc3eb8fa17460fb1ef405006db1172953b42ba95eff9f27498d58 It turned out that the DNS provider was carrying out maintenance work, which probably led to the temporary outage. https://status.ecozend.cloud/incident/515248 Wed, 19 Feb 2025 02:57:00 -0000 https://status.ecozend.cloud/incident/515248#ee0acb5ea97abcda6bc6b13894251263688d8dc161afec53bc4b6ecefdc450be It looks like there was a problem with the DNS server. We are still investigating whether the problem was with us or with the DNS provider. https://status.ecozend.cloud/incident/515248 Wed, 19 Feb 2025 01:37:00 -0000 https://status.ecozend.cloud/incident/515248#d8a52c421ca9cca1c56de802d9a581483ecaabf93465b7ca9f85d6961b8fbf75 The service seems to be available again. We are still trying to find a reason for this. https://status.ecozend.cloud/incident/515248 Wed, 19 Feb 2025 01:12:00 -0000 https://status.ecozend.cloud/incident/515248#d4f1e6826c6fc4e45a666e4a56d972172caac202f858df04d4200f6926e58b98 Our service was unavailable for a while. We are trying to find out why. https://status.ecozend.cloud/incident/514181 Mon, 17 Feb 2025 09:47:00 -0000 https://status.ecozend.cloud/incident/514181#6f20d5af907514521daaf290d4858113ecb5ef0c231e8dd87b3cc49c3027f6b1 Hosting provider is re-routing... https://status.ecozend.cloud/incident/514181 Mon, 17 Feb 2025 09:32:00 -0000 https://status.ecozend.cloud/incident/514181#73f3b681a4838a7083ff32f908ccf0faba13f171c1b60e524d49d2f3208e5818 There is currently an IPv4 problem at the server provider's data center. https://status.ecozend.cloud/incident/514181 Mon, 17 Feb 2025 07:59:00 -0000 https://status.ecozend.cloud/incident/514181#2feb0e27e93549797cb4ca77f48fd9f465bed210621954daa63e1cb6cf2d0107 Our hosting provider is currently experiencing a major service outage. We are currently waiting for updates. https://status.ecozend.cloud/incident/512712 Fri, 14 Feb 2025 01:07:00 -0000 https://status.ecozend.cloud/incident/512712#5d1fca8b385da1317b7c3906910e5ce6f05df966564acad82142e8ff247bf95f After closer examination, they fear that the Aki Solutions database was unintentionally restarted and thus the connection to the database was interrupted. There is already a fix for this at EcoZend which automatically reconnects to the database, but this will only be rolled out on the next patchday. https://status.ecozend.cloud/incident/512712 Fri, 14 Feb 2025 01:03:00 -0000 https://status.ecozend.cloud/incident/512712#97ac0e2946cb9d2c7631ced5a3c11e62144ea67a33d6754f815407c02da3fc04 We have been alerted by our system that there is currently a problem creating transactions. Our team is looking into this. https://status.ecozend.cloud/incident/512245 Thu, 13 Feb 2025 10:26:00 -0000 https://status.ecozend.cloud/incident/512245#2cc49707210fdc91825d37ffb046f451ddf366128abd748c32713a3ce2ea3cd7 We have deactivated the rule until further notice. https://status.ecozend.cloud/incident/512245 Thu, 13 Feb 2025 09:22:00 -0000 https://status.ecozend.cloud/incident/512245#150192c77146738f37a338a35efe18a0bffbd04f5116b4255b8ed1315d4da294 There is currently a problem that makes it impossible to delete wallets. https://status.ecozend.cloud/incident/489023 Sun, 05 Jan 2025 12:00:42 -0000 https://status.ecozend.cloud/incident/489023#7152702ef6762e0cd962054a8bc8c445a6d2fefb041ebbd9fa7e7ce506c592d3 Maintenance completed https://status.ecozend.cloud/incident/489023 Sun, 05 Jan 2025 08:10:42 -0000 https://status.ecozend.cloud/incident/489023#e942422d398d4269cb95e6cbc70fc96678c2475be6a7fbcbbcf04c3f1af59c2b On 5.1.2024 at 13:00 CET we will make changes to our infrastructure. For this reason there will be a short interruption of the service. Please also note that minor changes and updates are always made on Saturdays and Sundays and we therefore advise against transcations and other interactions with our services as errors may occur. Otherwise our support is always available https://status.ecozend.cloud/incident/461940 Fri, 15 Nov 2024 09:37:00 -0000 https://status.ecozend.cloud/incident/461940#125e085d8dea6b927582b2d022f1e2126f190208578f3b8b81479bd97ee6392a The error has been fixed. https://status.ecozend.cloud/incident/461940 Fri, 15 Nov 2024 09:34:00 -0000 https://status.ecozend.cloud/incident/461940#80bd90d1ac1808b6063d1abfbbc8a0cddcfaf321a2cbe0dbd503a92f53ff91bd We have found the problem and a fix is being rolled out. https://status.ecozend.cloud/incident/461940 Fri, 15 Nov 2024 08:56:00 -0000 https://status.ecozend.cloud/incident/461940#9003a60971d0a19da5b5a16ecc67b86409e2c6d758364039ba5566a990800bfb We have an increased volume of 403 status messages. We are working on a fix. https://status.ecozend.cloud/incident/452484 Fri, 01 Nov 2024 02:00:40 -0000 https://status.ecozend.cloud/incident/452484#4911e3ae6d9d845f648ada30fa2c74d1f576551fbe2628479cef87be7b32ca3a Maintenance completed https://status.ecozend.cloud/incident/452484 Fri, 01 Nov 2024 01:00:40 -0000 https://status.ecozend.cloud/incident/452484#01f9db98f49d2d54338a30065127a7ab868ab1e043dabbe481b1ab32c1b7dd40 On 01.11.2024 at 02:00 CET we will carry out a migration to our database which will mean that no requests can be accepted for a short time. https://status.ecozend.cloud/incident/423397 Wed, 04 Sep 2024 08:00:00 -0000 https://status.ecozend.cloud/incident/423397#1a8509227719913246e1e1d54c076183fa9cb324be019c9ea58326e22f74ad2c Maintenance completed https://status.ecozend.cloud/incident/423397 Wed, 04 Sep 2024 06:00:00 -0000 https://status.ecozend.cloud/incident/423397#0f8e6f103acfe91b474f0a2836d5e55b7260e08b0963452af2bde266d893e091 We make changes to the network information and DNS settings. There may be longer loading times https://status.ecozend.cloud/incident/413725 Wed, 14 Aug 2024 10:33:00 -0000 https://status.ecozend.cloud/incident/413725#a6d772d7121c95f2327fc51443e9c901519eb372f503e0610f4b634b9e961dfe Everything should be fixed now. https://status.ecozend.cloud/incident/413725 Wed, 14 Aug 2024 09:31:00 -0000 https://status.ecozend.cloud/incident/413725#689ea8fddcde8cda9c9eec1934bdc436060356316f1f7032c8f395f83453de6e We're currrently having some issues starting up our API Services on the secondary Host. We're working on a fix. More Informations about the outage can be found here: https://status.akami-solutions.cc/incident/413701 https://status.ecozend.cloud/incident/403723 Thu, 25 Jul 2024 20:28:00 -0000 https://status.ecozend.cloud/incident/403723#a015c2fe3908c8cfd2fb16c7118f03b9804123f5b69e00bb5b45d59f49367ee1 The issue is now fixed and everything should work normal for now on. https://status.ecozend.cloud/incident/403723 Thu, 25 Jul 2024 20:26:00 -0000 https://status.ecozend.cloud/incident/403723#5921eb07965c467d5dfe8f2b65acd6ccb45cfd6b55b40fe7bc4d6e370ca4a8d4 We've implemented a fix for this issue and validating the fix https://status.ecozend.cloud/incident/403723 Thu, 25 Jul 2024 20:17:00 -0000 https://status.ecozend.cloud/incident/403723#f9cb80bd0617869f8744c71e86a3b5f3f3482d8a48297f1438c4373362ef6d74 Wir verfolgen derzeit ein Problem dass das Caching betrifft. https://status.ecozend.cloud/incident/380990 Fri, 07 Jun 2024 13:25:00 -0000 https://status.ecozend.cloud/incident/380990#dae0128e3027248e565cff8b0550ef2cd4b8dd04f65288b698762e51e46090f3 Everything should now work as usual again. https://status.ecozend.cloud/incident/380990 Fri, 07 Jun 2024 12:09:00 -0000 https://status.ecozend.cloud/incident/380990#3682cc4e06a19e16d932ff0839cd62720c77e22341b21dea64bf33dbc69f87ac Please follow the status updates from our server provider. https://status.akami-solutions.cc/incident/380991 https://status.ecozend.cloud/incident/380990 Fri, 07 Jun 2024 11:54:00 -0000 https://status.ecozend.cloud/incident/380990#c41f8da5b94d1a5f42c256386057e0415f60fe19279f8017cd0786ad9e26e5e8 Our server provider is currently experiencing an outage. We are currently working on re-routing https://status.ecozend.cloud/incident/375373 Mon, 27 May 2024 12:30:00 -0000 https://status.ecozend.cloud/incident/375373#64e7f94f9c3964f75f74457b06380f894f1b161eb706a19e4fbe6944e26e2d82 Maintenance completed https://status.ecozend.cloud/incident/375373 Mon, 27 May 2024 11:15:00 -0000 https://status.ecozend.cloud/incident/375373#c98453b8c24ac68e2033ebe431d2678a54fa51e112a206de5eea92d1013f69c7 . https://status.ecozend.cloud/incident/367579 Fri, 10 May 2024 19:30:00 -0000 https://status.ecozend.cloud/incident/367579#d98840c416312e954c44c97c8702d7dc1ebcdb0ec53d3b933f39bc28220d5523 Maintenance completed https://status.ecozend.cloud/incident/367579 Fri, 10 May 2024 18:30:00 -0000 https://status.ecozend.cloud/incident/367579#64499965a7f6f729a8dcea4fc2e427b161fe35638cc873e59c259d56121e3830 On 10.05.2024 we are moving to a different Servercenter. This will cause to a few issues https://status.ecozend.cloud/incident/365375 Mon, 06 May 2024 05:30:00 -0000 https://status.ecozend.cloud/incident/365375#25c0abc5dfe6d7d6d80d29dcdf3441dc49d49c6d8b404d4f131b4c3247c6a39a We have restarted our server.Everything should work again. https://status.ecozend.cloud/incident/365375 Mon, 06 May 2024 05:20:00 -0000 https://status.ecozend.cloud/incident/365375#1c6f6da4e1eb11b80a17c87e319f379a68eaf2b7646c3b2b65844ae375cbba69 We are currently aware that one of our major servers is having problems. We are already in contact with our provider. https://status.ecozend.cloud/incident/361874 Sun, 28 Apr 2024 22:00:00 -0000 https://status.ecozend.cloud/incident/361874#231573c0222f8646bf634c8a1eede02ad379909329f1652cd6386946cd40e4a9 Maintenance completed https://status.ecozend.cloud/incident/361874 Sun, 28 Apr 2024 21:00:00 -0000 https://status.ecozend.cloud/incident/361874#857f25da1647d86a0beb0b40690161e756c7f3db15eb5d306821f7c63a76fc7e Changes are being made to one of our servers https://status.ecozend.cloud/incident/359103 Mon, 22 Apr 2024 13:18:00 -0000 https://status.ecozend.cloud/incident/359103#a7f01dfcbb217185a0847d7436dd0a6c25047afcbaa984f2d52ee8ca7d9cb0b5 We have found the problem and already fixed it. https://status.ecozend.cloud/incident/359103 Mon, 22 Apr 2024 13:05:00 -0000 https://status.ecozend.cloud/incident/359103#4cb12187701e1e8356359bc9b8367900a4996739057a922a83b6e2f69c70a7e2 We are currently experiencing internal server issues. We are currently working on a fix. https://status.ecozend.cloud/incident/357753 Fri, 19 Apr 2024 09:01:00 -0000 https://status.ecozend.cloud/incident/357753#b0e8e3db4a8d29598073beedd4235c2d24cdaf4f5486a1e61946b3c92faafb72 The failure has been fixed. After a software update, the API server was not started. This should now be fixed. https://status.ecozend.cloud/incident/357753 Fri, 19 Apr 2024 07:53:00 -0000 https://status.ecozend.cloud/incident/357753#1c7217d4a50be5d7d3bfbdcd5f54e8a447ca4071cf81e4445a4dd2fab607ae46 We are currently experiencing an outage with our API. Our administration is taking care of it. https://status.ecozend.cloud/incident/356134 Wed, 17 Apr 2024 07:00:00 -0000 https://status.ecozend.cloud/incident/356134#4d3b4c2ba8b3de30a92acf80f93347acdac4eb4633f64b98d2916d74dacf67dd Maintenance completed https://status.ecozend.cloud/incident/356134 Wed, 17 Apr 2024 06:00:00 -0000 https://status.ecozend.cloud/incident/356134#0859c3ac593d9f9bb89095a3fb72a9da32c27fad1b115f48f1a346893de9cb19 We will make changes to our reverse proxy on 17.04.2024 at 08:00. There will be short outages https://status.ecozend.cloud/incident/350052 Mon, 15 Apr 2024 07:30:00 -0000 https://status.ecozend.cloud/incident/350052#0509d98bbe479205936a471fdcd809fcf6e3a88c523a57d7f81dd155f2149778 Maintenance completed https://status.ecozend.cloud/incident/350052 Mon, 15 Apr 2024 06:30:00 -0000 https://status.ecozend.cloud/incident/350052#40576e627c75344c8968e7985a1cf1009a28cef0655010ab9fd629513323309b On 15.04.2024 we will release a new version of the SIWFT API. This new version includes a few new features and bug fixes. It will lead to short outages. https://status.ecozend.cloud/incident/353752 Wed, 10 Apr 2024 20:36:00 -0000 https://status.ecozend.cloud/incident/353752#a27e39192ff394d9bfab328d6f3d8d03c87b4b2b206a3902af1656f6f29d683e The problems have been fixed. We apologise for the downtime! https://status.ecozend.cloud/incident/353752 Wed, 10 Apr 2024 20:23:00 -0000 https://status.ecozend.cloud/incident/353752#a95bfec7ed4a19c456c1401f607f7ee1120d3836e06de0ca172c4d93cf7c5dfe We've implemented a fix. We're investigating the results. https://status.ecozend.cloud/incident/353752 Wed, 10 Apr 2024 19:44:00 -0000 https://status.ecozend.cloud/incident/353752#0d27108d835bb0ec38e36e6fd4653fefcc5b7118a4822a351fd953e4867b4364 We're currently aware of an SSL Handshake error. https://status.ecozend.cloud/incident/351453 Fri, 05 Apr 2024 20:46:00 -0000 https://status.ecozend.cloud/incident/351453#a8f32c02fa47541bf73da0fd9b7b29275969b1d718dfe78dee5d6879567d92f9 We've fixed this issue but we are not sure if there is a data loss. We continue investigate that https://status.ecozend.cloud/incident/351453 Fri, 05 Apr 2024 20:35:00 -0000 https://status.ecozend.cloud/incident/351453#2ebbc8f73ac154dd7bf528f6c52e93fad87302afe05c5cd8cd3a91b1088111c2 We've identified the issue. We are currently working on fixing this issue https://status.ecozend.cloud/incident/351453 Fri, 05 Apr 2024 20:21:00 -0000 https://status.ecozend.cloud/incident/351453#b4e5ae713b668408d26b9fa1eb81c3e702d22730a796f2a393ef74014f3b4ce5 Hello, we are currently experiencing major issues with our Mail Services. We are currently working on it. https://status.ecozend.cloud/incident/345628 Tue, 26 Mar 2024 10:19:29 -0000 https://status.ecozend.cloud/incident/345628#47514542563b7f09bee8727ecbcb7f65e466e68bcdb6614a3cfdce071488887c Maintenance completed https://status.ecozend.cloud/incident/345628 Tue, 26 Mar 2024 08:00:00 -0000 https://status.ecozend.cloud/incident/345628#fd203e2bf8a5ff703e61cb5c8272e1d623762bb173b601bec4a1b733609ea9e0 On 26.03.2024 CET we will carry out maintenance work on our database at 09:00 am. These changes will provide an enhanced layer of protection against attackers and attacks both internal and external. These changes will also improve the speed of the database connection. https://status.ecozend.cloud/incident/345628 Tue, 26 Mar 2024 08:00:00 -0000 https://status.ecozend.cloud/incident/345628#fd203e2bf8a5ff703e61cb5c8272e1d623762bb173b601bec4a1b733609ea9e0 On 26.03.2024 CET we will carry out maintenance work on our database at 09:00 am. These changes will provide an enhanced layer of protection against attackers and attacks both internal and external. These changes will also improve the speed of the database connection. https://status.ecozend.cloud/incident/344160 Thu, 21 Mar 2024 23:41:00 -0000 https://status.ecozend.cloud/incident/344160#72367f19926eb48d2dca3698768f7069da09bbac042610a56b1c8f57966e0d19 We've fixed our Firewall and its now completely functional. There are no limitations anymore https://status.ecozend.cloud/incident/344160 Thu, 21 Mar 2024 16:35:00 -0000 https://status.ecozend.cloud/incident/344160#8ab9caabb3ef6c83ffa68a7b12cb214606b590c882039686fd3ed57320548736 We dont care anymore about that shit. Nobody is using it so we give a fuck on it until tomorrow. https://status.ecozend.cloud/incident/344160 Thu, 21 Mar 2024 15:57:00 -0000 https://status.ecozend.cloud/incident/344160#c73e7cc55d98bd6113ee85763182168c6b9abce3aee31ab9518b9f6558ef2e80 We've fixed this issue but we came into another issue with our SSL certificate. https://status.ecozend.cloud/incident/344160 Thu, 21 Mar 2024 15:49:00 -0000 https://status.ecozend.cloud/incident/344160#ccafb20e430c11fa1f8ebb361516e7c7e9e55902bdc8a11acc821e157589b8f5 We are aware of this issue https://status.ecozend.cloud/incident/344069 Thu, 21 Mar 2024 13:00:00 -0000 https://status.ecozend.cloud/incident/344069#28e7dfda07bd373bb8ab99444c90f6603241b4c5675fc7ea5dd82fea8ebc7641 We've fixed this issue. The issue was a missconfiguration in our Firewall. We are still working on it . https://status.ecozend.cloud/incident/344069 Thu, 21 Mar 2024 12:08:00 -0000 https://status.ecozend.cloud/incident/344069#fa7417e00d13c441547a247cd9266dea96f03de5f8585efebe2884dd65d3010b Our System Administration team was notified. https://status.ecozend.cloud/incident/332326 Fri, 15 Mar 2024 23:00:00 -0000 https://status.ecozend.cloud/incident/332326#b678ada789462f59f7d33ac70b9fc986ba9b00a223b4602229a536e98dd6bbd7 Maintenance completed https://status.ecozend.cloud/incident/332326 Fri, 15 Mar 2024 22:00:00 -0000 https://status.ecozend.cloud/incident/332326#c78039603caf5b3a810cfb7d2225520f919c478ca746fc0c77e70ea0d4c3461f Akami Solutions will perform an update for the SIWFT API on 15.03.2024 at 23 CEST. Due to the fact that there has been a change in the internal building system which simplifies the whole thing, this may lead to outages. We try to keep the backup host up! https://status.ecozend.cloud/incident/331078 Fri, 23 Feb 2024 18:27:00 -0000 https://status.ecozend.cloud/incident/331078#652bcc2010f0e8e3c47c145b524c5964431bd7ea17b7840b3eb3d83db2119e55 We've fixed the Database issue and everything should be up and working from now on. https://status.ecozend.cloud/incident/331078 Fri, 23 Feb 2024 18:00:00 -0000 https://status.ecozend.cloud/incident/331078#581c779ddf6c33e72eb291bbb79015c256073b44c63ac08170b04c3919555a8a We are currently aware of a Database connection issue. We are working on it! https://status.ecozend.cloud/incident/330992 Fri, 23 Feb 2024 14:00:00 -0000 https://status.ecozend.cloud/incident/330992#29708128500204cedea65f8b1214fd89c17a977295718b07aa6599463c1851e1 Maintenance completed https://status.ecozend.cloud/incident/330992 Fri, 23 Feb 2024 13:05:00 -0000 https://status.ecozend.cloud/incident/330992#f4a91edeacfd887f6797aaffb9ac3d65aa2725b9e22c5751107c932d89e8d069 We're transfering our Domain Name Server Records to a different Account. Outages will happen. https://status.ecozend.cloud/incident/328165 Sat, 17 Feb 2024 18:00:00 -0000 https://status.ecozend.cloud/incident/328165#f3298db5100785b12eb34cebccee0c57d362218b8e85ce5fa0f83006b0beccea Maintenance completed https://status.ecozend.cloud/incident/328165 Sat, 17 Feb 2024 17:00:00 -0000 https://status.ecozend.cloud/incident/328165#6e850c7e94e5857ff12774db24c34838961ea46d4cb348484a82d6a713562875 Akami Solutions is making changes to the database. Some services may not work during the maintenance work. https://status.ecozend.cloud/incident/326599 Wed, 14 Feb 2024 23:10:00 -0000 https://status.ecozend.cloud/incident/326599#88c79d3a2bedf2d2e731c960e288bc16f2a459c3c61e3fa35c92b2e0ed4a00a2 Maintenance completed https://status.ecozend.cloud/incident/326599 Wed, 14 Feb 2024 23:00:00 -0000 https://status.ecozend.cloud/incident/326599#f13a039cd4d81ece7a7eeaed6c3448a827b3e92945b3b99366b49932e512d6f1 We are undergoing an API System Update. It can be possible that some requests takes a bit longer. https://status.ecozend.cloud/incident/322695 Tue, 06 Feb 2024 07:37:00 -0000 https://status.ecozend.cloud/incident/322695#37b56fdbac1bce28869ee20c045bb1a3994bb3bf13a509d054f29823a4b73947 We've finally fixed all the issues. The latest issue was solved by granting httpd the connection to the network https://status.ecozend.cloud/incident/322676 Mon, 05 Feb 2024 23:00:00 -0000 https://status.ecozend.cloud/incident/322676#27934d4cfbb7130072e0c3a91b6da490854844816821361080ed6ff8928a6c54 Maintenance completed https://status.ecozend.cloud/incident/322695 Mon, 05 Feb 2024 22:18:00 -0000 https://status.ecozend.cloud/incident/322695#6c404a9437b804d1cda750a51b3c33451a49231fdb175331ff6d6d1b845da680 We've fixed this major issue. We currently just have issues accessing to our api service port https://status.ecozend.cloud/incident/322695 Mon, 05 Feb 2024 21:30:00 -0000 https://status.ecozend.cloud/incident/322695#150144510cb9856b02bb366e6e42c419ef569bdcce52049a3c1982c0620929cb Due to the reason that NGINX have major issues with our OS we are currently not able to provide any Service in any way https://status.ecozend.cloud/incident/322676 Mon, 05 Feb 2024 20:45:00 -0000 https://status.ecozend.cloud/incident/322676#c9c611f5c001b338def3c26c0742d69572276455e90e6866dc1ab1933db97a3e We are undergoing some proxy configurations https://status.ecozend.cloud/incident/322547 Mon, 05 Feb 2024 14:15:00 -0000 https://status.ecozend.cloud/incident/322547#6de3313e93eb5b0d05b1855b6aff2f29d45246dce8de4a74f5f19ac63cfef682 00:23 : Massive increase in HTTP/503 error messages 08:00 : The Akami Solutions team has noticed the problem and is working to fix it. 10:00 : Akami Solutions has not been able to fix the error at gateway-vie-21 despite trying to switch to Cloudflare Tunnels. The number of 403 error messages has increased massively. Still no success, but some progress. 13:00 : It has been switched to gateway-il-02. Since the server was new, we had to transfer the data from gateway-vie-21 to gateway-il-02. The transfer went smoothly, but there were some problems with our reverse proxy. These problems had to be fixed before everything worked again. 15:15 : Akami Solutions administration has fixed all the bugs and the API is back online! https://status.ecozend.cloud/incident/322310 Mon, 05 Feb 2024 02:00:00 -0000 https://status.ecozend.cloud/incident/322310#2eaf96a9878badf11ebf571ce39c2d1ad1c91b0a2eb09089e02591b3dd4544c2 Maintenance completed https://status.ecozend.cloud/incident/322547 Sun, 04 Feb 2024 23:23:00 -0000 https://status.ecozend.cloud/incident/322547#988c462d13ab194bcf9275d1e745a57bed5566453a084289294968289a1083b5 00:23 : Massive increase in HTTP/503 error messages 08:00 : The Akami Solutions team has noticed the problem and is working to fix it. 10:00 : Akami Solutions has not been able to fix the error at gateway-vie-21 despite trying to switch to Cloudflare Tunnels. The number of 403 error messages has increased massively. Still no success, but some progress. 13:00 : It has been switched to gateway-il-02. Since the server was new, we had to transfer the data from gateway-vie-21 to gateway-il-02. The transfer went smoothly, but there were some problems with our reverse proxy. These problems had to be fixed before everything worked again. 15:15 : Akami Solutions administration has fixed all the bugs and the API is back online! https://status.ecozend.cloud/incident/322310 Fri, 02 Feb 2024 23:00:00 -0000 https://status.ecozend.cloud/incident/322310#953170f15ddba9e83cb0d8785b9a09c6333d39b4f03cd3533c5147c83e9fd89a We will be carrying out maintenance work on our network from 03.02.2024 to 05.02.2024. This may result in disruptions to our services https://status.ecozend.cloud/incident/320921 Thu, 01 Feb 2024 22:05:00 -0000 https://status.ecozend.cloud/incident/320921#1efea4f7b53ca96dee2361a3dfe3d2a63745f3cedf7d71652f5ea3196d06b219 Maintenance completed https://status.ecozend.cloud/incident/320921 Thu, 01 Feb 2024 21:57:00 -0000 https://status.ecozend.cloud/incident/320921#7432ce16f01ec73f85ab2ebec2333fcf61ae1d4bb30664c05472195cd9a4ed41 Due to a system update, the main server must be restarted. There will be interruptions for 5 minutes https://status.ecozend.cloud/incident/320675 Thu, 01 Feb 2024 09:30:00 -0000 https://status.ecozend.cloud/incident/320675#badb79731dd993cd4e51e08da9de5ff9e4610ed35af37f8f9af24dff537da66e Maintenance completed https://status.ecozend.cloud/incident/320675 Thu, 01 Feb 2024 07:30:00 -0000 https://status.ecozend.cloud/incident/320675#40021cbdc396b922e7940f335a7ba376d487234836b591278894b60ba40ad3fa We will be making changes to our reverse proxy. There may be increased loading times https://status.ecozend.cloud/incident/319734 Tue, 30 Jan 2024 10:28:00 -0000 https://status.ecozend.cloud/incident/319734#54a2ee1d3b24638eb0eeccf3d359a693df6868f35853e95223dc6c74e9f4ac49 We fixed it and everything should work now again https://status.ecozend.cloud/incident/317019 Wed, 24 Jan 2024 04:00:00 -0000 https://status.ecozend.cloud/incident/317019#602b9977c5b871f190575101bc6c7165b30277efb9e0d93def57122b08930fd7 We've found the issue a fix is being implemented https://status.ecozend.cloud/incident/315271 Sun, 21 Jan 2024 22:38:00 -0000 https://status.ecozend.cloud/incident/315271#1e4d41b06fff4a702448bc9551a64238ddc23eb8db82e045df4a9ffb6d04a5eb We've loaded a Backup and everything looks normal. https://status.ecozend.cloud/incident/315271 Sat, 20 Jan 2024 01:07:00 -0000 https://status.ecozend.cloud/incident/315271#4d2214a543e29fa28a9cc841377d2ef0810509ac4256707badc4440ee30faf2e Due to an NDA, we cannot provide any more detailed information on this case. https://status.ecozend.cloud/incident/315199 Fri, 19 Jan 2024 21:42:00 -0000 https://status.ecozend.cloud/incident/315199#064a9e0578acad44ba9152458eb2e7508990e82e06ed2636811eda19a1fbb6ef It looks like a server restart has fixed the error. We are still keeping an eye on the problem! https://status.ecozend.cloud/incident/315199 Fri, 19 Jan 2024 21:35:00 -0000 https://status.ecozend.cloud/incident/315199#b033269488e0e7c5c2fc8467cd10406bcb6a20d5ba54e5f2c2667375496308e7 We are currently aware of a problem with wallet data queries. These queries timeout with the error code 502