Incidents reported on status page for TM Dev. https://status.tm-dev.be/ en 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/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/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/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/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.