Incidents reported on status page for d3vex https://status.d3vex.fr/ en https://status.d3vex.fr/ Fri, 23 Jan 2026 23:35:39 +0000 https://status.d3vex.fr/#5ec92d7ac688391049b1a2765e504283bcd7c8d4aed5ec437dc3e4b92b264074 NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Fri, 23 Jan 2026 23:33:02 +0000 https://status.d3vex.fr/#5ec92d7ac688391049b1a2765e504283bcd7c8d4aed5ec437dc3e4b92b264074 NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Fri, 23 Jan 2026 21:44:41 +0000 https://status.d3vex.fr/#d8a337958116e18eedd783d4ff9e2fa3d063827b9d1f3f91ec3583974264811b NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Fri, 23 Jan 2026 21:42:01 +0000 https://status.d3vex.fr/#d8a337958116e18eedd783d4ff9e2fa3d063827b9d1f3f91ec3583974264811b NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Fri, 23 Jan 2026 19:56:41 +0000 https://status.d3vex.fr/#093e71049120eb4e57d5f115a32b3a434c08e0797245f1e37d65f4392bb4906b NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Fri, 23 Jan 2026 19:53:59 +0000 https://status.d3vex.fr/#093e71049120eb4e57d5f115a32b3a434c08e0797245f1e37d65f4392bb4906b NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Fri, 23 Jan 2026 10:38:36 +0000 https://status.d3vex.fr/#f50249b3abe254750865bdd20ff6187241e4a13f8c65dd9d7b632187af2d2fda NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Fri, 23 Jan 2026 10:35:58 +0000 https://status.d3vex.fr/#f50249b3abe254750865bdd20ff6187241e4a13f8c65dd9d7b632187af2d2fda NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Fri, 23 Jan 2026 01:41:42 +0000 https://status.d3vex.fr/#bcd86c783195f5a2187a098504b0623cd7ecc5a22eb2933ccc7b2ba206844e81 NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Fri, 23 Jan 2026 01:38:59 +0000 https://status.d3vex.fr/#bcd86c783195f5a2187a098504b0623cd7ecc5a22eb2933ccc7b2ba206844e81 NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Thu, 22 Jan 2026 12:50:37 +0000 https://status.d3vex.fr/#95135decf58c0145ac4c54eb758d6553d6a360b90490bf7834861600fe85deb7 NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Thu, 22 Jan 2026 12:48:00 +0000 https://status.d3vex.fr/#95135decf58c0145ac4c54eb758d6553d6a360b90490bf7834861600fe85deb7 NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Thu, 22 Jan 2026 11:32:38 +0000 https://status.d3vex.fr/#c01fc61ab23a1584b290effd362b4f82786aa088814caa547ff2436ce55d213c NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Thu, 22 Jan 2026 11:30:02 +0000 https://status.d3vex.fr/#c01fc61ab23a1584b290effd362b4f82786aa088814caa547ff2436ce55d213c NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Thu, 22 Jan 2026 06:32:37 +0000 https://status.d3vex.fr/#2193e76f4b88a457bc9d22e0ce91793c883c42e91b7c1a2a87e16243e874ac56 NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Thu, 22 Jan 2026 06:30:05 +0000 https://status.d3vex.fr/#2193e76f4b88a457bc9d22e0ce91793c883c42e91b7c1a2a87e16243e874ac56 NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Wed, 21 Jan 2026 12:02:42 +0000 https://status.d3vex.fr/#afaf379a2d5b6a3c15df3a57c6bbfaa08d574728eb12677cb4a9607558c776cc NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Wed, 21 Jan 2026 11:59:57 +0000 https://status.d3vex.fr/#afaf379a2d5b6a3c15df3a57c6bbfaa08d574728eb12677cb4a9607558c776cc NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Wed, 21 Jan 2026 01:41:41 +0000 https://status.d3vex.fr/#8ee63959a9546947b5f39011585d40a5d497381eb189c4d1258d594295b7f5ba NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Wed, 21 Jan 2026 01:38:56 +0000 https://status.d3vex.fr/#8ee63959a9546947b5f39011585d40a5d497381eb189c4d1258d594295b7f5ba NODE 2 - MX-HEBERG went down https://status.d3vex.fr/incident/807177 Mon, 19 Jan 2026 07:40:00 -0000 https://status.d3vex.fr/incident/807177#4dff413ae55c6c4aa801bb7ca2bec196bef2d143b591eec6a009cc9f60ff53f2 Maintenance completed https://status.d3vex.fr/ Mon, 19 Jan 2026 07:38:39 +0000 https://status.d3vex.fr/#09569b901af4c52a95716cc8578dd34ebfb5650055d311b66c9593be40ad0af1 NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Fri, 16 Jan 2026 01:09:05 +0000 https://status.d3vex.fr/#09569b901af4c52a95716cc8578dd34ebfb5650055d311b66c9593be40ad0af1 NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Fri, 16 Jan 2026 01:05:45 +0000 https://status.d3vex.fr/#c685243824eb21afb550066f66b7fb7ed3d4fa4406702720856de9a0045339b2 NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Fri, 16 Jan 2026 00:48:00 +0000 https://status.d3vex.fr/#c685243824eb21afb550066f66b7fb7ed3d4fa4406702720856de9a0045339b2 NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Fri, 16 Jan 2026 00:44:38 +0000 https://status.d3vex.fr/#d56ed0bb0d828a186499d1b2e69c48dfa2e1985e74154f16676be09908a38c9f NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Thu, 15 Jan 2026 19:42:03 +0000 https://status.d3vex.fr/#d56ed0bb0d828a186499d1b2e69c48dfa2e1985e74154f16676be09908a38c9f NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Thu, 15 Jan 2026 19:35:38 +0000 https://status.d3vex.fr/#e0181de733bbe1f7bd5f1197bd373b724483bf5f20e400eee009d61876751cdb NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Thu, 15 Jan 2026 18:42:38 +0000 https://status.d3vex.fr/#245fb1fbbc476420a2973505cf0317680d41846af2caae6d2f52b8420f82cfa7 IONOS recovered https://status.d3vex.fr/ Thu, 15 Jan 2026 18:39:44 +0000 https://status.d3vex.fr/#245fb1fbbc476420a2973505cf0317680d41846af2caae6d2f52b8420f82cfa7 IONOS went down https://status.d3vex.fr/ Thu, 15 Jan 2026 15:48:01 +0000 https://status.d3vex.fr/#e0181de733bbe1f7bd5f1197bd373b724483bf5f20e400eee009d61876751cdb NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Thu, 15 Jan 2026 15:44:37 +0000 https://status.d3vex.fr/#57365ebf64b58449c64c246ba7b0bfcb48691f2caa233e687a22f654cf0ad135 NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Thu, 15 Jan 2026 15:39:05 +0000 https://status.d3vex.fr/#57365ebf64b58449c64c246ba7b0bfcb48691f2caa233e687a22f654cf0ad135 NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Thu, 15 Jan 2026 15:29:44 +0000 https://status.d3vex.fr/#edf477b05d1cdc3c205bada60449c5f9ba44dc6251a4add30d2748d8bd008f38 NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/incident/807177 Tue, 13 Jan 2026 23:00:00 -0000 https://status.d3vex.fr/incident/807177#7908f50dc24387fbb22bc9f6ba5f5e5ce1fb5bca480e023a97609a56ac8911e5 The IP provider for the MX-HEBERG (NODE 2) have stop providing us the IP. The tunnel was black hole and no connection have been working. We change IP, now it should work again correctly. Due to Week-end, we have not been able to work correctly, this is why it take so long https://status.d3vex.fr/ Tue, 13 Jan 2026 22:45:08 +0000 https://status.d3vex.fr/#edf477b05d1cdc3c205bada60449c5f9ba44dc6251a4add30d2748d8bd008f38 NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Fri, 09 Jan 2026 16:00:46 +0000 https://status.d3vex.fr/#07c7c022c475f55a2555b5ae6b3dd5f4d668e28e2a9871e3c6dd9a13f6e6e915 IONOS recovered https://status.d3vex.fr/ Fri, 09 Jan 2026 15:57:45 +0000 https://status.d3vex.fr/#07c7c022c475f55a2555b5ae6b3dd5f4d668e28e2a9871e3c6dd9a13f6e6e915 IONOS went down https://status.d3vex.fr/ Sun, 04 Jan 2026 02:39:15 +0000 https://status.d3vex.fr/#fbcc13007ad547de42445e817019fabd8be18dc8f6447bf80a66e7529cfd35c2 NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Sun, 04 Jan 2026 02:36:29 +0000 https://status.d3vex.fr/#fbcc13007ad547de42445e817019fabd8be18dc8f6447bf80a66e7529cfd35c2 NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Tue, 30 Dec 2025 19:24:43 +0000 https://status.d3vex.fr/#b29266414ad3c15eca2609628dae0e5efd1283c92b82c93c9c2270ffa1bc518b IONOS recovered https://status.d3vex.fr/ Tue, 30 Dec 2025 19:21:42 +0000 https://status.d3vex.fr/#b29266414ad3c15eca2609628dae0e5efd1283c92b82c93c9c2270ffa1bc518b IONOS went down https://status.d3vex.fr/ Thu, 18 Dec 2025 11:06:14 +0000 https://status.d3vex.fr/#d284192f74997d841379d5faf3832ac4a5279431efbfe3ca4f4e76a17638d37b NODE 1 - REDHEBERG recovered https://status.d3vex.fr/ Thu, 18 Dec 2025 10:48:32 +0000 https://status.d3vex.fr/#d284192f74997d841379d5faf3832ac4a5279431efbfe3ca4f4e76a17638d37b NODE 1 - REDHEBERG went down https://status.d3vex.fr/ Sun, 14 Dec 2025 22:38:43 +0000 https://status.d3vex.fr/#cdd071b41e61c7398a96f7b64cd888840125a0b330b06c0059598438df9c3ca2 NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Sun, 14 Dec 2025 22:24:07 +0000 https://status.d3vex.fr/#cdd071b41e61c7398a96f7b64cd888840125a0b330b06c0059598438df9c3ca2 NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Sun, 14 Dec 2025 22:08:46 +0000 https://status.d3vex.fr/#e5421cc45a490bc18756ef057b12a715cefa5cc1a365ba64653482da159da35d NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Sun, 14 Dec 2025 21:51:01 +0000 https://status.d3vex.fr/#e5421cc45a490bc18756ef057b12a715cefa5cc1a365ba64653482da159da35d NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Mon, 01 Dec 2025 19:54:43 +0000 https://status.d3vex.fr/#475ebb7875c8d8f614d28e59d9a79fc5f9aef3f8934fe0be260bc7e6b54c410f NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Mon, 01 Dec 2025 19:40:04 +0000 https://status.d3vex.fr/#475ebb7875c8d8f614d28e59d9a79fc5f9aef3f8934fe0be260bc7e6b54c410f NODE 2 - MX-HEBERG went down https://status.d3vex.fr/ Fri, 28 Nov 2025 18:16:49 +0000 https://status.d3vex.fr/#096101f1da6884c8d103edf14e06fa29d2e39a458addc98e98204cf2cf000670 NODE 2 - MX-HEBERG recovered https://status.d3vex.fr/ Fri, 28 Nov 2025 17:38:07 +0000 https://status.d3vex.fr/#096101f1da6884c8d103edf14e06fa29d2e39a458addc98e98204cf2cf000670 NODE 2 - MX-HEBERG went down https://status.d3vex.fr/incident/372075 Mon, 20 May 2024 13:00:00 -0000 https://status.d3vex.fr/incident/372075#b64f97efa9fc92d4d5f30f759e0b4090e9aeef3d5e3982572c6853c2b9d625d8 Maintenance completed https://status.d3vex.fr/incident/372075 Mon, 20 May 2024 12:30:00 -0000 https://status.d3vex.fr/incident/372075#9481ba42d784735c747ab70281ed39247dc6e78914b2d6afb931e3aeaec4b3d9 Mise à jour pterodactyl, packages, serveur, et configurations https://status.d3vex.fr/incident/368994 Mon, 13 May 2024 21:07:00 -0000 https://status.d3vex.fr/incident/368994#b683a576dd56b2773011fbafe57ef2768f91a9fcc32f53ddfe60f54256739618 A cause d'une erreur de prélèvement automatique et de mon inattention, le serveur n'avait pas été payé entièrement ce qui a entraîné une suspension de celui ci. https://status.d3vex.fr/incident/365960 Tue, 07 May 2024 09:08:00 -0000 https://status.d3vex.fr/incident/365960#d77566923caa0d747d0c6644424e0445b620378760253c87d35e1770925e803a Le serveur 1 hébergeant toutes les données est actuellement down. Une équipe technique est déjà sur le coup!