<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Exoscale Status - Incident History</title>
    <link>https://exoscalestatus.com</link>
    <atom:link rel="self" href="https://exoscalestatus.com/history.rss" type="application/rss+xml"/>
    <description>Incident history of Exoscale</description>
    <pubDate>Thu, 19 Nov 2026 16:00:00 +0000</pubDate>
    <item>
      <title>[Compute API] Planned maintenance</title>
      <pubDate>Mon, 16 Nov 2026 15:09:09 +0000</pubDate>
      <category domain="event:start">Tue, 8 Dec 2026 20:00:00 +0000</category>
      <category domain="event:end">Tue, 8 Dec 2026 21:00:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-GVA-2, API, CH-DK-2, API, DE-FRA-1, API, DE-MUC-1, API, AT-VIE-1, API, AT-VIE-2, API, BG-SOF-1, API, HR-ZAG-1, API&lt;/p&gt;&lt;p&gt;&lt;small&gt;November 16, 2026 · 16:04 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are going to proceed with a maintenance on the Compute orchestrator that will requires a short stop of the API.  &lt;br /&gt;
Only the API will be impacted, running instances will not be impacted.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/256249</link>
      <guid>https://exoscalestatus.com/incidents/256249</guid>
    </item>
    <item>
      <title>[CH-DK-2] Network Maintenance - Edge Routers | Backup date</title>
      <pubDate>Wed, 11 Nov 2026 10:13:46 +0000</pubDate>
      <category domain="event:start">Thu, 26 Nov 2026 20:00:00 +0000</category>
      <category domain="event:end">Fri, 27 Nov 2026 05:00:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-DK-2, API, Block Storage, Compute, Concrete AI, Dedicated Inference, Key Management Service KMS, Managed Database service DBaaS, Managed Kubernetes SKS, Managed Private Networks, Network Internet Transit Connectivity, Network Load Balancer NLB, Object Storage SOS&lt;/p&gt;&lt;p&gt;&lt;small&gt;November 11, 2026 · 11:12 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
As part of ongoing efforts to improve network resilience and reliability, we are performing a scheduled maintenance to migrate the edge routers in our CH-DK-2 zone to the next generation of hardware.&lt;/p&gt;
&lt;p&gt;
No customer impact is expected.&lt;/p&gt;
&lt;p&gt;
We will provide further information as the work progresses.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/255732</link>
      <guid>https://exoscalestatus.com/incidents/255732</guid>
    </item>
    <item>
      <title>[CH-DK-2] Network Maintenance - Edge Routers</title>
      <pubDate>Wed, 11 Nov 2026 10:13:33 +0000</pubDate>
      <category domain="event:start">Wed, 25 Nov 2026 20:00:00 +0000</category>
      <category domain="event:end">Thu, 26 Nov 2026 05:00:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-DK-2, API, Block Storage, Compute, Concrete AI, Dedicated Inference, Key Management Service KMS, Managed Database service DBaaS, Managed Kubernetes SKS, Managed Private Networks, Network Internet Transit Connectivity, Network Load Balancer NLB, Object Storage SOS&lt;/p&gt;&lt;p&gt;&lt;small&gt;November 25, 2026 · 21:00 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
As part of ongoing efforts to improve network resilience and reliability, we are performing a scheduled maintenance to migrate the edge routers in our CH-DK-2 zone to the next generation of hardware.&lt;/p&gt;
&lt;p&gt;
No customer impact is expected.&lt;/p&gt;
&lt;p&gt;
We will provide further information as the work progresses.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/255731</link>
      <guid>https://exoscalestatus.com/incidents/255731</guid>
    </item>
    <item>
      <title>Scheduled Maintenance: Concrete AI Dedicated Inference</title>
      <pubDate>Thu, 19 Nov 2026 16:00:00 +0000</pubDate>
      <category domain="event:start">Thu, 19 Nov 2026 15:00:00 +0000</category>
      <category domain="event:end">Thu, 19 Nov 2026 16:00:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-GVA-2, Concrete AI, Dedicated Inference, CH-DK-2, Concrete AI, Dedicated Inference, DE-FRA-1, Concrete AI, Dedicated Inference, DE-MUC-1, Concrete AI, Dedicated Inference, AT-VIE-1, Concrete AI, Dedicated Inference, AT-VIE-2, Concrete AI, Dedicated Inference, BG-SOF-1, Concrete AI, Dedicated Inference, HR-ZAG-1, Concrete AI, Dedicated Inference&lt;/p&gt;&lt;p&gt;&lt;small&gt;November 19, 2026 · 17:00 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance has been concluded as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November 19, 2026 · 16:00 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November  5, 2026 · 12:00 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We will perform maintenance on the Concrete AI Dedicated Inference service. During the maintenance window, a brief interruption (a few seconds) of traffic to your service endpoints may occur. GPU workloads are not affected and will not be restarted. No action is required on your side.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/255121</link>
      <guid>https://exoscalestatus.com/incidents/255121</guid>
    </item>
    <item>
      <title>[Compute API] Latency and errors increase</title>
      <pubDate>Tue, 17 Nov 2026 15:05:56 +0000</pubDate>
      <category domain="event:start">Tue, 17 Nov 2026 13:03:11 +0000</category>
      <category domain="event:end">Tue, 17 Nov 2026 15:05:56 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Partial outage&lt;/strong&gt; - CH-GVA-2, API, CH-DK-2, API, DE-FRA-1, API, DE-MUC-1, API, AT-VIE-1, API, AT-VIE-2, API, BG-SOF-1, API, HR-ZAG-1, API&lt;/p&gt;&lt;p&gt;&lt;small&gt;November 17, 2026 · 15:57 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The root cause was identified.  &lt;br /&gt;
The service is stable and the load on our database is back to baseline.  &lt;br /&gt;
We’re closing this incident.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November 17, 2026 · 15:33 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The service is still stable.  &lt;br /&gt;
We’re maintaining the incident in monitoring while we’re making the last validations.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November 17, 2026 · 15:16 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Latency and errors are still all good. We’re keeping the incident in monitoring for now.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November 17, 2026 · 14:49 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The situation remain stable.  &lt;br /&gt;
We’re continuing monitoring.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November 17, 2026 · 14:35 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are still monitoring the situation, all services seem to be running as expected.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November 17, 2026 · 14:24 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The service is back and should work as expected.  &lt;br /&gt;
We’re monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November 17, 2026 · 14:03 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We have an increase of latency and error on the Compute API.  &lt;br /&gt;
We’re investigating the issue.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/256385</link>
      <guid>https://exoscalestatus.com/incidents/256385</guid>
    </item>
    <item>
      <title>[Network] Increased internet network latencies and packet loss</title>
      <pubDate>Thu, 12 Nov 2026 22:46:06 +0000</pubDate>
      <category domain="event:start">Thu, 12 Nov 2026 22:09:14 +0000</category>
      <category domain="event:end">Thu, 12 Nov 2026 22:46:06 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Partial outage&lt;/strong&gt; - BG-SOF-1, Network Internet Transit Connectivity&lt;/p&gt;&lt;p&gt;&lt;small&gt;November 12, 2026 · 23:44 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The incident has been resolved. It was related to the ongoing maintenance. A network link failed of a rack while in reduced redundancy mode due to the maintenance. Only that compute rack was affected.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November 12, 2026 · 23:23 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Connectivity has been restored. We are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November 12, 2026 · 23:15 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The issue has been identified. We are applying physical mitigation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November 12, 2026 · 23:11 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The issue seems related to an ongoing maintenance &lt;a target=&quot;_blank&quot; href=&quot;https://exoscalestatus.com/incidents/254534&quot;&gt;https://exoscalestatus.com/incidents/254534&lt;/a&gt; We are investigating&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November 12, 2026 · 23:09 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are investigating Increased internet network latencies and packet loss. We’ll post an update as soon as we have more information.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/255891</link>
      <guid>https://exoscalestatus.com/incidents/255891</guid>
    </item>
    <item>
      <title>[BG-SOF-1] Core Network - Hardware replacement</title>
      <pubDate>Thu, 12 Nov 2026 23:07:42 +0000</pubDate>
      <category domain="event:start">Thu, 12 Nov 2026 21:00:01 +0000</category>
      <category domain="event:end">Thu, 12 Nov 2026 23:07:42 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - BG-SOF-1, API, Block Storage, Compute, Concrete AI, Dedicated Inference, Key Management Service KMS, Managed Database service DBaaS, Managed Kubernetes SKS, Managed Private Networks, Network Internet Transit Connectivity, Network Load Balancer NLB, Object Storage SOS&lt;/p&gt;&lt;p&gt;&lt;small&gt;November 13, 2026 · 00:06 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance has been concluded as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November 12, 2026 · 22:00 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November  2, 2026 · 13:44 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
As part of our ongoing commitment to improve our core network architecture on a global scale, we are implementing significant changes to our networking infrastructure in BG-SOF-1.&lt;/p&gt;
&lt;p&gt;
We don’t expect this intervention to have any impact on operations and services, however a TCP session reset could be seen on the ongoing connections a couple of times.&lt;/p&gt;
&lt;p&gt;
Please be assured that we will provide regular updates on the progress of this deployment. Your satisfaction and uninterrupted service remains our top priority.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/254534</link>
      <guid>https://exoscalestatus.com/incidents/254534</guid>
    </item>
    <item>
      <title>[BG-SOF-1] Core Network - Hardware replacement</title>
      <pubDate>Wed, 11 Nov 2026 05:00:00 +0000</pubDate>
      <category domain="event:start">Tue, 10 Nov 2026 21:00:00 +0000</category>
      <category domain="event:end">Wed, 11 Nov 2026 05:00:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - BG-SOF-1, API, Block Storage, Compute, Concrete AI, Dedicated Inference, Key Management Service KMS, Managed Database service DBaaS, Managed Kubernetes SKS, Managed Private Networks, Network Internet Transit Connectivity, Network Load Balancer NLB, Object Storage SOS&lt;/p&gt;&lt;p&gt;&lt;small&gt;November 11, 2026 · 06:00 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance has been concluded as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November 10, 2026 · 22:00 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November  2, 2026 · 13:41 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
As part of our ongoing commitment to improve our core network architecture on a global scale, we are implementing significant changes to our networking infrastructure in BG-SOF-1.&lt;/p&gt;
&lt;p&gt;
We don’t expect this intervention to have any impact on operations and services, however a TCP session reset could be seen on the ongoing connections a couple of times.&lt;/p&gt;
&lt;p&gt;
Please be assured that we will provide regular updates on the progress of this deployment. Your satisfaction and uninterrupted service remains our top priority.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/254533</link>
      <guid>https://exoscalestatus.com/incidents/254533</guid>
    </item>
    <item>
      <title>AI API operations are unavailable</title>
      <pubDate>Fri, 6 Nov 2026 17:26:16 +0000</pubDate>
      <category domain="event:start">Fri, 6 Nov 2026 17:01:23 +0000</category>
      <category domain="event:end">Fri, 6 Nov 2026 17:26:16 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Partial outage&lt;/strong&gt; - CH-GVA-2, Concrete AI, Dedicated Inference, CH-DK-2, Concrete AI, Dedicated Inference, DE-FRA-1, Concrete AI, Dedicated Inference, DE-MUC-1, Concrete AI, Dedicated Inference, AT-VIE-1, Concrete AI, Dedicated Inference, AT-VIE-2, Concrete AI, Dedicated Inference, BG-SOF-1, Concrete AI, Dedicated Inference, HR-ZAG-1, Concrete AI, Dedicated Inference&lt;/p&gt;&lt;p&gt;&lt;small&gt;November  6, 2026 · 18:26 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Incident closed.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November  6, 2026 · 18:10 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Services are back to nominal.  &lt;br /&gt;
We are still monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November  6, 2026 · 18:04 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We found the root cause and mitigated it.  &lt;br /&gt;
Services should be back to nominal.&lt;/p&gt;
&lt;p&gt;
We are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November  6, 2026 · 18:01 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Interactions with the AI dedicated inference service API are currently not possible.  &lt;br /&gt;
Inference itself is not impacted.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/255244</link>
      <guid>https://exoscalestatus.com/incidents/255244</guid>
    </item>
    <item>
      <title>Concrete AI Dedicated Inference</title>
      <pubDate>Thu, 5 Nov 2026 16:26:47 +0000</pubDate>
      <category domain="event:start">Thu, 5 Nov 2026 15:56:16 +0000</category>
      <category domain="event:end">Thu, 5 Nov 2026 16:26:47 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Partial outage&lt;/strong&gt; - AT-VIE-2, Concrete AI, Dedicated Inference&lt;/p&gt;&lt;p&gt;&lt;small&gt;November  5, 2026 · 17:25 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Memory issues around the ingress were identified and resolved.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November  5, 2026 · 16:56 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are investigating ingress traffic to service endpoints not working anymore.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/255152</link>
      <guid>https://exoscalestatus.com/incidents/255152</guid>
    </item>
    <item>
      <title>[CH-DK-2] Network Maintenance - VPN</title>
      <pubDate>Tue, 3 Nov 2026 09:28:00 +0000</pubDate>
      <category domain="event:start">Tue, 3 Nov 2026 08:00:00 +0000</category>
      <category domain="event:end">Tue, 3 Nov 2026 09:28:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-DK-2, API, Block Storage, Compute, Concrete AI, Dedicated Inference, Key Management Service KMS, Managed Database service DBaaS, Managed Kubernetes SKS, Managed Private Networks, Network Internet Transit Connectivity, Network Load Balancer NLB, Object Storage SOS&lt;/p&gt;&lt;p&gt;&lt;small&gt;November  3, 2026 · 10:26 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The maintenance was successfully completed. &lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;November  3, 2026 · 09:00 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October 30, 2026 · 15:52 CET&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
As part of ongoing efforts to improve network resilience and reliability, we are performing scheduled maintenance to upgrade a VPN in our CH-DK-2 zone to the next generation of software.&lt;/p&gt;
&lt;p&gt;
No customer impact is expected.&lt;/p&gt;
&lt;p&gt;
We will provide further information as the work progresses.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/254388</link>
      <guid>https://exoscalestatus.com/incidents/254388</guid>
    </item>
    <item>
      <title>[CH-GVA-2] Network Maintenance - Edge Routers | Backup date</title>
      <pubDate>Thu, 15 Oct 2026 00:05:28 +0000</pubDate>
      <category domain="event:start">Thu, 15 Oct 2026 19:00:00 +0000</category>
      <category domain="event:end">Fri, 16 Oct 2026 04:00:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-GVA-2, Network Internet Transit Connectivity&lt;/p&gt;&lt;p&gt;&lt;small&gt;October 15, 2026 · 02:04 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Canceled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The scheduled maintenance was completed as planned – backup maintenance window canceled. &lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  2, 2026 · 10:59 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
As part of ongoing efforts to improve network resilience and reliability, we are performing a scheduled maintenance to migrate the edge routers in our CH-GVA-2 zone to the next generation of hardware.&lt;/p&gt;
&lt;p&gt;
No customer impact is expected.&lt;/p&gt;
&lt;p&gt;
We will provide further information as the work progresses.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/250392</link>
      <guid>https://exoscalestatus.com/incidents/250392</guid>
    </item>
    <item>
      <title>[CH-GVA-2] Network Maintenance - Edge Routers</title>
      <pubDate>Thu, 15 Oct 2026 04:00:00 +0000</pubDate>
      <category domain="event:start">Wed, 14 Oct 2026 19:00:00 +0000</category>
      <category domain="event:end">Thu, 15 Oct 2026 04:00:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-GVA-2, Network Internet Transit Connectivity&lt;/p&gt;&lt;p&gt;&lt;small&gt;October 15, 2026 · 06:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance has been concluded as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October 15, 2026 · 02:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The scheduled maintenance was completed as planned.  &lt;/p&gt;
&lt;p&gt;
No service impact was observed during the maintenance window.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October 14, 2026 · 21:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  2, 2026 · 10:48 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
As part of ongoing efforts to improve network resilience and reliability, we are performing a scheduled maintenance to migrate the edge routers in our CH-GVA-2 zone to the next generation of hardware.&lt;/p&gt;
&lt;p&gt;
No customer impact is expected.&lt;/p&gt;
&lt;p&gt;
We will provide further information as the work progresses.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/250391</link>
      <guid>https://exoscalestatus.com/incidents/250391</guid>
    </item>
    <item>
      <title>[API] Increased Error Rates and Latencies</title>
      <pubDate>Fri, 9 Oct 2026 15:08:19 +0000</pubDate>
      <category domain="event:start">Fri, 9 Oct 2026 14:34:00 +0000</category>
      <category domain="event:end">Fri, 9 Oct 2026 15:08:19 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Partial outage&lt;/strong&gt; - CH-GVA-2, API, CH-DK-2, API, DE-FRA-1, API, DE-MUC-1, API, AT-VIE-1, API, AT-VIE-2, API, BG-SOF-1, API, HR-ZAG-1, API&lt;/p&gt;&lt;p&gt;&lt;small&gt;October  9, 2026 · 17:08 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The issue has been resolved&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  9, 2026 · 17:02 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
All systems are back to normal. We continue to monitor the situation&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  9, 2026 · 16:54 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Mitigation have been applied. We are monitoring the situation for recovery&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  9, 2026 · 16:52 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The root cause has been identified, we are working towards mitigation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  9, 2026 · 16:48 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The situation did not improve. We are continuing investigations.&lt;/p&gt;
&lt;p&gt;
All Mutating compute related API calls are currently impacted.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  9, 2026 · 16:40 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We have reverted a compute orchestrator release that was being deployed. We are monitoring for situation improvements.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  9, 2026 · 16:35 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are investigating increased errors rate with Compute related API calls&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  9, 2026 · 16:34 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are investigating an increased error rates and latencies on the API. We’ll post an update as soon as we have more information.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/251186</link>
      <guid>https://exoscalestatus.com/incidents/251186</guid>
    </item>
    <item>
      <title>[API] Increased Error Rates and Latencies</title>
      <pubDate>Fri, 9 Oct 2026 11:51:35 +0000</pubDate>
      <category domain="event:start">Thu, 8 Oct 2026 13:27:45 +0000</category>
      <category domain="event:end">Thu, 8 Oct 2026 15:57:49 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Major outage&lt;/strong&gt; - Global, Portal, CH-GVA-2, API, Concrete AI, Dedicated Inference, Managed Kubernetes SKS, Network Load Balancer NLB&lt;/p&gt;&lt;p&gt;&lt;small&gt;October  9, 2026 · 13:48 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Post-mortem&lt;/strong&gt;&lt;/p&gt;&lt;h1&gt;
Post-mortem&lt;/h1&gt;
&lt;h2&gt;
Summary&lt;/h2&gt;
&lt;p&gt;
On 2026-10-08, between 13:18 and 14:52 UTC, the Exoscale public API in ch-gva-2, the global Portal, the Network Load Balancer (NLB) service in ch-gva-2 and the Scalable Kubernetes Service (SKS) in ch-gva-2 were unavailable or heavily degraded.&lt;/p&gt;
&lt;p&gt;
During infrastructure work to prepare a new Exoscale zone, a configuration change was applied by mistake to our production platform in ch-gva-2. This change detached firewall rules (security groups) from the nodes that host our reverse proxies, NLBs and SKS control planes. Inbound traffic to these nodes was then dropped.&lt;/p&gt;
&lt;p&gt;
Recovery took longer than we wanted. Several of the internal tools we normally use to fix this kind of problem relied upon the services that were down. We restored the missing rules through an emergency procedure, and the first attempt did not take effect, which delayed recovery by about one hour.&lt;/p&gt;
&lt;p&gt;
Customer instances kept running for the whole incident. Data was not affected.&lt;/p&gt;
&lt;h2&gt;
Impact&lt;/h2&gt;
&lt;p&gt;
From 13:18 to 14:52 UTC:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Public API (ch-gva-2): unavailable. Many clients (the &lt;code class=&quot;inline&quot;&gt;exo&lt;/code&gt; CLI, Terraform and other integrations) use ch-gva-2 by default, for example to list zones.  Because of this, creating, updating, deleting and listing resources failed or hung in all zones.  &lt;/li&gt;
  &lt;li&gt;
Network Load Balancers (ch-gva-2): unavailable or intermittent. Services exposed through an NLB were unreachable or flapping.  &lt;/li&gt;
  &lt;li&gt;
SKS (ch-gva-2): the Kubernetes control plane of clusters was unreachable.  Worker nodes and running workloads were not affected unless they were exposed through an NLB.  &lt;/li&gt;
  &lt;li&gt;
Portal (global): unavailable.  &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
From 14:52 to about 15:45 UTC, there were residual effects:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Some SKS background operations failed because one of our internal secrets backend nodes were overwhelmed after service was restored.  &lt;/li&gt;
  &lt;li&gt;
Some cross-zone bucket replication into ch-gva-2 timed out. All replication tasks recovered afterwards and got re-executed.  &lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;
Timeline UTC&lt;/h2&gt;
&lt;ul&gt;
  &lt;li&gt;
13:18: A configuration change meant for a new zone is applied to the ch-gva-2 production platform by mistake. Security groups are detached from the reverse-proxy, NLB and SKS control-plane nodes. The public API, the Portal and NLBs become unreachable.  &lt;/li&gt;
  &lt;li&gt;
13:24: Incident declared, response team assembled.  &lt;/li&gt;
  &lt;li&gt;
13:40 -&gt; 14:40: The team restores the security group associations through an emergency procedure. Our usual tooling cannot be used because it depends on the impacted API. The changes do not take effect on the hypervisors, and traffic is still dropped.  &lt;/li&gt;
  &lt;li&gt;
14:40: Root cause of the failed restoration found: the corrections had been written to a read replica of the database instead of the primary.  &lt;/li&gt;
  &lt;li&gt;
14:47: Corrections applied to the primary database.  &lt;/li&gt;
  &lt;li&gt;
14:48: NLB nodes start recovering.  &lt;/li&gt;
  &lt;li&gt;
14:50: Public API and &lt;code class=&quot;inline&quot;&gt;exo&lt;/code&gt; CLI operational again.  &lt;/li&gt;
  &lt;li&gt;
14:52: Portal operational again. End of main impact.  &lt;/li&gt;
  &lt;li&gt;
15:06: SKS health checks green in all zones.  &lt;/li&gt;
  &lt;li&gt;
15:20 -&gt; 15:40: An internal secrets backend node, overloaded by the backlog of requests, causes some SKS background jobs to fail. The node is restarted at 15:34 and the service is healthy again at 15:40.  &lt;/li&gt;
  &lt;li&gt;
~15:45: Bucket replication errors into ch-gva-2 stop.  &lt;/li&gt;
  &lt;li&gt;
15:57: Incident closed.  &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
&lt;strong&gt;Total duration of main impact: 1h34.&lt;/strong&gt;&lt;/p&gt;
&lt;h2&gt;
Root cause&lt;/h2&gt;
&lt;p&gt;
Our infrastructure-as-code configuration is shared across zones. A change prepared for the new zone was planned and applied against the ch-gva-2 production platform instead of the new platform. It removed the security groups that allow inbound traffic on the nodes hosting our reverse proxies, NLBs and SKS control planes.&lt;/p&gt;
&lt;p&gt;
Two factors made the incident last longer:&lt;/p&gt;
&lt;ol&gt;
  &lt;li&gt;
Circular dependencies: The deployment pipeline that applied the change lost access to the API and could not complete or report its state. Several internal tools and communication channels were also hosted behind the impacted reverse proxies.  &lt;/li&gt;
  &lt;li&gt;
Emergency procedure error: Because the API was down, we had to restore the security groups at a lower level. Using direct writes to the database opened us up to the risk of human errors, which caused us to initially write the changes incorrectly. As a result, they had no effect for about one hour.  &lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;
What We Learned&lt;/h2&gt;
&lt;ul&gt;
  &lt;li&gt;
Infrastructure changes need stronger safeguards. Our IAC configuration is shared across zones and makes it possible for a change to impact multiple zones. While we already have strong safeguards against any resource deletion, we need to improve our safeguards to catch removals in mutating changes.  &lt;/li&gt;
  &lt;li&gt;
Emergency procedures must be reliable. Restoring network configuration without the public API was error-prone and slow. We need to improve our tooling for these situations, gaining efficiency and confidence while also avoiding direct database access.  &lt;/li&gt;
  &lt;li&gt;
Global operations depend too much on one zone. Our public, internal tooling and integrations use ch-gva-2 by default, so a regional outage affected API operations in every zone.  &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
We are actively working on each of these points. We apologize for the disruption. We know many of you depend on the Exoscale API and NLBs for your own services, and we are committed to making sure this kind of change cannot have this impact again.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  8, 2026 · 17:57 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The situation is stable, we are closing this status. A public postmortem will be published in the coming days.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  8, 2026 · 16:54 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Our systems are back to normal, we are monitoring the situation. Every services should be back online.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  8, 2026 · 16:50 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We confirmed some services are recovering, some flaps are to be expected in the coming minutes.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  8, 2026 · 16:44 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
New mitigations are being applied, we will publish new updates shortly.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  8, 2026 · 16:33 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Mitigations are still been applied, they did not solve the ongoing incident. The impact continues on both API services (full impact) &amp; NLB traffic (partial packet loss).&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  8, 2026 · 16:22 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
All mitigations have been applied and the team is monitoring the system. Investigations into the NLB packet loss is ongoing.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  8, 2026 · 16:05 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The team is confirming that all known mitigations have been applied. Another part of the team is investigating packet drops on NLB in Geneva.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  8, 2026 · 15:59 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are still actively working on applying mitigations. NLB services are correctly processing traffic and were not impacted, we are removing them from the impacted scope.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  8, 2026 · 15:53 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are still actively working on applying mitigations, services are still unreachable.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  8, 2026 · 15:44 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are still actively working on mitigations, the impact is extended api, nlb, sks and ai services in ch-gva-2.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  8, 2026 · 15:37 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The source of the problem has been localized and we are actively working on applying mitigations.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  8, 2026 · 15:31 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The impact is confined to the ch-gva-2 zone, the API is working correctly in other zones.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  8, 2026 · 15:27 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are investigating an increased error rates and latencies on the API. We’ll post an update as soon as we have more information.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/251055</link>
      <guid>https://exoscalestatus.com/incidents/251055</guid>
    </item>
    <item>
      <title>[Compute API] Planned maintenance</title>
      <pubDate>Tue, 6 Oct 2026 20:00:00 +0000</pubDate>
      <category domain="event:start">Tue, 6 Oct 2026 19:00:00 +0000</category>
      <category domain="event:end">Tue, 6 Oct 2026 20:00:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-GVA-2, API, CH-DK-2, API, DE-FRA-1, API, DE-MUC-1, API, AT-VIE-1, API, AT-VIE-2, API, BG-SOF-1, API, HR-ZAG-1, API&lt;/p&gt;&lt;p&gt;&lt;small&gt;October  6, 2026 · 22:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance has been concluded as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  6, 2026 · 21:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 18, 2026 · 11:32 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are going to proceed with a maintenance on the Compute orchestrator that will requires a short stop of the API.  &lt;br /&gt;
Only the API will be impacted, running instances will not be impacted.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/249111</link>
      <guid>https://exoscalestatus.com/incidents/249111</guid>
    </item>
    <item>
      <title>[API] Increased Error Rates and Latencies</title>
      <pubDate>Tue, 6 Oct 2026 10:10:10 +0000</pubDate>
      <category domain="event:start">Tue, 6 Oct 2026 08:39:10 +0000</category>
      <category domain="event:end">Tue, 6 Oct 2026 10:10:10 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Major outage&lt;/strong&gt; - CH-GVA-2, API, CH-DK-2, API, DE-FRA-1, API, DE-MUC-1, API, AT-VIE-1, API, AT-VIE-2, API, BG-SOF-1, API, HR-ZAG-1, API&lt;/p&gt;&lt;p&gt;&lt;small&gt;October  6, 2026 · 11:56 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The issue has been resolved.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  6, 2026 · 11:48 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Mitigation have been applied. Services are back to normal. We are monitoring the situation&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  6, 2026 · 11:24 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The situation is still unstable. We are working back on mitigation&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  6, 2026 · 11:15 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The service should be back to normal. We are monitoring the situation&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  6, 2026 · 11:04 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
It appears we are still experiencing transient API issues in some zones. We are investigating&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  6, 2026 · 10:58 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Services are back to normal.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  6, 2026 · 10:55 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are monitoring the services recovery&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  6, 2026 · 10:52 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We identified the root cause and applied mitigation&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  6, 2026 · 10:42 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
API connectivity is impacted for for most of the services. The issue is related to some internal connectivity issue we are facing. We are working to identify the root cause.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  6, 2026 · 10:39 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are investigating an increased error rates and latencies on the API. We’ll post an update as soon as we have more information.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/250726</link>
      <guid>https://exoscalestatus.com/incidents/250726</guid>
    </item>
    <item>
      <title>SKS control plane components migration to new deployment platform</title>
      <pubDate>Wed, 7 Oct 2026 10:32:50 +0000</pubDate>
      <category domain="event:start">Tue, 6 Oct 2026 08:30:00 +0000</category>
      <category domain="event:end">Wed, 7 Oct 2026 10:32:47 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-DK-2, Managed Kubernetes SKS&lt;/p&gt;&lt;p&gt;&lt;small&gt;October  7, 2026 · 12:32 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Migration completed&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  7, 2026 · 11:54 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Workloads migrated, monitoring&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  7, 2026 · 10:29 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Starting migration as scheduled&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  6, 2026 · 10:51 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Postponed&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Postponing to 2026.10.7 8:30 UTC (10:30 CEST)&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  6, 2026 · 10:30 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  5, 2026 · 10:17 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are going to migrate SKS control plane components to a new deployment platform.  &lt;br /&gt;
We estimate that this operation will take approximately 1 and 1/2 hour to achieve.&lt;/p&gt;
&lt;p&gt;
No visible impact is expected from a user perspective.  &lt;br /&gt;
During the maintenance window, both your SKS clusters and the SKS product API will continue to work as expected. The “etcd” backend of your clusters is not in the scope of this migration.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/250529</link>
      <guid>https://exoscalestatus.com/incidents/250529</guid>
    </item>
    <item>
      <title>Network Load Balancer maintenance</title>
      <pubDate>Fri, 2 Oct 2026 11:00:00 +0000</pubDate>
      <category domain="event:start">Fri, 2 Oct 2026 09:30:00 +0000</category>
      <category domain="event:end">Fri, 2 Oct 2026 11:00:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - AT-VIE-2, API, Network Load Balancer NLB&lt;/p&gt;&lt;p&gt;&lt;small&gt;October  2, 2026 · 13:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance has been concluded as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  2, 2026 · 11:30 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 28, 2026 · 10:58 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We will be conducting scheduled maintenance on our Network Load Balancer (NLB).&lt;/p&gt;
&lt;p&gt;
NLB related API requests are expected to not work both for new and existing entities during the window, though no traffic interruption is expected. This work is being performed to support ongoing improvements to our platform.&lt;/p&gt;
&lt;p&gt;
Thank you for your understanding.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/249981</link>
      <guid>https://exoscalestatus.com/incidents/249981</guid>
    </item>
    <item>
      <title>Network Load Balancer maintenance</title>
      <pubDate>Fri, 2 Oct 2026 09:30:00 +0000</pubDate>
      <category domain="event:start">Fri, 2 Oct 2026 08:00:00 +0000</category>
      <category domain="event:end">Fri, 2 Oct 2026 09:30:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - AT-VIE-1, API, Network Load Balancer NLB&lt;/p&gt;&lt;p&gt;&lt;small&gt;October  2, 2026 · 11:30 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance has been concluded as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  2, 2026 · 10:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 28, 2026 · 10:56 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We will be conducting scheduled maintenance on our Network Load Balancer (NLB).&lt;/p&gt;
&lt;p&gt;
NLB related API requests are expected to not work both for new and existing entities during the window, though no traffic interruption is expected. This work is being performed to support ongoing improvements to our platform.&lt;/p&gt;
&lt;p&gt;
Thank you for your understanding.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/249980</link>
      <guid>https://exoscalestatus.com/incidents/249980</guid>
    </item>
    <item>
      <title>Concrete AI Dedicated Inference - Requests ending with 500</title>
      <pubDate>Fri, 2 Oct 2026 11:06:13 +0000</pubDate>
      <category domain="event:start">Thu, 1 Oct 2026 16:01:12 +0000</category>
      <category domain="event:end">Fri, 2 Oct 2026 05:35:42 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Partial outage&lt;/strong&gt; - CH-GVA-2, Concrete AI, Dedicated Inference, CH-DK-2, Concrete AI, Dedicated Inference, DE-FRA-1, Concrete AI, Dedicated Inference, AT-VIE-2, Concrete AI, Dedicated Inference, HR-ZAG-1, Concrete AI, Dedicated Inference&lt;/p&gt;&lt;p&gt;&lt;small&gt;October  2, 2026 · 13:04 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;h1&gt;
Post-mortem&lt;/h1&gt;
&lt;h2&gt;
Summary&lt;/h2&gt;
&lt;p&gt;
On October 1, 2026, during a scheduled maintenance window to migrate to a new AI router, a partial outage occurred affecting Dedicated Inference services. Customers initially received HTTP 404 errors, followed by HTTP 502 errors. The root cause was identified as missing TLS configurations in some customer deployments.&lt;/p&gt;
&lt;h2&gt;
Impact&lt;/h2&gt;
&lt;p&gt;
Requests to impacted Dedicated Inference deployments resulted in errors for approximately 1.5 hours. This impacted all zones where dedicated inference is available.&lt;/p&gt;
&lt;h2&gt;
Timeline&lt;/h2&gt;
&lt;p&gt;
17:00 CET: Migration to the new vLLM router started.  &lt;br /&gt;
17:15 CET: DNS change that resulted in routing issues, causing requests to end up with 404 errors.  &lt;br /&gt;
17:30 CET: The routing issue has been fixed, and HTTP 502 errors were being returned  &lt;br /&gt;
18:00 CET: The incident was escalated as a partial outage  &lt;br /&gt;
18:07 CET: Mitigations are being gradually applied to fix the TLS configurations of the deployments  &lt;br /&gt;
18:21 CET: All deployments across all zones have been successfully patched.  &lt;br /&gt;
18:30 CET: Service back to nominal&lt;/p&gt;
&lt;h2&gt;
What Happened&lt;/h2&gt;
&lt;p&gt;
The new AI Router proxies to Dedicated inference deployments through mTLS. Some of the mTLS resources were missing for some deployments. Because of this misconfiguration, impacted deployments returned HTTP 502 errors for all inference requests.&lt;/p&gt;
&lt;h2&gt;
What We Learned&lt;/h2&gt;
&lt;p&gt;
We didn’t have a proper way to validate that all deployments had their mTLS configuration set up before the maintenance, and we incorrectly assumed this was true for all of them.&lt;/p&gt;
&lt;h2&gt;
What We’ve Changed&lt;/h2&gt;
&lt;p&gt;
We took an inventory and created the missing resources.&lt;/p&gt;
&lt;h2&gt;
Moving Forward&lt;/h2&gt;
&lt;p&gt;
Future infrastructural rollouts will be performed more gradually, progressing deployment by deployment, staged per zone.&lt;/p&gt;
&lt;p&gt;
Also, we are adding more processes to ensure the invariants that should hold are true before performing this kind of maintenance.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  2, 2026 · 07:34 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We haven’t seen any more HTTP 500 errors since our last communication.  &lt;br /&gt;
The situation is nominal; we are sorry for the inconvenience.  &lt;br /&gt;
A public post-mortem will follow.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  1, 2026 · 18:58 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The situation has been resolved; we will monitor it until tomorrow morning.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  1, 2026 · 18:21 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
All the deployments have been fixed, we are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  1, 2026 · 18:16 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We discovered the issue and have already fixed some deployments.  &lt;br /&gt;
We are continuing to apply the mitigation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  1, 2026 · 18:01 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Customers with dedicated deployments might encounter HTTP 500 errors when making inference requests.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/250360</link>
      <guid>https://exoscalestatus.com/incidents/250360</guid>
    </item>
    <item>
      <title>Concrete AI Dedicated Inference</title>
      <pubDate>Thu, 1 Oct 2026 16:00:00 +0000</pubDate>
      <category domain="event:start">Thu, 1 Oct 2026 15:00:00 +0000</category>
      <category domain="event:end">Thu, 1 Oct 2026 16:00:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-GVA-2, Concrete AI, Dedicated Inference, CH-DK-2, Concrete AI, Dedicated Inference, DE-FRA-1, Concrete AI, Dedicated Inference, DE-MUC-1, Concrete AI, Dedicated Inference, AT-VIE-1, Concrete AI, Dedicated Inference, AT-VIE-2, Concrete AI, Dedicated Inference, BG-SOF-1, Concrete AI, Dedicated Inference, HR-ZAG-1, Concrete AI, Dedicated Inference&lt;/p&gt;&lt;p&gt;&lt;small&gt;October  1, 2026 · 18:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance has been concluded as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  1, 2026 · 17:55 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Some customers with deployments may encounter 500 errors; we are working to restore the service to its normal state.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;October  1, 2026 · 17:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 24, 2026 · 12:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Dedicated Inference request routing will be updated as part of the transition to AI API Keys. During DNS propagation, some inference requests may briefly fail.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/249744</link>
      <guid>https://exoscalestatus.com/incidents/249744</guid>
    </item>
    <item>
      <title>SKS pro clusters etcd Backend Migration</title>
      <pubDate>Wed, 30 Sep 2026 10:25:46 +0000</pubDate>
      <category domain="event:start">Wed, 30 Sep 2026 08:00:00 +0000</category>
      <category domain="event:end">Wed, 30 Sep 2026 10:25:42 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-DK-2, Managed Kubernetes SKS&lt;/p&gt;&lt;p&gt;&lt;small&gt;September 30, 2026 · 12:25 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Maintenance completed&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 30, 2026 · 11:36 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Migration is completed, we are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 30, 2026 · 10:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 23, 2026 · 17:11 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
 Only pro SKS Clusters are targeted during this maintenance.&lt;/p&gt;
&lt;p&gt;
In order to improve performance and reliability of SKS Kubernetes API server operations, we will be migrating SKS clusters to new etcd backends.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Expected Impact&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;
This migration is designed to be fully transparent.  &lt;br /&gt;
No action is required on your side, and you should not notice any disruption.&lt;/p&gt;
&lt;p&gt;
If you have any questions or specific requirements regarding the maintenance window, please contact us through the support channel.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/249686</link>
      <guid>https://exoscalestatus.com/incidents/249686</guid>
    </item>
    <item>
      <title>Network Load Balancer maintenance</title>
      <pubDate>Tue, 29 Sep 2026 12:30:00 +0000</pubDate>
      <category domain="event:start">Tue, 29 Sep 2026 10:30:00 +0000</category>
      <category domain="event:end">Tue, 29 Sep 2026 12:30:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-DK-2, API, Network Load Balancer NLB&lt;/p&gt;&lt;p&gt;&lt;small&gt;September 29, 2026 · 14:30 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance has been concluded as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 29, 2026 · 12:30 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 22, 2026 · 12:16 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We will be conducting scheduled maintenance on our Network Load Balancer (NLB).&lt;/p&gt;
&lt;p&gt;
NLB related API requests are expected to not work both for new and existing entities during the window, though no traffic interruption is expected. This work is being performed to support ongoing improvements to our platform.&lt;/p&gt;
&lt;p&gt;
Thank you for your understanding.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/249553</link>
      <guid>https://exoscalestatus.com/incidents/249553</guid>
    </item>
    <item>
      <title>Network Load Balancer maintenance</title>
      <pubDate>Tue, 29 Sep 2026 10:00:00 +0000</pubDate>
      <category domain="event:start">Tue, 29 Sep 2026 08:00:33 +0000</category>
      <category domain="event:end">Tue, 29 Sep 2026 10:00:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-GVA-2, API, Network Load Balancer NLB&lt;/p&gt;&lt;p&gt;&lt;small&gt;September 29, 2026 · 12:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance has been concluded as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 29, 2026 · 10:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 22, 2026 · 12:15 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We will be conducting scheduled maintenance on our Network Load Balancer (NLB).&lt;/p&gt;
&lt;p&gt;
NLB related API requests are expected to not work both for new and existing entities during the window, though no traffic interruption is expected. This work is being performed to support ongoing improvements to our platform.&lt;/p&gt;
&lt;p&gt;
Thank you for your understanding.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/249552</link>
      <guid>https://exoscalestatus.com/incidents/249552</guid>
    </item>
    <item>
      <title>Network Load Balancer maintenance</title>
      <pubDate>Mon, 28 Sep 2026 12:00:00 +0000</pubDate>
      <category domain="event:start">Mon, 28 Sep 2026 10:00:00 +0000</category>
      <category domain="event:end">Mon, 28 Sep 2026 12:00:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - DE-FRA-1, API, Network Load Balancer NLB&lt;/p&gt;&lt;p&gt;&lt;small&gt;September 28, 2026 · 14:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance has been concluded as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 28, 2026 · 12:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 22, 2026 · 12:15 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We will be conducting scheduled maintenance on our Network Load Balancer (NLB).&lt;/p&gt;
&lt;p&gt;
NLB related API requests are expected to not work both for new and existing entities during the window, though no traffic interruption is expected. This work is being performed to support ongoing improvements to our platform.&lt;/p&gt;
&lt;p&gt;
Thank you for your understanding.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/249551</link>
      <guid>https://exoscalestatus.com/incidents/249551</guid>
    </item>
    <item>
      <title>Network Load Balancer maintenance</title>
      <pubDate>Mon, 28 Sep 2026 09:30:00 +0000</pubDate>
      <category domain="event:start">Mon, 28 Sep 2026 08:00:00 +0000</category>
      <category domain="event:end">Mon, 28 Sep 2026 09:30:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - DE-MUC-1, API, Network Load Balancer NLB&lt;/p&gt;&lt;p&gt;&lt;small&gt;September 28, 2026 · 11:30 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance has been concluded as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 28, 2026 · 10:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 22, 2026 · 12:14 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We will be conducting scheduled maintenance on our Network Load Balancer (NLB).&lt;/p&gt;
&lt;p&gt;
NLB related API requests are expected to not work both for new and existing entities during the window, though no traffic interruption is expected. This work is being performed to support ongoing improvements to our platform.&lt;/p&gt;
&lt;p&gt;
Thank you for your understanding.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/249550</link>
      <guid>https://exoscalestatus.com/incidents/249550</guid>
    </item>
    <item>
      <title>Network Load Balancer maintenance</title>
      <pubDate>Sun, 27 Sep 2026 10:36:54 +0000</pubDate>
      <category domain="event:start">Sun, 27 Sep 2026 10:00:00 +0000</category>
      <category domain="event:end">Sun, 27 Sep 2026 10:36:54 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - AT-VIE-1, API, Network Load Balancer NLB&lt;/p&gt;&lt;p&gt;&lt;small&gt;September 27, 2026 · 12:34 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance has been concluded as planned, with no impact on the API during the time window.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 27, 2026 · 12:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 22, 2026 · 12:10 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We will be conducting scheduled maintenance on our Network Load Balancer (NLB).&lt;/p&gt;
&lt;p&gt;
NLB related API requests are expected to not work both for new and existing entities during the window, though no traffic interruption is expected. This work is being performed to support ongoing improvements to our platform.&lt;/p&gt;
&lt;p&gt;
Thank you for your understanding.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/249549</link>
      <guid>https://exoscalestatus.com/incidents/249549</guid>
    </item>
    <item>
      <title>Network Load Balancer maintenance</title>
      <pubDate>Sun, 27 Sep 2026 09:30:00 +0000</pubDate>
      <category domain="event:start">Sun, 27 Sep 2026 08:00:01 +0000</category>
      <category domain="event:end">Sun, 27 Sep 2026 09:30:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - AT-VIE-2, API, Network Load Balancer NLB&lt;/p&gt;&lt;p&gt;&lt;small&gt;September 27, 2026 · 11:30 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance has been concluded as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 27, 2026 · 10:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 22, 2026 · 12:07 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We will be conducting scheduled maintenance on our Network Load Balancer (NLB).&lt;/p&gt;
&lt;p&gt;
NLB related API requests are expected to not work both for new and existing entities during the window, though no traffic interruption is expected. This work is being performed to support ongoing improvements to our platform.&lt;/p&gt;
&lt;p&gt;
Thank you for your understanding.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/249547</link>
      <guid>https://exoscalestatus.com/incidents/249547</guid>
    </item>
    <item>
      <title>Starter SKS clusters etcd Backend Migration</title>
      <pubDate>Wed, 23 Sep 2026 09:18:07 +0000</pubDate>
      <category domain="event:start">Wed, 23 Sep 2026 08:00:00 +0000</category>
      <category domain="event:end">Wed, 23 Sep 2026 09:18:07 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-DK-2, Managed Kubernetes SKS&lt;/p&gt;&lt;p&gt;&lt;small&gt;September 23, 2026 · 11:17 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Maintenance completed&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 23, 2026 · 10:32 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The maintenance is still ongoing.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 23, 2026 · 10:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 16, 2026 · 18:27 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Only starter SKS Clusters are targeted during this maintenance.&lt;/p&gt;
&lt;p&gt;
In order to improve performance and reliability of SKS Kubernetes API server operations, we will be migrating SKS clusters to new etcd backends.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Expected Impact&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;
This migration is designed to be fully transparent.  &lt;br /&gt;
No action is required on your side, and you should not notice any disruption.&lt;/p&gt;
&lt;p&gt;
If you have any questions or specific requirements regarding the maintenance window, please contact us through the support channel.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/248973</link>
      <guid>https://exoscalestatus.com/incidents/248973</guid>
    </item>
    <item>
      <title>NLB SOF maintenance takes more time than expected.</title>
      <pubDate>Mon, 21 Sep 2026 10:30:53 +0000</pubDate>
      <category domain="event:start">Mon, 21 Sep 2026 10:11:52 +0000</category>
      <category domain="event:end">Mon, 21 Sep 2026 10:30:53 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Partial outage&lt;/strong&gt; - BG-SOF-1, Network Load Balancer NLB&lt;/p&gt;&lt;p&gt;&lt;small&gt;September 21, 2026 · 12:30 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The migration has being completed. No more issues are expected.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 21, 2026 · 12:11 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are experiencing issues with a scheduled NLB maintenance.  &lt;br /&gt;
API is not working, while no traffic drop to existing NLBs is expected.&lt;/p&gt;
&lt;p&gt;
We are working on the fix.  &lt;br /&gt;
Sorry for the inconvenience.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/249448</link>
      <guid>https://exoscalestatus.com/incidents/249448</guid>
    </item>
    <item>
      <title>Network Load Balancer maintenance</title>
      <pubDate>Mon, 21 Sep 2026 09:00:01 +0000</pubDate>
      <category domain="event:start">Mon, 21 Sep 2026 08:00:00 +0000</category>
      <category domain="event:end">Mon, 21 Sep 2026 09:00:01 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - BG-SOF-1, Network Load Balancer NLB&lt;/p&gt;&lt;p&gt;&lt;small&gt;September 21, 2026 · 11:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance has been concluded as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 21, 2026 · 10:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 14, 2026 · 10:46 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We will be conducting scheduled maintenance on our Network Load Balancer (NLB).&lt;/p&gt;
&lt;p&gt;
NLB related API requests are expected to not work both for new and existing entities during the window, though no traffic interruption is expected. This work is being performed to support ongoing improvements to our platform.&lt;/p&gt;
&lt;p&gt;
Thank you for your understanding.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/248693</link>
      <guid>https://exoscalestatus.com/incidents/248693</guid>
    </item>
    <item>
      <title>Compute Managed Elastic IP issues</title>
      <pubDate>Fri, 18 Sep 2026 16:03:04 +0000</pubDate>
      <category domain="event:start">Fri, 18 Sep 2026 15:19:59 +0000</category>
      <category domain="event:end">Fri, 18 Sep 2026 16:03:04 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Partial outage&lt;/strong&gt; - CH-DK-2, Compute, DE-FRA-1, Compute, AT-VIE-1, Compute, BG-SOF-1, Compute&lt;/p&gt;&lt;p&gt;&lt;small&gt;September 18, 2026 · 18:02 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
All the identified hosts have been handled.  &lt;br /&gt;
We are now closing the incident.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 18, 2026 · 17:58 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Mitigation has been applied.  &lt;br /&gt;
We are now monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 18, 2026 · 17:43 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are applying mitigation&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 18, 2026 · 17:33 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The issue is only impacting CH-DK-2, AT-VIE-1, DE-FRA-1 and BG-SOF-1. The number of impacted mEIPs is limited.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 18, 2026 · 17:24 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The root cause has been identified. We are preparing mitigation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 18, 2026 · 17:19 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are investigating a limited number of managed Elastic IPs connectivity issue&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/249140</link>
      <guid>https://exoscalestatus.com/incidents/249140</guid>
    </item>
    <item>
      <title>SKS control plane components migration to new deployment platform</title>
      <pubDate>Thu, 17 Sep 2026 10:47:34 +0000</pubDate>
      <category domain="event:start">Thu, 17 Sep 2026 08:30:00 +0000</category>
      <category domain="event:end">Thu, 17 Sep 2026 10:47:31 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - DE-FRA-1, Managed Kubernetes SKS&lt;/p&gt;&lt;p&gt;&lt;small&gt;September 17, 2026 · 12:47 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Migration carried out successfully&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 17, 2026 · 10:30 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 16, 2026 · 11:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are going to migrate SKS control plane components to a new deployment platform.  &lt;br /&gt;
We estimate that this operation will take approximately 1 and 1/2 hour to achieve.&lt;/p&gt;
&lt;p&gt;
No visible impact is expected from a user perspective.  &lt;br /&gt;
During the maintenance window, both your SKS clusters and the SKS product API will continue to work as expected. The “etcd” backend of your clusters is not in the scope of this migration.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/248899</link>
      <guid>https://exoscalestatus.com/incidents/248899</guid>
    </item>
    <item>
      <title>SKS API operations are unavailable</title>
      <pubDate>Wed, 16 Sep 2026 08:20:07 +0000</pubDate>
      <category domain="event:start">Wed, 16 Sep 2026 07:58:43 +0000</category>
      <category domain="event:end">Wed, 16 Sep 2026 08:20:07 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Partial outage&lt;/strong&gt; - DE-FRA-1, Managed Kubernetes SKS&lt;/p&gt;&lt;p&gt;&lt;small&gt;September 16, 2026 · 10:19 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Incident resolved.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 16, 2026 · 10:13 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The root cause of the issue has been fixed.  &lt;br /&gt;
We are still monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 16, 2026 · 09:58 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Updating clusters or nodepools is not possible at the moment.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/248890</link>
      <guid>https://exoscalestatus.com/incidents/248890</guid>
    </item>
    <item>
      <title>High API error rate</title>
      <pubDate>Thu, 10 Sep 2026 10:08:46 +0000</pubDate>
      <category domain="event:start">Thu, 10 Sep 2026 09:27:59 +0000</category>
      <category domain="event:end">Thu, 10 Sep 2026 10:08:46 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Partial outage&lt;/strong&gt; - CH-GVA-2, API, CH-DK-2, API, DE-FRA-1, API, DE-MUC-1, API, AT-VIE-1, API, AT-VIE-2, API, BG-SOF-1, API, HR-ZAG-1, API&lt;/p&gt;&lt;p&gt;&lt;small&gt;September 10, 2026 · 12:08 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
All systems are operational&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 10, 2026 · 11:50 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Service is back to nominal. We are monitoring the situation&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 10, 2026 · 11:40 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Situation has mostly recovered back to nominal for most API calls&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 10, 2026 · 11:38 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The situation is improving. Less latency or errors are being observed&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 10, 2026 · 11:35 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
All compute related API actions are currently affected. We are currently investigating the cause.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 10, 2026 · 11:30 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Issue escalated to partial outage&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September 10, 2026 · 11:27 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We observe elevated error rate on most API operations.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/248471</link>
      <guid>https://exoscalestatus.com/incidents/248471</guid>
    </item>
    <item>
      <title>SKS control plane components migration to new deployment platform</title>
      <pubDate>Fri, 4 Sep 2026 10:52:16 +0000</pubDate>
      <category domain="event:start">Fri, 4 Sep 2026 08:30:00 +0000</category>
      <category domain="event:end">Fri, 4 Sep 2026 10:52:11 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-GVA-2, Managed Kubernetes SKS&lt;/p&gt;&lt;p&gt;&lt;small&gt;September  4, 2026 · 12:51 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Migration completed&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  4, 2026 · 12:33 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The migration completed as expected.  &lt;br /&gt;
We are still monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  4, 2026 · 10:30 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  2, 2026 · 17:03 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are going to migrate SKS control plane components to a new deployment platform.  &lt;br /&gt;
We estimate that this operation will take approximately 1 and 1/2 hour to achieve.&lt;/p&gt;
&lt;p&gt;
No visible impact is expected from a user perspective.  &lt;br /&gt;
During the maintenance window, both your SKS clusters and the SKS product API will continue to work as expected. The “etcd” backend of your clusters is not in the scope of this migration.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/247721</link>
      <guid>https://exoscalestatus.com/incidents/247721</guid>
    </item>
    <item>
      <title>[API] Increased Error Rates and Latencies </title>
      <pubDate>Thu, 3 Sep 2026 12:34:53 +0000</pubDate>
      <category domain="event:start">Thu, 3 Sep 2026 12:15:28 +0000</category>
      <category domain="event:end">Thu, 3 Sep 2026 12:34:53 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Major outage&lt;/strong&gt; - CH-GVA-2, Compute, CH-DK-2, Compute, DE-FRA-1, Compute, DE-MUC-1, Compute, AT-VIE-1, Compute, AT-VIE-2, Compute, BG-SOF-1, Compute, HR-ZAG-1, Compute&lt;/p&gt;&lt;p&gt;&lt;small&gt;September  3, 2026 · 14:34 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
All systems back to nominal.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  3, 2026 · 14:25 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We have applied a mitigation&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  3, 2026 · 14:15 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are investigating an increased error rates and latencies on the API. We’ll post an update as soon as we have more information.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/247883</link>
      <guid>https://exoscalestatus.com/incidents/247883</guid>
    </item>
    <item>
      <title>Starter SKS clusters etcd Backend Migration</title>
      <pubDate>Mon, 31 Aug 2026 18:22:10 +0000</pubDate>
      <category domain="event:start">Wed, 2 Sep 2026 15:00:00 +0000</category>
      <category domain="event:end">Wed, 2 Sep 2026 17:00:00 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-DK-2, Managed Kubernetes SKS&lt;/p&gt;&lt;p&gt;&lt;small&gt;August 31, 2026 · 20:20 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Canceled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Due to a technical reason, we decided to postpone this migration to a later date.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 27, 2026 · 18:17 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
&lt;strong&gt;UPDATE: only starter clusters will be migrated during this maintenance.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;
In order to improve performance and reliability of SKS Kubernetes API server operations, we will be migrating SKS clusters to new etcd backends.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Expected Impact&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;
This migration is designed to be fully transparent.  &lt;br /&gt;
No action is required on your side, and you should not notice any disruption.&lt;/p&gt;
&lt;p&gt;
If you have any questions or specific requirements regarding the maintenance window, please contact us through the support channel.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/247268</link>
      <guid>https://exoscalestatus.com/incidents/247268</guid>
    </item>
    <item>
      <title>[API] Increased Error Rates and Latencies</title>
      <pubDate>Tue, 1 Sep 2026 13:34:38 +0000</pubDate>
      <category domain="event:start">Tue, 1 Sep 2026 12:36:05 +0000</category>
      <category domain="event:end">Tue, 1 Sep 2026 13:34:38 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Partial outage&lt;/strong&gt; - CH-DK-2, API, Network Load Balancer NLB&lt;/p&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 15:32 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
All systems operational&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 14:55 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Service should be back to nominal. We are monitoring the situation&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 14:54 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Mitigation have been applied, service is recovering. We are monitoring the situation&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 14:53 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Escalate&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Escalating has it’s impacting the NLB service has well.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 14:51 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The issue has been identified, we are applying mitigations&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 14:47 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are still investigating the cause of Increased Error Rates and Latencies&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 14:36 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are investigating an increased error rates and latencies on the API. We’ll post an update as soon as we have more information.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/247542</link>
      <guid>https://exoscalestatus.com/incidents/247542</guid>
    </item>
    <item>
      <title>Portal and API outage</title>
      <pubDate>Fri, 4 Sep 2026 14:21:30 +0000</pubDate>
      <category domain="event:start">Tue, 1 Sep 2026 03:57:48 +0000</category>
      <category domain="event:end">Tue, 1 Sep 2026 10:16:40 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Partial outage&lt;/strong&gt; - CH-GVA-2, API, CH-DK-2, API, DE-FRA-1, API, DE-MUC-1, API, AT-VIE-1, API, AT-VIE-2, API, BG-SOF-1, API, HR-ZAG-1, API&lt;/p&gt;&lt;p&gt;&lt;small&gt;September  4, 2026 · 16:20 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Post-mortem&lt;/strong&gt;&lt;/p&gt;&lt;h1&gt;
Post-mortem&lt;/h1&gt;
&lt;h2&gt;
Summary&lt;/h2&gt;
&lt;p&gt;
On September 1st 2026, we experienced an outage of our control plane, affecting our portal and the APIs of all our services in all zones, caused by an outdated nameserver IP address in our internal resolver configuration. Impact began around 03:20 UTC and all systems were back to nominal at 10:15 UTC.&lt;/p&gt;
&lt;h2&gt;
Impact&lt;/h2&gt;
&lt;p&gt;
Between 03:20 and 10:15 UTC, with the most severe impact between 03:30 and 08:30 UTC, the APIs of all our services were affected in all zones.&lt;/p&gt;
&lt;p&gt;
This was an outage of our control plane, not of the services themselves. Our API and portal returned elevated error rates and timeouts, failing intermittently rather than consistently. Because every service is managed through the API and the portal, creating, listing, modifying and deleting resources could fail or hang for any service, in any zone.&lt;/p&gt;
&lt;p&gt;
Resources already provisioned continued to operate. Compute instances kept running and existing network traffic was not interrupted. No customer data was lost or exposed.&lt;/p&gt;
&lt;h2&gt;
Timeline&lt;/h2&gt;
&lt;p&gt;
All times UTC.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;~03:20&lt;/strong&gt; First errors appear in our internal services.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;03:34&lt;/strong&gt; Our on-call team is engaged.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;03:57&lt;/strong&gt; Errors become visible on the API and portal.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;04:01&lt;/strong&gt; &lt;a target=&quot;_blank&quot; href=&quot;https://exoscalestatus.com/incidents/247488&quot;&gt;Incident opened on the status page.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;04:04&lt;/strong&gt; Impact confirmed across several zones.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;04:04 to 06:24&lt;/strong&gt; Investigation. Symptoms are intermittent and differ between zones and services, and initially point at several unrelated subsystems.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;06:24&lt;/strong&gt; Name resolution identified as the common factor.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;06:52&lt;/strong&gt; Root cause identified.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;06:53&lt;/strong&gt; Status page updated. Incorrect configuration identified, fix being deployed.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;07:00 to 08:18&lt;/strong&gt; Fix deployed and resolver caches flushed across all zones.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;08:05&lt;/strong&gt; API and portal back in service.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;08:29&lt;/strong&gt; Majority of services recovered.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;09:14&lt;/strong&gt; Some services still degraded, monitoring continues.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;10:15&lt;/strong&gt; All systems back to nominal.&lt;/p&gt;
&lt;h2&gt;
What Happened&lt;/h2&gt;
&lt;p&gt;
Our internal DNS zones are replicated to authoritative nameservers hosted outside our own infrastructure. This is a deliberate design choice made to increase resilience. Name resolution is the foundation that every other internal system depends on, so if our zones were served only from within our own platform, any failure large enough to affect that platform would also remove our ability to resolve internal names, and with it much of our ability to diagnose and recover from the failure. Replicating the zones to nameservers operated independently of our infrastructure means internal name resolution continues to work when parts of our platform do not, and keeps a path open for us to recover them.&lt;/p&gt;
&lt;p&gt;
Our resolvers therefore query both our internal nameservers and these external ones. The external nameservers are referenced by IP address in our resolver configuration.&lt;/p&gt;
&lt;p&gt;
One of those external nameserver addresses changed. The change had been announced in advance, but our resolver configuration was not updated everywhere the address appears.&lt;/p&gt;
&lt;p&gt;
That old address had since been reassigned to an unrelated network, and something at it was answering DNS queries. It had no authority over our zones, and rather than refusing the query or returning NXDOMAIN, it replied with an unrelated public IP address for every internal name it was asked about.&lt;/p&gt;
&lt;p&gt;
Had the address been left unrouted, or had it returned an error, our resolvers would have moved on to the other nameservers and the stale entry would have gone unnoticed. The entry had not been updated when the address changed, and the behaviour of the reassigned address is what resulted in an outage.&lt;/p&gt;
&lt;p&gt;
Most queries continued to be answered correctly by our internal nameservers. Only a portion reached the stale address. The result was therefore not a clean failure but an intermittent one. The same lookup could succeed, return a wrong address a moment later, then succeed again. Because a wrong answer is still a valid response, nothing retried it and nothing failed over to another nameserver, and each wrong answer was then cached for the lifetime of the record.&lt;/p&gt;
&lt;p&gt;
As those wrong answers accumulated, internal services connected to the wrong address or waited on hosts that never answered. Orchestrators lost access to their databases, our public API lost access to its backends, and service discovery lost its view of the fleet, each of them partially and unpredictably rather than all at once.&lt;/p&gt;
&lt;p&gt;
This intermittency is the main reason the incident lasted as long as it did. Symptoms differed between zones and between components, services degraded and recovered on their own, and restarting a component often appeared to fix it because its next lookup happened to be answered correctly. The investigation followed those symptoms into the private network layer and then into the databases for three hours before the pattern was recognised as a name resolution problem.&lt;/p&gt;
&lt;p&gt;
Correcting the address was a one line change. Deploying it was another story. Our configuration management and job scheduling systems depend on the same internal DNS and could not reliably distribute the fix, so it was applied manually per zone over out of band access. Correcting the configuration also did not clear the wrong answers already cached. Every local resolver cache across our infrastructure had to be flushed before resolution was reliably correct again.&lt;/p&gt;
&lt;h2&gt;
What We Learned&lt;/h2&gt;
&lt;p&gt;
We had no mechanism to detect that a hard-coded external nameserver address no longer matched the reality. Applying such a change depends on manual follow-up across every place the address appears, with nothing to verify that it had been completed everywhere.&lt;/p&gt;
&lt;p&gt;
Our DNS monitoring verified that names resolved, not that they resolved correctly. A wrong answer produced no alert.&lt;/p&gt;
&lt;p&gt;
A partial, intermittent failure is considerably harder to diagnose than a total one. Because most lookups still succeeded, the symptoms presented as unrelated flapping across several systems rather than as a single common cause.&lt;/p&gt;
&lt;p&gt;
Our remediation path depended on the system that had failed. Most of the time between identifying the cause and restoring service was spent working around that.&lt;/p&gt;
&lt;h2&gt;
What We’ve Changed&lt;/h2&gt;
&lt;p&gt;
Completed&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
We fixed the nameserver addresses in all resolver configurations, in all zones.  &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
In progress&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
We are revisiting our monitoring strategy so that this type of problem is detected quickly, and reviewing our internal dependencies so that our recovery tooling remains usable when name resolution is degraded.  &lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;
Moving Forward&lt;/h2&gt;
&lt;p&gt;
DNS is a shared dependency of everything we run, and we did not treat it with the verification and ownership that implies. That is the focus of the work above. &lt;/p&gt;
&lt;p&gt;
We sincerely apologize for the disruption and thank you for your trust and patience. If you have any questions or concerns, our support team is here to help.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 12:15 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
All systems back to nominal.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 12:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The team is investigating minor remaining problems and putting in place mitigations.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 11:14 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Some services are still flaky. We are still actively monitoring and working on stabilising the system.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 10:29 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The majority of the services have recovered. The team is monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 10:18 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Deployment of config changes is complete and the team is now checking individual services and applying the changes. Services are recovering progressively.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 09:45 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The deployment is continuing and the team is monitoring the situation. Services are recovering progressively.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 09:16 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Changes are being deployed to all affected systems, and the team is monitoring the situation for improvement.&lt;/p&gt;
&lt;p&gt;
Our next update will be at 09h45 CEST.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 08:53 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The team has identified an incorrect configuration and a fix is being deployed. Our next update will be at 09h15 CEST.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 08:27 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The team is still investigating, and some corrective actions have been taken. Our next update will be at 09h00 CEST.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 07:40 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Our team is still looking at the issue.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 06:34 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are still investigating the issue and wil provide an update as soon as possible.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 06:04 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
SKS and Block Storage seems to be impacted too.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;September  1, 2026 · 05:57 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are noticing a high error rate on the API, out team is checking.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/247488</link>
      <guid>https://exoscalestatus.com/incidents/247488</guid>
    </item>
    <item>
      <title>SKS Etcd Backend Migration</title>
      <pubDate>Thu, 27 Aug 2026 16:09:19 +0000</pubDate>
      <category domain="event:start">Thu, 27 Aug 2026 15:00:00 +0000</category>
      <category domain="event:end">Thu, 27 Aug 2026 16:09:19 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - DE-FRA-1, Managed Kubernetes SKS&lt;/p&gt;&lt;p&gt;&lt;small&gt;August 27, 2026 · 18:08 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The migration is done.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 27, 2026 · 17:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 20, 2026 · 17:51 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
In order to improve performance and reliability of SKS Kubernetes API server operations, we will be migrating SKS clusters to new etcd backends.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Expected Impact&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;
This migration is designed to be fully transparent.  &lt;br /&gt;
No action is required on your side, and you should not notice any disruption.&lt;/p&gt;
&lt;p&gt;
If you have any questions or specific requirements regarding the maintenance window, please contact us through the support channel.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/246404</link>
      <guid>https://exoscalestatus.com/incidents/246404</guid>
    </item>
    <item>
      <title>Concrete AI Dedicated Inference</title>
      <pubDate>Wed, 26 Aug 2026 18:24:36 +0000</pubDate>
      <category domain="event:start">Wed, 26 Aug 2026 17:00:32 +0000</category>
      <category domain="event:end">Wed, 26 Aug 2026 18:24:36 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-GVA-2, Concrete AI, Dedicated Inference, CH-DK-2, Concrete AI, Dedicated Inference, DE-FRA-1, Concrete AI, Dedicated Inference, DE-MUC-1, Concrete AI, Dedicated Inference, AT-VIE-1, Concrete AI, Dedicated Inference, AT-VIE-2, Concrete AI, Dedicated Inference, BG-SOF-1, Concrete AI, Dedicated Inference, HR-ZAG-1, Concrete AI, Dedicated Inference&lt;/p&gt;&lt;p&gt;&lt;small&gt;August 26, 2026 · 20:24 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The scheduled maintenance has been performed as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 26, 2026 · 19:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 19, 2026 · 09:29 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Customers using a Dedicated Inference deployment will experience a temporary interruption while the service restarts and becomes available again.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/246188</link>
      <guid>https://exoscalestatus.com/incidents/246188</guid>
    </item>
    <item>
      <title>SKS Etcd Backend Migration</title>
      <pubDate>Wed, 26 Aug 2026 16:51:17 +0000</pubDate>
      <category domain="event:start">Wed, 26 Aug 2026 15:00:00 +0000</category>
      <category domain="event:end">Wed, 26 Aug 2026 16:51:17 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - CH-GVA-2, Managed Kubernetes SKS&lt;/p&gt;&lt;p&gt;&lt;small&gt;August 26, 2026 · 18:50 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The migration is completed with success.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 26, 2026 · 17:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 14, 2026 · 18:15 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Migration as been postponed to 26th of August.&lt;/p&gt;
&lt;p&gt;
In order to improve performance and reliability of SKS Kubernetes API server operations, we will be migrating SKS clusters to new etcd backends.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Expected Impact&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;
This migration is designed to be fully transparent.  &lt;br /&gt;
No action is required on your side, and you should not notice any disruption.&lt;/p&gt;
&lt;p&gt;
If you have any questions or specific requirements regarding the maintenance window, please contact us through the support channel.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/245752</link>
      <guid>https://exoscalestatus.com/incidents/245752</guid>
    </item>
    <item>
      <title>SKS control plane components migration to new deployment platform</title>
      <pubDate>Thu, 27 Aug 2026 09:39:03 +0000</pubDate>
      <category domain="event:start">Wed, 26 Aug 2026 08:30:00 +0000</category>
      <category domain="event:end">Thu, 27 Aug 2026 09:38:59 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - AT-VIE-2, Managed Kubernetes SKS&lt;/p&gt;&lt;p&gt;&lt;small&gt;August 27, 2026 · 11:38 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Migration complete&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 27, 2026 · 11:11 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Workloads migrated, monitoring&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 27, 2026 · 10:53 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Migration ongoing&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 26, 2026 · 11:36 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Postponed&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Postponed to 2026-08-27 8:30 UTC&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 26, 2026 · 10:30 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 24, 2026 · 15:38 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are going to migrate SKS control plane components to a new deployment platform.  &lt;br /&gt;
We estimate that this operation will take approximately 1 and 1/2 hour to achieve.&lt;/p&gt;
&lt;p&gt;
No visible impact is expected from a user perspective.  &lt;br /&gt;
During the maintenance window, both your SKS clusters and the SKS product API will continue to work as expected. The “etcd” backend of your clusters is not in the scope of this migration.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/246687</link>
      <guid>https://exoscalestatus.com/incidents/246687</guid>
    </item>
    <item>
      <title>SKS control plane components migration to new deployment platform</title>
      <pubDate>Mon, 24 Aug 2026 10:42:12 +0000</pubDate>
      <category domain="event:start">Mon, 24 Aug 2026 08:30:00 +0000</category>
      <category domain="event:end">Mon, 24 Aug 2026 10:42:08 +0000</category>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - AT-VIE-1, Managed Kubernetes SKS&lt;/p&gt;&lt;p&gt;&lt;small&gt;August 24, 2026 · 12:41 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Migration successful&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 24, 2026 · 10:30 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 21, 2026 · 09:29 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are going to migrate SKS control plane components to a new deployment platform.  &lt;br /&gt;
We estimate that this operation will take approximately 1 and 1/2 hour to achieve.&lt;/p&gt;
&lt;p&gt;
No visible impact is expected from a user perspective.  &lt;br /&gt;
During the maintenance window, both your SKS clusters and the SKS product API will continue to work as expected. The “etcd” backend of your clusters is not in the scope of this migration.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/246435</link>
      <guid>https://exoscalestatus.com/incidents/246435</guid>
    </item>
    <item>
      <title>SKS control plane components migration to new deployment platform</title>
      <pubDate>Thu, 20 Aug 2026 10:02:07 +0000</pubDate>
      <category domain="event:start">Thu, 20 Aug 2026 08:30:00 +0000</category>
      <category domain="event:end"/>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - AT-VIE-1, Managed Kubernetes SKS&lt;/p&gt;&lt;p&gt;&lt;small&gt;August 20, 2026 · 12:01 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Canceled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Cancelled due to ongoing incident&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 20, 2026 · 10:30 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;August 17, 2026 · 14:26 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are going to migrate SKS control plane components to a new deployment platform.  &lt;br /&gt;
We estimate that this operation will take approximately 1 and 1/2 hour to achieve.&lt;/p&gt;
&lt;p&gt;
No visible impact is expected from a user perspective.  &lt;br /&gt;
During the maintenance window, both your SKS clusters and the SKS product API will continue to work as expected. The “etcd” backend of your clusters is not in the scope of this migration.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/245917</link>
      <guid>https://exoscalestatus.com/incidents/245917</guid>
    </item>
    <item>
      <title>SKS control plane components migration to new deployment platform</title>
      <pubDate>Thu, 2 Jul 2026 10:30:20 +0000</pubDate>
      <category domain="event:start">Thu, 2 Jul 2026 09:00:00 +0000</category>
      <category domain="event:end"/>
      <description>&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - BG-SOF-1, Managed Kubernetes SKS&lt;/p&gt;&lt;p&gt;&lt;small&gt;July  2, 2026 · 12:28 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Canceled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We decided to cancel this migration due to unexpected conditions.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  2, 2026 · 11:32 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The maintenance is still ongoing.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  2, 2026 · 11:30 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance has been concluded as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  2, 2026 · 11:00 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Started&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This maintenance is now starting as planned.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;June 26, 2026 · 17:27 CEST&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are going to migrate SKS control plane components to a new deployment platform.  &lt;br /&gt;
We estimate that this operation will take less than 30 minutes to achieve.&lt;/p&gt;
&lt;p&gt;
No visible impact is expected from a user perspective.  &lt;br /&gt;
During the maintenance window, both your SKS clusters and the SKS product API will continue to work as expected. The “etcd” backend of your clusters is not in the scope of this migration.&lt;/p&gt;
</description>
      <link>https://exoscalestatus.com/incidents/240482</link>
      <guid>https://exoscalestatus.com/incidents/240482</guid>
    </item>
  </channel>
</rss>