Incidents reported on status page for Ponlponl123 Labs https://status.ponlponl123.com/ https://d1lppblt9t2x15.cloudfront.net/logos/d7dba4f3cefa2af24a2d3cb667210e1e.png https://status.ponlponl123.com/ en https://status.ponlponl123.com/incident/830468 Sun, 22 Feb 2026 05:40:00 -0000 https://status.ponlponl123.com/incident/830468#d137c520d512b35a3f7c63f7b2f366ab21ec7f6937fadcb21f2141034c0e62d6 Mail server is currently maintenancing for better performance and high-availability. https://status.ponlponl123.com/incident/814288 Thu, 29 Jan 2026 10:00:00 -0000 https://status.ponlponl123.com/incident/814288#1edc26acf9f5ebcfb7419fbeb700ed943482599c31be882ecf1fc3df1252800e Storage system (included CDN) will temporary unreachable during maintainance. https://status.ponlponl123.com/incident/723573 Sun, 07 Sep 2025 17:00:21 -0000 https://status.ponlponl123.com/incident/723573#8356382da60cface7fa718dc638be7d6c027ca4f85956a4068266bc8642a62f9 We are maintaining our Internal Firewall for maximum performance, availability and stability. https://status.ponlponl123.com/incident/715795 Sun, 31 Aug 2025 12:20:00 -0000 https://status.ponlponl123.com/incident/715795#8edc0b3034989937212f6fa099422845ecda18b49cc5f01358a0948644b92a64 We're currently migrating our infrastructure from rke2 to k3s cuz rke2 required more resources but our each machine have a limit budget to handle it. https://status.ponlponl123.com/incident/708605 Tue, 19 Aug 2025 16:00:00 -0000 https://status.ponlponl123.com/incident/708605#08facbfd082cbde4db311ad38fc7d67cb497a239b15768444d1bb82b3de4fb8c We apologize for the inconvenience. We are migrating our infrastructure from microk8s to RKE2 for greater stability. As we expanded our infrastructure, microk8s began to malfunction. After rebooting each node, our microk8s no longer functioned properly. Therefore, we are taking this opportunity to migrate to a more stable, production-grade infrastructure than microk8s. https://status.ponlponl123.com/incident/706151 Fri, 15 Aug 2025 11:16:00 -0000 https://status.ponlponl123.com/incident/706151#1c1672290a35785d5a02d3de7eb93629e55dfbb718761acc0bc922ab201316ed Fixed! https://status.ponlponl123.com/incident/706154 Thu, 14 Aug 2025 16:57:00 -0000 https://status.ponlponl123.com/incident/706154#0cc31491e2c16bd1658245afcb7069a1f3e3d7995c93b7c93e1de10e6d643a1d We're temporary degraded our database cluster to only node to maintenance. https://status.ponlponl123.com/incident/706151 Thu, 14 Aug 2025 16:55:00 -0000 https://status.ponlponl123.com/incident/706151#55c1d8733f62ff1f03b6c80a380eb17ca98238c0e9c7e908a05984e53e7389f3 We're temporary degraded our database cluster to only node to maintenance. https://status.ponlponl123.com/incident/706071 Thu, 14 Aug 2025 16:55:00 -0000 https://status.ponlponl123.com/incident/706071#39484c0bc423910e116744785b161255effb3d956746c3b78b3adf3a18bfaacf Fixed! https://status.ponlponl123.com/incident/706071 Thu, 14 Aug 2025 14:21:00 -0000 https://status.ponlponl123.com/incident/706071#3cfe1200504dda80ab911b9faf7ad620cfadc24c0341375b0f13faaf5646996a We're coding more error handlers for handle our down time as soon as possible, sorry for the outage service. https://status.ponlponl123.com/incident/706037 Thu, 14 Aug 2025 13:26:00 -0000 https://status.ponlponl123.com/incident/706037#87d7bb69e945546ec4eb5191eea1e71b303b60f41ca6376c80290284650ea4bc All service recovered! https://status.ponlponl123.com/incident/705568 Thu, 14 Aug 2025 12:30:00 -0000 https://status.ponlponl123.com/incident/705568#d50fca46e00a87aaaa3cc12a9a0fd67712a4aaa4b66055cbe7983d49c1c8eda4 Static storage server recovered! https://status.ponlponl123.com/incident/706037 Thu, 14 Aug 2025 04:35:00 -0000 https://status.ponlponl123.com/incident/706037#16343b1d0fb77a9bfccbfb506744c8c11b9653f67f87f281e0432d162c14ff62 We're trying to restarting it as possible (internal remote is not working too) https://status.ponlponl123.com/incident/706037 Thu, 14 Aug 2025 04:34:00 -0000 https://status.ponlponl123.com/incident/706037#654009b7dcda1a41596677fd2b30d633428c32dd8f742f0e8e61fa45e5848d0d Our Master K8S Node not responding https://status.ponlponl123.com/incident/706037 Thu, 14 Aug 2025 04:07:00 -0000 https://status.ponlponl123.com/incident/706037#c962b32551fe6693c7b14210561289769b72b0d57f8dfcda9b2de3271c7422ba Our Internal Firewall not response to any requests https://status.ponlponl123.com/incident/705568 Wed, 13 Aug 2025 15:57:00 -0000 https://status.ponlponl123.com/incident/705568#1fce892b96760db2c7438dc29424465bb0d29626ee52d388d02a7787d3cfefd5 Sorry for outage service, i'm now going to recovery it. this will take time for a while or a few days. https://status.ponlponl123.com/incident/626199 Sat, 26 Jul 2025 17:11:00 -0000 https://status.ponlponl123.com/incident/626199#5bf8613ea11a553ba4e0cd6f438bd2d453cb981b536154b4970414d96369cd99 Issue solved https://status.ponlponl123.com/incident/626199 Sat, 26 Jul 2025 03:33:00 -0000 https://status.ponlponl123.com/incident/626199#634f72f352ae9b677e19acdccff3bf76686e4821943e211735791e8079a563b0 Due to the current conflict on the Thailand-Cambodian border, in order for all relevant officials to be able to work effectively, we reserve the right to temporarily suspend our services, including software and radio services, as well as satellite networks. We understand that the inability to access and/or use these services may cause damage and loss at the very least. However, in order to protect Thailand's sovereignty to the best of our ability, we must migrate our services and infrastructure systems before everything returns to normal. With deep concern and sorrow for the current conflict on the Thai-Cambodian border, which has resulted in injuries, loss of life, and damage to communities, including civilian targets, the lives and peace of the people must not be used as a tool in any conflict. The team condemns all violence and attacks on innocent people, regardless of the reason or demand, and reaffirms the voice of the public: We do not support war and violence in any form. We call on both sides to return to negotiations and find a peaceful and sustainable solution for the safety and well-being of the people of both countries. We would like to send our encouragement and condolences to all the families of the victims. Team Pattarapong.Dev Network and infrastructure service providers, open source developers Ponlponl123 Labs and Ponlponl123. https://status.ponlponl123.com/incident/598669 Sat, 07 Jun 2025 16:59:00 -0000 https://status.ponlponl123.com/incident/598669#5f79f3b28d59b538a9400074a9943ee04c4dac53551c59f9f2174ea62f4e0b7a Resolved https://status.ponlponl123.com/incident/598669 Sat, 07 Jun 2025 15:00:00 -0000 https://status.ponlponl123.com/incident/598669#ae24069a532c66122a1ba7afc9b5ee492f5ec5efbefb708b08e19f88d7cb4dcb Our Internal-Health-Check-API is currently having some issues, that will show up services is down in Status Page but actually that service is still operational. https://status.ponlponl123.com/incident/559983 Sun, 11 May 2025 05:00:00 -0000 https://status.ponlponl123.com/incident/559983#41e47cd85ae624f04fd17d3f4e69066aa63bd3035888659b3baa0bec6a32f4b3 We're currently maintenance some of our k8s nodes and our proxy on 1st networking layer may temporary unavailable. https://status.ponlponl123.com/incident/559685 Sat, 10 May 2025 11:55:55 -0000 https://status.ponlponl123.com/incident/559685#aea4322af57e733c3c0eee4674bd6746487ce1f157969e6693649cde4097b7f6 Maintenance completed https://status.ponlponl123.com/incident/559685 Sat, 10 May 2025 10:55:55 -0000 https://status.ponlponl123.com/incident/559685#a8d64ba753f36ddd95886e2f70d003a79364ae0851b953743e0afa5f80981933 We're currently booting up our machine back to operate