Incidents reported on status page for TM Dev. https://status.tm-dev.be/ en https://status.tm-dev.be/incident/897413 Sat, 16 May 2026 20:55:23 -0000 https://status.tm-dev.be/incident/897413#d1d56ed49ae76d719fa5faf07f5595973fa1445c621c0792acfb56f48491d2f3 Maintenance completed https://status.tm-dev.be/incident/897413 Sat, 16 May 2026 18:55:23 -0000 https://status.tm-dev.be/incident/897413#76918059ecf5d1b03360e6ed237162d64462b5d11ef10f9cbd60f6098a792d29 We will be performing scheduled maintenance on our API to optimize networking configurations. This maintenance is necessary to enhance performance and prepare for future updates. Please be aware that during this time, some main services may experience temporary downtime. We appreciate your understanding and patience as we work to improve our services. https://status.tm-dev.be/incident/889207 Sat, 09 May 2026 17:50:00 -0000 https://status.tm-dev.be/incident/889207#292a68e55f7e2c1c8629ba7b761c7a9ab50fce779671467443aa77ba22115c4d We are happy to report that the majority of bugs and minor issues identified during the initial migration have been successfully resolved. The final required content and updates are scheduled to be published within the next 72 hours. https://status.tm-dev.be/incident/891701 Sat, 09 May 2026 12:01:00 -0000 https://status.tm-dev.be/incident/891701#210eadcc41eda0b99a1f6a92372196dd28783db21bf2d1f9a293e5fce485debd To ensure long-term stability on our current hardware, we are performing a mandatory storage cleanup and service restructuring. This maintenance will prepare our environment for the transition. Some services may be temporarily unavailable or experience a degrade in performance during the operation. https://status.tm-dev.be/incident/889207 Tue, 05 May 2026 19:05:00 -0000 https://status.tm-dev.be/incident/889207#f4b23c724f2edf205b2b304fad734f48190637f516db92a2bc3fc2b927af8fe7 Because the migration is fresh, some minor issues or bugs may be present. These are known and are being actively tracked. The improved and fully optimized version of the portfolio will be live this week. https://status.tm-dev.be/incident/874730 Tue, 05 May 2026 18:14:00 -0000 https://status.tm-dev.be/incident/874730#5538d0d7643f39f85d88b91d6faa1a192f3da698280568215dcc0b5b37b58671 The planned server upgrade has been postponed and will be rescheduled for a later date. In the meantime, we are shifting our focus to a more immediate solution for our mailing services. **Key Changes:** - **DMS Status**: Direct-Mail Services (DMS) are currently being taken offline. - **GGR Activation**: we are switching back to Global Group Redistribution (GGR) to handle our mail traffic. - **Address Consolidation**: All email addresses that previously used a subdomain are being moved to the root domain (placed before the @ symbol). This centralizes our communication and simplifies the configuration. https://status.tm-dev.be/incident/889207 Sun, 03 May 2026 10:24:00 -0000 https://status.tm-dev.be/incident/889207#57b68b52b7df6af246ecc23a1a114449532201a9fbb28a3bf89543e0a458d737 We are currently investing time into fine-tuning the new storage and database volumes to ensure long-term stability. https://status.tm-dev.be/incident/874730 Sat, 02 May 2026 11:20:00 -0000 https://status.tm-dev.be/incident/874730#2efc58e8bb13b5cf94c8e17eb818389d8fe116483817a183b27877bd4e72e761 We have finalized our plan to migrate to a higher-capacity environment to host our new integrated mail server. However, our provider currently has this specific hardware tier listed as out of stock. As soon as the upgrade is applied, we will schedule a maintenance window to deploy the mailing server and resolve all current conflicts. https://status.tm-dev.be/incident/889207 Thu, 30 Apr 2026 18:39:00 -0000 https://status.tm-dev.be/incident/889207#0b70d10160164aa86728dc7c83cc110fddbe25645818b6da28f3c5e2d0b16016 We have migrated away from Supabase. While powerful, Supabase was too heavy for our current infrastructure. We have replaced it with a custom, lightweight database that is faster and more efficient for our specific needs. https://status.tm-dev.be/incident/874730 Wed, 29 Apr 2026 12:32:00 -0000 https://status.tm-dev.be/incident/874730#256a4f09176939215468c1c4925b2fabbb7ab69408af3f9553e6a351a5c48a1b After extensive research, our team is moving forward with a potential solution to modernize our email infrastructure. We are currently evaluating the implementation to replace our current setup. https://status.tm-dev.be/incident/874730 Tue, 28 Apr 2026 19:32:00 -0000 https://status.tm-dev.be/incident/874730#e00f19adc6674c21472cda51088726c77191fbcc18f43932cc6d13e2bc5fc95d We are officially beginning a deep-dive investigation into our email infrastructure to resolve the ongoing routing and delivery issues. https://status.tm-dev.be/incident/881542 Tue, 28 Apr 2026 19:30:47 -0000 https://status.tm-dev.be/incident/881542#a3b95af525749e836033a57a23f379dabb14d081fbe1e8e6778c31c6b6769750 Despite our recent efforts, the technical conflicts involving our email infrastructure remain unresolved. As this is a solo-managed project, we are taking the necessary time over the coming days to perform a deep-dive investigation and implement a stable, long-term solution. https://status.tm-dev.be/incident/874730 Sat, 18 Apr 2026 21:57:00 -0000 https://status.tm-dev.be/incident/874730#270998921ecd6942260f5a110021b761cd57bbb1fc2e32d73f2266d6863f70f0 While our Direct-Mail Services are stable, the GGR layer is currently undergoing a deep-dive investigation. We have isolated the issue to the complex "one-to-many" routing logic required to distribute messages across our global groups. https://status.tm-dev.be/incident/872527 Sat, 18 Apr 2026 21:38:00 -0000 https://status.tm-dev.be/incident/872527#7291d9ec2ad1a1d85fff37ea1181f4164c1c0a6f9b4882e00e2db535d6676803 While our standard email services are fully operational, we have made the decision to pause our Global Group Redistribution services (email redirects) while we transition to a more reliable solution. https://status.tm-dev.be/ Sat, 18 Apr 2026 14:30:33 +0000 https://status.tm-dev.be/#d0f1676d59ab610025f3570cb050c1f3c89b2af2661765de73895bd126374760 Git Repository recovered https://status.tm-dev.be/ Thu, 16 Apr 2026 19:00:32 +0000 https://status.tm-dev.be/#d0f1676d59ab610025f3570cb050c1f3c89b2af2661765de73895bd126374760 Git Repository went down https://status.tm-dev.be/incident/889207 Thu, 16 Apr 2026 12:16:00 -0000 https://status.tm-dev.be/incident/889207#3c0ead78c34719c53f9cbdb678b2c7bd0d82e7fa5986732d96f758e6b43f8fa1 We have officially stopped using AWS and Vercel for hosting and storage. The portfolio now runs entirely on our own hardware for better control and privacy. https://status.tm-dev.be/ Thu, 16 Apr 2026 08:00:27 +0000 https://status.tm-dev.be/#fbe1a94dba6c6bbae18bec58860066eacfe2a98fdb78d3667f270d59445d910f Git Repository recovered https://status.tm-dev.be/ Thu, 16 Apr 2026 07:31:08 +0000 https://status.tm-dev.be/#fbe1a94dba6c6bbae18bec58860066eacfe2a98fdb78d3667f270d59445d910f Git Repository went down https://status.tm-dev.be/incident/872527 Wed, 15 Apr 2026 20:08:00 -0000 https://status.tm-dev.be/incident/872527#48edcfe3d0f5e53c32a940317c4128eb8cc24f60988152245e8caeebc8e6e24c We are currently in a wait-and-see phase regarding our email redirects. While our internal tests confirm that our new records are correctly configured, our external routing service is currently unable to "see" these updates. https://status.tm-dev.be/incident/872527 Wed, 15 Apr 2026 19:53:00 -0000 https://status.tm-dev.be/incident/872527#a3f707edd487a00cefff8933a25763add5969db8d43488adf30b8bd08ff182ef While our email infrastructure is online, we are currently tracking significant delivery latency and reports of intermittent message failures across our distribution groups. We are treating this as a high-priority issue and are working to restore real-time delivery as quickly as possible. https://status.tm-dev.be/incident/872149 Wed, 15 Apr 2026 18:44:00 -0000 https://status.tm-dev.be/incident/872149#bd2cc2da5eabf2cc75fe99bc18f873896dd012242da3c713ca991905955a97a8 We have successfully deployed a solution for our global email redirects and core service connectivity. The "plumbing" is now connected, and messages are routing correctly through our new infrastructure. https://status.tm-dev.be/ Wed, 15 Apr 2026 18:43:40 +0000 https://status.tm-dev.be/#41a0e97c8dbbb8c9a4764f16e3ad43d29d1c1b32040a56ede0bb900ffffa9e35 Connectivity recovered https://status.tm-dev.be/ Wed, 15 Apr 2026 18:43:40 +0000 https://status.tm-dev.be/#803c3909c1be77ec8788be679172d6267465cd96e26bd8c9f740797c7c1b0761 Git Repository recovered https://status.tm-dev.be/incident/872299 Wed, 15 Apr 2026 16:43:00 -0000 https://status.tm-dev.be/incident/872299#1d2936b2b9a39964cd73818a8edf2fb6c479975c7613c9287bead9e7025f76a6 We have successfully resolved the conflict between our Git repositories and the core infrastructure. The connection has been re-established, and all repository-dependent services are once again reachable. https://status.tm-dev.be/ Wed, 15 Apr 2026 14:01:20 +0000 https://status.tm-dev.be/#41a0e97c8dbbb8c9a4764f16e3ad43d29d1c1b32040a56ede0bb900ffffa9e35 Connectivity went down https://status.tm-dev.be/ Wed, 15 Apr 2026 13:30:29 +0000 https://status.tm-dev.be/#803c3909c1be77ec8788be679172d6267465cd96e26bd8c9f740797c7c1b0761 Git Repository went down https://status.tm-dev.be/incident/872299 Wed, 15 Apr 2026 11:34:00 -0000 https://status.tm-dev.be/incident/872299#d8a1020e58e5fd27cfe0320dda5753115eda45cb7262762e9ddc2ff86884a0a2 We have identified a significant conflict between our Git repositories and the core infrastructure. As a result, both the development environment and certain project endpoints are currently unreachable. https://status.tm-dev.be/incident/872149 Wed, 15 Apr 2026 10:06:00 -0000 https://status.tm-dev.be/incident/872149#07beee90a4390e612b07c4108d63d4ab9e8bec4664cd634880a64230305c0353 We have made significant progress in restoring our communication infrastructure. Standard outbound email delivery is now partially resolved and functioning for most services. We are now shifting our investigation to our Global and Group Email Redirects. While individual emails are sending correctly, the logic that routes messages to our distribution groups is still being fine-tuned within the new network configuration. https://status.tm-dev.be/incident/872149 Wed, 15 Apr 2026 07:39:00 -0000 https://status.tm-dev.be/incident/872149#63ad75f95dc9c1e2cfda2b52668575609db2f17dd444f06263528ee481efc3ea While our web projects are progressively coming back online, automated emails and group redirects are currently being held in a queue or failing to send. We are addressing a configuration mismatch in our mail relay. https://status.tm-dev.be/incident/870613 Mon, 13 Apr 2026 14:54:00 -0000 https://status.tm-dev.be/incident/870613#541829a0198944359ba080aba39fa6bb9381ac0feac62878fa08d5a83d57bfcb We have successfully resolved the issues affecting our CI/CD pipelines. The "immediate exit" errors have been addressed, and automated deployments are once again functional across the platform. https://status.tm-dev.be/incident/870613 Mon, 13 Apr 2026 13:38:00 -0000 https://status.tm-dev.be/incident/870613#1b4f9842600c894dce446386c6debd94a988438733f5b6db0228b6388232bd42 While our core infrastructure remains stable, we are currently experiencing a technical block with our CI/CD pipelines. Recent project deployments are returning immediate exit codes, which is preventing us from pushing live updates to the platform. https://status.tm-dev.be/incident/869983 Mon, 13 Apr 2026 13:34:00 -0000 https://status.tm-dev.be/incident/869983#27d619ee8ebdac5bca940a5d81ce73ed4a31929857b6fc21b9ad4f3549ed978b The networking and CI/CD issues are now partially resolved. All operators are currently back online, and services are progressively returning to normal. https://status.tm-dev.be/ Mon, 13 Apr 2026 09:30:30 +0000 https://status.tm-dev.be/#96394dae70bf94d9f93cf6072f0548722f95ff1a1fdf742530abbcfa22e1a2fc Git Repository recovered https://status.tm-dev.be/ Mon, 13 Apr 2026 09:00:33 +0000 https://status.tm-dev.be/#96394dae70bf94d9f93cf6072f0548722f95ff1a1fdf742530abbcfa22e1a2fc Git Repository went down https://status.tm-dev.be/incident/869983 Sun, 12 Apr 2026 14:05:00 -0000 https://status.tm-dev.be/incident/869983#05443fc2b91d6641da59316b0a90ab429d44838b2eb9a9ffe16a7f4f8ec1b7ed While the new setup is applied, we are currently experiencing networking conflicts and Runner connectivity failures. As a result, several services will remain down for the day while I reconfigure the internal routing. I am aiming for full stability by the end of the day.