Incidents reported on status page for Thalassa Cloud https://status.thalassa.cloud/ https://d1lppblt9t2x15.cloudfront.net/logos/9c28a5906f34c3e0539befb2af236886.png https://status.thalassa.cloud/ en https://status.thalassa.cloud/incident/784692 Thu, 11 Dec 2025 21:02:00 -0000 https://status.thalassa.cloud/incident/784692#26110fb89b6c8b465a8f9c23a4b3aed95a836457e7d4115187864828724cbab4 We have not seen any issues since our last update. We consider this incident to be resolved. ## Incident Trigger The incident has been triggered by an internal network component that did not fully recover after a restart. This is normally a regular maintenance task, without impact for customers, however failed this time. We are performing further investigation and testing into the exact root cause, so we can adjust procedures, scripts and health checking to avoid this in the future. ## Impact A subset of loadbalancers, natgateways and VMs have been impacted by this incident, as they were running on the affected physical machines. ## Actions taken We have moved away any workloads on the impacted machines. In a few cases, autohealing triggered for Kubernetes nodes, automatically replacing an unhealthy node. If you have any questions, please reach out to our helpdesk (support@thalassa.cloud). https://status.thalassa.cloud/incident/784692 Thu, 11 Dec 2025 21:02:00 -0000 https://status.thalassa.cloud/incident/784692#26110fb89b6c8b465a8f9c23a4b3aed95a836457e7d4115187864828724cbab4 We have not seen any issues since our last update. We consider this incident to be resolved. ## Incident Trigger The incident has been triggered by an internal network component that did not fully recover after a restart. This is normally a regular maintenance task, without impact for customers, however failed this time. We are performing further investigation and testing into the exact root cause, so we can adjust procedures, scripts and health checking to avoid this in the future. ## Impact A subset of loadbalancers, natgateways and VMs have been impacted by this incident, as they were running on the affected physical machines. ## Actions taken We have moved away any workloads on the impacted machines. In a few cases, autohealing triggered for Kubernetes nodes, automatically replacing an unhealthy node. If you have any questions, please reach out to our helpdesk (support@thalassa.cloud). https://status.thalassa.cloud/incident/784692 Thu, 11 Dec 2025 21:02:00 -0000 https://status.thalassa.cloud/incident/784692#26110fb89b6c8b465a8f9c23a4b3aed95a836457e7d4115187864828724cbab4 We have not seen any issues since our last update. We consider this incident to be resolved. ## Incident Trigger The incident has been triggered by an internal network component that did not fully recover after a restart. This is normally a regular maintenance task, without impact for customers, however failed this time. We are performing further investigation and testing into the exact root cause, so we can adjust procedures, scripts and health checking to avoid this in the future. ## Impact A subset of loadbalancers, natgateways and VMs have been impacted by this incident, as they were running on the affected physical machines. ## Actions taken We have moved away any workloads on the impacted machines. In a few cases, autohealing triggered for Kubernetes nodes, automatically replacing an unhealthy node. If you have any questions, please reach out to our helpdesk (support@thalassa.cloud). https://status.thalassa.cloud/incident/784692 Thu, 11 Dec 2025 20:28:00 -0000 https://status.thalassa.cloud/incident/784692#fb67566ac4e42bc171455abb91691946ab7deba8a94763fd5910b92cf787ad3a Our monitoring indicates that all systems have recovered. For some customers, Kubernetes node autohealing has kicked in and recycled the Kubernetes machines with new ones automatically during the incident. We are continuing monitoring and the investigating the root cause. https://status.thalassa.cloud/incident/784692 Thu, 11 Dec 2025 20:28:00 -0000 https://status.thalassa.cloud/incident/784692#fb67566ac4e42bc171455abb91691946ab7deba8a94763fd5910b92cf787ad3a Our monitoring indicates that all systems have recovered. For some customers, Kubernetes node autohealing has kicked in and recycled the Kubernetes machines with new ones automatically during the incident. We are continuing monitoring and the investigating the root cause. https://status.thalassa.cloud/incident/784692 Thu, 11 Dec 2025 20:28:00 -0000 https://status.thalassa.cloud/incident/784692#fb67566ac4e42bc171455abb91691946ab7deba8a94763fd5910b92cf787ad3a Our monitoring indicates that all systems have recovered. For some customers, Kubernetes node autohealing has kicked in and recycled the Kubernetes machines with new ones automatically during the incident. We are continuing monitoring and the investigating the root cause. https://status.thalassa.cloud/incident/784692 Thu, 11 Dec 2025 20:20:00 -0000 https://status.thalassa.cloud/incident/784692#e82dae998e5f6dae72271484aa839a78a0d3750d96ce3402f8ed670fa40bbba9 The issues seem isolated to a small subset of machines. We are currently investigating and moving workloads to healthy machines. https://status.thalassa.cloud/incident/784692 Thu, 11 Dec 2025 20:20:00 -0000 https://status.thalassa.cloud/incident/784692#e82dae998e5f6dae72271484aa839a78a0d3750d96ce3402f8ed670fa40bbba9 The issues seem isolated to a small subset of machines. We are currently investigating and moving workloads to healthy machines. https://status.thalassa.cloud/incident/784692 Thu, 11 Dec 2025 20:20:00 -0000 https://status.thalassa.cloud/incident/784692#e82dae998e5f6dae72271484aa839a78a0d3750d96ce3402f8ed670fa40bbba9 The issues seem isolated to a small subset of machines. We are currently investigating and moving workloads to healthy machines. https://status.thalassa.cloud/incident/784692 Thu, 11 Dec 2025 20:16:00 -0000 https://status.thalassa.cloud/incident/784692#dedf0a842bc25e71e68ee0e8c9843cc08d172500d1088d1a69064780ec7c0f05 We currently have a network issue. We are investigating. https://status.thalassa.cloud/incident/784692 Thu, 11 Dec 2025 20:16:00 -0000 https://status.thalassa.cloud/incident/784692#dedf0a842bc25e71e68ee0e8c9843cc08d172500d1088d1a69064780ec7c0f05 We currently have a network issue. We are investigating. https://status.thalassa.cloud/incident/784692 Thu, 11 Dec 2025 20:16:00 -0000 https://status.thalassa.cloud/incident/784692#dedf0a842bc25e71e68ee0e8c9843cc08d172500d1088d1a69064780ec7c0f05 We currently have a network issue. We are investigating. https://status.thalassa.cloud/incident/756431 Sun, 02 Nov 2025 19:30:00 -0000 https://status.thalassa.cloud/incident/756431#e94c34b855aa88d26f2b25c49bce3eb3a5fb900441292e4dbeb218fc4ffb7d69 Maintenance completed https://status.thalassa.cloud/incident/756431 Sun, 02 Nov 2025 17:00:00 -0000 https://status.thalassa.cloud/incident/756431#00cf5d51ad6cb83a1a70f695d3ed054ae61e9697df976cbaefaa2caeb6cd4009 The Platform API is currently undergoing maintenance. Some services may be temporarily unavailable or experience degraded performance. VPC service may experience errors or delays in provisioning.