Incidents and maintenance reported on status page for TM Dev. https://status.tm-dev.be/ en https://status.tm-dev.be/incident/1081411 Sun, 04 Oct 2026 22:41:00 -0000 https://status.tm-dev.be/incident/1081411#6df06cf4558934748bef6c546fc4f87e70050558e9044de40cc553807e377f58 Incident The fix has been successfully deployed and the latest version of ForkDeploy CLI is now live. All API issues and request errors have been fully resolved. Please update your CLI installation to the newest version to resume deployments. https://status.tm-dev.be/incident/1081411 Sun, 04 Oct 2026 22:24:00 -0000 https://status.tm-dev.be/incident/1081411#51de4df56623a25b85b981c446f3bb9b5156add1fe8a65d81a3652c5490ef019 Incident The API issue affecting ForkDeploy CLI has been completely fixed. A new version of the CLI is being published now and will be available within minutes. https://status.tm-dev.be/incident/1081411 Sun, 04 Oct 2026 22:11:00 -0000 https://status.tm-dev.be/incident/1081411#599ccca6e3490d1b25aa9ee00ba148de7f997597b5c83dd6a6169170ab3bf2d3 Incident Following further analysis and testing, we have confirmed that the third-party service is fully operational and up to date. The root cause of the current issue has been isolated to an error within our own API. We actively conducting tests and debugging the API to deploy a fix as soon as possible. We will post another update once testing concludes. https://status.tm-dev.be/incident/1081411 Sun, 04 Oct 2026 15:35:00 -0000 https://status.tm-dev.be/incident/1081411#dc6588034b4d4cfe224e876586a931cd2a1887525bdcc30feba8550897b06c62 Incident We have identified the root cause of the ForkDeploy CLI errors (405 / authorization failures). Requests are being blocked by strict CORS policies enforced by an upstream third-party service provider. Some users may still be able to complete deployments normally. If you encounter errors, you can attempt to retry the command, though full reliability will be restored once the policy adjustments are complete. We expect to provide our next progress update in 24 hours. https://status.tm-dev.be/incident/1081411 Sun, 04 Oct 2026 15:17:00 -0000 https://status.tm-dev.be/incident/1081411#c4f542cf0b335799b8f965b1d0045607d01d80d28ce6504369b5f72fb4fe03b2 Incident We are investigating reports of receiving 405 Unauthorized errors when executing commands via the newly released ForkDeploy CLI. We are actively analyzing the root cause and is preparing a patch release for the CLI to address this issue. We will post another update as soon as a new CLI version is available or further details are confirmed. https://status.tm-dev.be/incident/1075618 Sun, 27 Sep 2026 19:46:00 -0000 https://status.tm-dev.be/incident/1075618#a223d9a1a0fb7c72c6857da13d11fc007f4f0d2c441d4d453843b92a4b7304f8 Incident The issue affecting our services and valid Let's Encrypt certificates are once again actively serving all endpoints. No user data or project files were impacted during this event. If you are still seeing a connection warning, your browser may have cached the invalid certificate. Please perform a hard refresh (Ctrl + Shift + R or Cmd + Shift + R) or open the page in a private/incognito window. If you continue to experience issues, our support team is monitoring incoming emails with zero delay for the next hour. Reach out directly to hello@tm-dev.be for immediate assistance. https://status.tm-dev.be/incident/1075618 Sun, 27 Sep 2026 19:33:00 -0000 https://status.tm-dev.be/incident/1075618#5cdcfa5235552692eb3c623a1e388bb1df5f1c0c748e78ff7520214e280c1892 Incident We have identified the root cause of the current outage, which stems from missing/invalid SSL/TLS certificates preventing secure connections to our application (NET::ERR_CERT_AUTHORITY_INVALID). To resolve this completely, our team is performing a full infrastructure rebuild and redeployment. Please rest assured that no projects or user data are lost. We are actively restoring services and will provide another update as soon as the redeployment is complete. https://status.tm-dev.be/incident/1075618 Sun, 27 Sep 2026 19:28:00 -0000 https://status.tm-dev.be/incident/1075618#1cd98b0d50c35bebc38c477207191979accb0cb8b6db0d75d7dfe66fab8f5c71 Incident Our systems are currently unavailable. We are actively executing server patches and rebooting services to bring everything back online as soon as possible. https://status.tm-dev.be/incident/1075618 Sun, 27 Sep 2026 19:24:00 -0000 https://status.tm-dev.be/incident/1075618#112e3af2f4c02841a0a7904071d7256ab8456f01468d77849aaa3e57ad5a37da Incident We are currently investigating an issue causing server instability and degraded service performance across several systems. Initial findings indicate this may be linked to a recent server upgrade and a delay in TLS services initializing post-reboot. Our team is actively working on a fix and expects to restore full functionality shortly. We will provide another update as soon as progress is made. https://status.tm-dev.be/incident/889207 Sat, 09 May 2026 17:50:00 -0000 https://status.tm-dev.be/incident/889207#292a68e55f7e2c1c8629ba7b761c7a9ab50fce779671467443aa77ba22115c4d Incident 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/889207 Tue, 05 May 2026 19:05:00 -0000 https://status.tm-dev.be/incident/889207#f4b23c724f2edf205b2b304fad734f48190637f516db92a2bc3fc2b927af8fe7 Incident 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/889207 Sun, 03 May 2026 10:24:00 -0000 https://status.tm-dev.be/incident/889207#57b68b52b7df6af246ecc23a1a114449532201a9fbb28a3bf89543e0a458d737 Incident 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/889207 Thu, 30 Apr 2026 18:39:00 -0000 https://status.tm-dev.be/incident/889207#0b70d10160164aa86728dc7c83cc110fddbe25645818b6da28f3c5e2d0b16016 Incident 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/889207 Thu, 16 Apr 2026 12:16:00 -0000 https://status.tm-dev.be/incident/889207#3c0ead78c34719c53f9cbdb678b2c7bd0d82e7fa5986732d96f758e6b43f8fa1 Incident 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.