Incidents reported on status page for TM https://status.tm-dev.be/ en https://status.tm-dev.be/incident/809701 Thu, 22 Jan 2026 16:02:00 -0000 https://status.tm-dev.be/incident/809701#6fbcc316ed171ba76d35117fb7adcfcc2435fcc0b969de66eea7c6c30e8d6e25 Should be fixed now? https://status.tm-dev.be/incident/809701 Thu, 22 Jan 2026 16:02:00 -0000 https://status.tm-dev.be/incident/809701#6fbcc316ed171ba76d35117fb7adcfcc2435fcc0b969de66eea7c6c30e8d6e25 Should be fixed now? https://status.tm-dev.be/incident/809701 Thu, 22 Jan 2026 16:02:00 -0000 https://status.tm-dev.be/incident/809701#6fbcc316ed171ba76d35117fb7adcfcc2435fcc0b969de66eea7c6c30e8d6e25 Should be fixed now? https://status.tm-dev.be/incident/809701 Thu, 22 Jan 2026 16:02:00 -0000 https://status.tm-dev.be/incident/809701#6fbcc316ed171ba76d35117fb7adcfcc2435fcc0b969de66eea7c6c30e8d6e25 Should be fixed now? https://status.tm-dev.be/ Thu, 22 Jan 2026 16:01:49 +0000 https://status.tm-dev.be/#81532bd3aae67e6d7a91c132d10e2e9418e1327bed8fa85512e0217531bd096f Hosting recovered https://status.tm-dev.be/ Thu, 22 Jan 2026 16:01:12 +0000 https://status.tm-dev.be/#12d152ae1451ffbade185ce66f1c0133ddcae434bd0d7807cead959a52141523 Custom Statuspages recovered https://status.tm-dev.be/ Thu, 22 Jan 2026 16:00:43 +0000 https://status.tm-dev.be/#25c63e3ec37c9d5f1fe0e678d8ec0cb13656f30e1ca6da0b748e6fa505c3bd0f S3 Storage recovered https://status.tm-dev.be/ Thu, 22 Jan 2026 15:57:43 +0000 https://status.tm-dev.be/#25c63e3ec37c9d5f1fe0e678d8ec0cb13656f30e1ca6da0b748e6fa505c3bd0f S3 Storage went down https://status.tm-dev.be/ Thu, 22 Jan 2026 15:55:48 +0000 https://status.tm-dev.be/#81532bd3aae67e6d7a91c132d10e2e9418e1327bed8fa85512e0217531bd096f Hosting went down https://status.tm-dev.be/ Thu, 22 Jan 2026 15:55:08 +0000 https://status.tm-dev.be/#12d152ae1451ffbade185ce66f1c0133ddcae434bd0d7807cead959a52141523 Custom Statuspages went down https://status.tm-dev.be/incident/809701 Thu, 22 Jan 2026 15:27:00 -0000 https://status.tm-dev.be/incident/809701#840b4f9caec881fc576a8f61451f30836e35c0975f4b3ff338fa99beeb78f5e6 Changes applied. Minor disconnections expected. Full stability in 5-10m. https://status.tm-dev.be/incident/809701 Thu, 22 Jan 2026 15:27:00 -0000 https://status.tm-dev.be/incident/809701#840b4f9caec881fc576a8f61451f30836e35c0975f4b3ff338fa99beeb78f5e6 Changes applied. Minor disconnections expected. Full stability in 5-10m. https://status.tm-dev.be/incident/809701 Thu, 22 Jan 2026 15:27:00 -0000 https://status.tm-dev.be/incident/809701#840b4f9caec881fc576a8f61451f30836e35c0975f4b3ff338fa99beeb78f5e6 Changes applied. Minor disconnections expected. Full stability in 5-10m. https://status.tm-dev.be/incident/809701 Thu, 22 Jan 2026 15:27:00 -0000 https://status.tm-dev.be/incident/809701#840b4f9caec881fc576a8f61451f30836e35c0975f4b3ff338fa99beeb78f5e6 Changes applied. Minor disconnections expected. Full stability in 5-10m. https://status.tm-dev.be/ Thu, 22 Jan 2026 15:21:02 +0000 https://status.tm-dev.be/#66b53df7ad1d9d02955de91d2677b389ed3dcaf60e74245054f8f10bdcde2d70 Newsletters recovered https://status.tm-dev.be/incident/809701 Thu, 22 Jan 2026 15:20:00 -0000 https://status.tm-dev.be/incident/809701#81c68ceda49c62244beb201dbec7a670b93a663b3a81ea480dd029f18c9bc7ac Services restored. Minor transients possible. https://status.tm-dev.be/incident/809701 Thu, 22 Jan 2026 15:20:00 -0000 https://status.tm-dev.be/incident/809701#81c68ceda49c62244beb201dbec7a670b93a663b3a81ea480dd029f18c9bc7ac Services restored. Minor transients possible. https://status.tm-dev.be/incident/809701 Thu, 22 Jan 2026 15:20:00 -0000 https://status.tm-dev.be/incident/809701#81c68ceda49c62244beb201dbec7a670b93a663b3a81ea480dd029f18c9bc7ac Services restored. Minor transients possible. https://status.tm-dev.be/incident/809701 Thu, 22 Jan 2026 15:20:00 -0000 https://status.tm-dev.be/incident/809701#81c68ceda49c62244beb201dbec7a670b93a663b3a81ea480dd029f18c9bc7ac Services restored. Minor transients possible. https://status.tm-dev.be/ Thu, 22 Jan 2026 15:19:46 +0000 https://status.tm-dev.be/#1fa4d457a33b30f517cdb2b1cd2c3f5d30d5a4795e074779544a5056289bf0bb Hosting recovered https://status.tm-dev.be/ Thu, 22 Jan 2026 15:19:02 +0000 https://status.tm-dev.be/#5e77d733982eaaa4886be244b26ef5f82376c6bf2cf36cd42537f3b02f43cf41 Custom Statuspages recovered https://status.tm-dev.be/ Thu, 22 Jan 2026 15:18:44 +0000 https://status.tm-dev.be/#46c8ff53478e1789bee0aeda5bad6e1f295ae8c9718e301417455f3978a285cd S3 Storage recovered https://status.tm-dev.be/ Thu, 22 Jan 2026 15:13:27 +0000 https://status.tm-dev.be/#66b53df7ad1d9d02955de91d2677b389ed3dcaf60e74245054f8f10bdcde2d70 Newsletters went down https://status.tm-dev.be/incident/809701 Thu, 22 Jan 2026 15:09:00 -0000 https://status.tm-dev.be/incident/809701#b8802296beeee7839f170a1d5c775a16fd5dbde6d651c105b8d58686df8f5c0f All services down. Server looped. Rebooting. This isn't your fault. The server broke itself. https://status.tm-dev.be/incident/809701 Thu, 22 Jan 2026 15:09:00 -0000 https://status.tm-dev.be/incident/809701#b8802296beeee7839f170a1d5c775a16fd5dbde6d651c105b8d58686df8f5c0f All services down. Server looped. Rebooting. This isn't your fault. The server broke itself. https://status.tm-dev.be/incident/809701 Thu, 22 Jan 2026 15:09:00 -0000 https://status.tm-dev.be/incident/809701#b8802296beeee7839f170a1d5c775a16fd5dbde6d651c105b8d58686df8f5c0f All services down. Server looped. Rebooting. This isn't your fault. The server broke itself. https://status.tm-dev.be/incident/809701 Thu, 22 Jan 2026 15:09:00 -0000 https://status.tm-dev.be/incident/809701#b8802296beeee7839f170a1d5c775a16fd5dbde6d651c105b8d58686df8f5c0f All services down. Server looped. Rebooting. This isn't your fault. The server broke itself. https://status.tm-dev.be/ Thu, 22 Jan 2026 15:07:39 +0000 https://status.tm-dev.be/#1fa4d457a33b30f517cdb2b1cd2c3f5d30d5a4795e074779544a5056289bf0bb Hosting went down https://status.tm-dev.be/ Thu, 22 Jan 2026 15:07:11 +0000 https://status.tm-dev.be/#46c8ff53478e1789bee0aeda5bad6e1f295ae8c9718e301417455f3978a285cd S3 Storage went down https://status.tm-dev.be/ Thu, 22 Jan 2026 15:07:03 +0000 https://status.tm-dev.be/#5e77d733982eaaa4886be244b26ef5f82376c6bf2cf36cd42537f3b02f43cf41 Custom Statuspages went down https://status.tm-dev.be/ Tue, 20 Jan 2026 21:13:25 +0000 https://status.tm-dev.be/#50f4e7ae3de51b82023354beada186a828e6f4ffa3fa96bb729f8ed543f5ceb2 Newsletters recovered https://status.tm-dev.be/ Tue, 20 Jan 2026 20:44:25 +0000 https://status.tm-dev.be/#50f4e7ae3de51b82023354beada186a828e6f4ffa3fa96bb729f8ed543f5ceb2 Newsletters went down https://status.tm-dev.be/ Tue, 20 Jan 2026 02:43:32 +0000 https://status.tm-dev.be/#24a777e431f7c82d9bdc646c46a8a82b6f5486748329ab9c3ce6ed0b7573c193 Newsletters recovered https://status.tm-dev.be/ Tue, 20 Jan 2026 02:14:55 +0000 https://status.tm-dev.be/#24a777e431f7c82d9bdc646c46a8a82b6f5486748329ab9c3ce6ed0b7573c193 Newsletters went down https://status.tm-dev.be/ Tue, 06 Jan 2026 15:11:50 +0000 https://status.tm-dev.be/#cc5de29738fd7145a92ecfa75716a49b4c86de4cd153cd146e65bfc2fe427dc1 S3 Storage recovered https://status.tm-dev.be/ Tue, 30 Dec 2025 16:51:46 +0000 https://status.tm-dev.be/#cc5de29738fd7145a92ecfa75716a49b4c86de4cd153cd146e65bfc2fe427dc1 S3 Storage went down https://status.tm-dev.be/ Fri, 28 Nov 2025 19:50:21 +0000 https://status.tm-dev.be/#da72059305da2db0e5f2e5b809e7cadc3c0efda4a3a4af3a7c1fe852af696b8f Hosting recovered https://status.tm-dev.be/ Fri, 28 Nov 2025 19:49:48 +0000 https://status.tm-dev.be/#da72059305da2db0e5f2e5b809e7cadc3c0efda4a3a4af3a7c1fe852af696b8f Hosting went down https://status.tm-dev.be/ Wed, 26 Nov 2025 10:37:11 +0000 https://status.tm-dev.be/#e8a19d66482cb9cd45d6416b25da7840eb38a8d2356c0469a98b29c36320305b Custom Statuspages recovered https://status.tm-dev.be/ Wed, 26 Nov 2025 10:33:28 +0000 https://status.tm-dev.be/#e8a19d66482cb9cd45d6416b25da7840eb38a8d2356c0469a98b29c36320305b Custom Statuspages went down