<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><link rel="alternate" type="text/html" href="https://status.preprod.ubika.io/"/><title>Runtime (Gra11) on PREPRODUCTION — UBIKA Service Status</title><link>https://status.preprod.ubika.io/affected/runtime-gra11/</link><description>Incident history</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2026-09-21T10:00:00+02:00</lastBuildDate><updated>2026-09-21T10:00:00+02:00</updated><atom:link href="https://status.preprod.ubika.io/affected/runtime-gra11/index.xml" rel="self" type="application/rss+xml"/><item><title>[TEST] RSS notification test</title><link>https://status.preprod.ubika.io/issues/2026-09-21-test-rss/</link><pubDate>Mon, 21 Sep 2026 10:00:00 +0200</pubDate><guid>https://status.preprod.ubika.io/issues/2026-09-21-test-rss/</guid><category/><description>&lt;p&gt;&lt;strong&gt;This is a test entry, no real incident is ongoing.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This post is published to validate the status page notification chain (RSS feed → Power Automate → e-mail). It carries a severity, two affected components and an unresolved status so that every &lt;code&gt;&amp;lt;category&amp;gt;&lt;/code&gt; field of the feed item can be checked by the consumer.&lt;/p&gt;
&lt;p&gt;No action is required from customers or partners. This entry will be marked as resolved and removed once the test is complete.&lt;/p&gt;</description><content type="html">&lt;p&gt;&lt;strong&gt;This is a test entry, no real incident is ongoing.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This post is published to validate the status page notification chain (RSS feed → Power Automate → e-mail). It carries a severity, two affected components and an unresolved status so that every &lt;code&gt;&amp;lt;category&amp;gt;&lt;/code&gt; field of the feed item can be checked by the consumer.&lt;/p&gt;
&lt;p&gt;No action is required from customers or partners. This entry will be marked as resolved and removed once the test is complete.&lt;/p&gt;
&lt;p&gt;The Ubika Support Team&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Test update entry, used to check that feed consumers pick up an updated item.
&lt;span class="faded"&gt;(10:30 — Sep 21)&lt;/span&gt;
&lt;/p&gt;</content></item><item><title>[Resolved] Disruption Detected</title><link>https://status.preprod.ubika.io/issues/2026-05-21-incident_ddos/</link><pubDate>Thu, 21 May 2026 09:45:00 +0100</pubDate><guid>https://status.preprod.ubika.io/issues/2026-05-21-incident_ddos/</guid><category>2026-05-21T09:47:00+01:00</category><description>&lt;p&gt;Dear Customer, Dear Partner,&lt;/p&gt;
&lt;p&gt;We experienced a high load DDoS attack from 09:45 a.m. to 09:47 a.m.&lt;/p&gt;
&lt;p&gt;Traffic was impacted, resulting in slowdowns.
The console was not impacted.&lt;/p&gt;
&lt;p&gt;We have identified the bottleneck and are working to address it.&lt;/p&gt;
&lt;p&gt;The Ubika Support Team&lt;/p&gt;</description><content type="html">&lt;p&gt;Dear Customer, Dear Partner,&lt;/p&gt;
&lt;p&gt;We experienced a high load DDoS attack from 09:45 a.m. to 09:47 a.m.&lt;/p&gt;
&lt;p&gt;Traffic was impacted, resulting in slowdowns.
The console was not impacted.&lt;/p&gt;
&lt;p&gt;We have identified the bottleneck and are working to address it.&lt;/p&gt;
&lt;p&gt;The Ubika Support Team&lt;/p&gt;</content></item><item><title>[Resolved] Disruption Detected</title><link>https://status.preprod.ubika.io/issues/2026-05-20-incident_ddos/</link><pubDate>Wed, 20 May 2026 19:30:00 +0100</pubDate><guid>https://status.preprod.ubika.io/issues/2026-05-20-incident_ddos/</guid><category>2026-05-20T19:40:00+01:00</category><description>&lt;p&gt;Dear Customer, Dear Partner,&lt;/p&gt;
&lt;p&gt;We experienced a high load DDoS attack from 19:30 p.m. to 19:40 a.m.&lt;/p&gt;
&lt;p&gt;Traffic was impacted, resulting in slowdowns.
The console was not impacted.&lt;/p&gt;
&lt;p&gt;We have identified the bottleneck and are working to address it.&lt;/p&gt;
&lt;p&gt;The Ubika Support Team&lt;/p&gt;</description><content type="html">&lt;p&gt;Dear Customer, Dear Partner,&lt;/p&gt;
&lt;p&gt;We experienced a high load DDoS attack from 19:30 p.m. to 19:40 a.m.&lt;/p&gt;
&lt;p&gt;Traffic was impacted, resulting in slowdowns.
The console was not impacted.&lt;/p&gt;
&lt;p&gt;We have identified the bottleneck and are working to address it.&lt;/p&gt;
&lt;p&gt;The Ubika Support Team&lt;/p&gt;</content></item><item><title>[Resolved] Disruption Detected</title><link>https://status.preprod.ubika.io/issues/2026-04-28-incident_ddos/</link><pubDate>Tue, 28 Apr 2026 08:50:00 +0100</pubDate><guid>https://status.preprod.ubika.io/issues/2026-04-28-incident_ddos/</guid><category>2026-04-28T11:10:00+01:00</category><description>&lt;p&gt;Dear Customer, Dear Partner,&lt;/p&gt;
&lt;p&gt;There are currently disruptions on the Cloud Protector platform.&lt;/p&gt;
&lt;p&gt;All our teams are mobilized to get it back to 100% operational as soon as possible.&lt;/p&gt;
&lt;p&gt;This ticket will be updated as the investigation progresses.&lt;/p&gt;
&lt;p&gt;The Ubika Support Team&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;We experienced a DDoS attack from 8:50 a.m. to 11:10 a.m. The Cloud Protector platform is now fully operational again.
Traffic was impacted, resulting in slowdowns, and some application logs were also lost.
The console was not impacted.
Actions have been taken to improve the anti-DDoS system as well as the scalability of the filtering environment.
&lt;span class="faded"&gt;(11:10 — Apr 28)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;p&gt;Dear Customer, Dear Partner,&lt;/p&gt;
&lt;p&gt;There are currently disruptions on the Cloud Protector platform.&lt;/p&gt;
&lt;p&gt;All our teams are mobilized to get it back to 100% operational as soon as possible.&lt;/p&gt;
&lt;p&gt;This ticket will be updated as the investigation progresses.&lt;/p&gt;
&lt;p&gt;The Ubika Support Team&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;We experienced a DDoS attack from 8:50 a.m. to 11:10 a.m. The Cloud Protector platform is now fully operational again.
Traffic was impacted, resulting in slowdowns, and some application logs were also lost.
The console was not impacted.
Actions have been taken to improve the anti-DDoS system as well as the scalability of the filtering environment.
&lt;span class="faded"&gt;(11:10 — Apr 28)&lt;/span&gt;
&lt;/p&gt;</content></item><item><title>[Resolved] Disruption Detected</title><link>https://status.preprod.ubika.io/issues/2026-03-26-incident/</link><pubDate>Thu, 26 Mar 2026 11:40:00 +0100</pubDate><guid>https://status.preprod.ubika.io/issues/2026-03-26-incident/</guid><category>2026-03-26T14:15:00+01:00</category><description>&lt;p&gt;Dear Customer, Dear Partner,&lt;/p&gt;
&lt;p&gt;Our filtering cluster hosted in Gravelines is facing an OVH incident impacting all of our gateways. The service remains fully operational via our Strasbourg cluster, but since 50% of the traffic is still routed towards the impacted cluster, half of the requests get a 503 HTTP error.&lt;/p&gt;
&lt;p&gt;We decided to deactivate Gravelines from production. The &lt;strong&gt;service is again fully operational&lt;/strong&gt;.
&lt;span class="faded"&gt;(11:59 — Mar 26)&lt;/span&gt;
&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;The Gravelines cluster is back up and running. We are checking everything before reintroducing it in production.
&lt;span class="faded"&gt;(13:40 — Mar 26)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;p&gt;Dear Customer, Dear Partner,&lt;/p&gt;
&lt;p&gt;Our filtering cluster hosted in Gravelines is facing an OVH incident impacting all of our gateways. The service remains fully operational via our Strasbourg cluster, but since 50% of the traffic is still routed towards the impacted cluster, half of the requests get a 503 HTTP error.&lt;/p&gt;
&lt;p&gt;We decided to deactivate Gravelines from production. The &lt;strong&gt;service is again fully operational&lt;/strong&gt;.
&lt;span class="faded"&gt;(11:59 — Mar 26)&lt;/span&gt;
&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;The Gravelines cluster is back up and running. We are checking everything before reintroducing it in production.
&lt;span class="faded"&gt;(13:40 — Mar 26)&lt;/span&gt;
&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;The Gravelines cluster is back in production and now handling traffic again.
&lt;span class="faded"&gt;(14:15 — Mar 26)&lt;/span&gt;
&lt;/p&gt;</content></item><item><title>[Resolved] Disruption Detected</title><link>https://status.preprod.ubika.io/issues/2025-12-10-incident/</link><pubDate>Wed, 10 Dec 2025 12:00:00 +0100</pubDate><guid>https://status.preprod.ubika.io/issues/2025-12-10-incident/</guid><category>2025-12-10T20:00:00+01:00</category><description>&lt;p&gt;Dear Customer, Dear Partner,&lt;/p&gt;
&lt;p&gt;Our filtering cluster hosted in Gravelines faced troubles to deploy new configuration updates. Hence, we decided to isolate it from production.&lt;/p&gt;
&lt;p&gt;Please note that &lt;strong&gt;the service remains fully operational via our Strasbourg cluster&lt;/strong&gt;, ensuring continued protection and availability. In case of configuration modification, the deployment status in the console will remain in “pending” state (orange). This is a consequence of Gravelines isolation and has no impact on the service availibility.&lt;/p&gt;</description><content type="html">&lt;p&gt;Dear Customer, Dear Partner,&lt;/p&gt;
&lt;p&gt;Our filtering cluster hosted in Gravelines faced troubles to deploy new configuration updates. Hence, we decided to isolate it from production.&lt;/p&gt;
&lt;p&gt;Please note that &lt;strong&gt;the service remains fully operational via our Strasbourg cluster&lt;/strong&gt;, ensuring continued protection and availability. In case of configuration modification, the deployment status in the console will remain in “pending” state (orange). This is a consequence of Gravelines isolation and has no impact on the service availibility.&lt;/p&gt;
&lt;p&gt;A case is ongoing with our hosting provider.&lt;/p&gt;
&lt;h2 id="the-ubika-support-team"&gt;The Ubika Support Team&lt;/h2&gt;
&lt;p&gt;The Gravelines cluster in back on production.
&lt;span class="faded"&gt;(20:00 — Dec 10)&lt;/span&gt;
&lt;/p&gt;</content></item><item><title>[Resolved] Availability issue AFTER CONFIGURATION UPGRADE</title><link>https://status.preprod.ubika.io/issues/2025-11-07/</link><pubDate>Fri, 07 Nov 2025 12:00:00 +0100</pubDate><guid>https://status.preprod.ubika.io/issues/2025-11-07/</guid><category>2025-11-07T20:55:00+01:00</category><description>&lt;p&gt;Dear Customer, Dear Partner,&lt;/p&gt;
&lt;p&gt;Some asset are facing traffic logs loss on our Gravelines cluster. Cause is under investigation.&lt;/p&gt;
&lt;p&gt;This have no impact on filtering efficiency and traffic passing through Cloud Protector.&lt;/p&gt;
&lt;p&gt;The Ubika Support Team&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;We do not reproduce impact, but it seems that there are issues reported by customers that it has impact on traffic.&lt;/p&gt;
&lt;p&gt;Gravelines cluster is now out of production to avoid side effects
&lt;span class="faded"&gt;(15:50 — Nov 7)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;p&gt;Dear Customer, Dear Partner,&lt;/p&gt;
&lt;p&gt;Some asset are facing traffic logs loss on our Gravelines cluster. Cause is under investigation.&lt;/p&gt;
&lt;p&gt;This have no impact on filtering efficiency and traffic passing through Cloud Protector.&lt;/p&gt;
&lt;p&gt;The Ubika Support Team&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;We do not reproduce impact, but it seems that there are issues reported by customers that it has impact on traffic.&lt;/p&gt;
&lt;p&gt;Gravelines cluster is now out of production to avoid side effects
&lt;span class="faded"&gt;(15:50 — Nov 7)&lt;/span&gt;
&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Our second cluster now exhibits the same behaviour. You may encounter 504 HTTP error in particular if WAF configurations are frequently reloaded.&lt;/p&gt;
&lt;p&gt;We enabled back the Gravelines cluster as there is no benefit of keeping it off. Investigations are ongoing with our hoster.
&lt;span class="faded"&gt;(16:40 — Nov 7)&lt;/span&gt;
&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;If possible, avoid to update configurations of assets to avoid assets issues. We are on the process of applying a workaround that mitigate the issue.&lt;/p&gt;
&lt;p&gt;Our hoster is investigating on the managed kubernetes infrastructures that seems to be the cause of the issue.
&lt;span class="faded"&gt;(18:10 — Nov 7)&lt;/span&gt;
&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Root cause has been identified. A workaround has been deployed and situation should go back to normal. A proper fix will be deployed on 12/11/2025.
&lt;span class="faded"&gt;(20:55 — Nov 7)&lt;/span&gt;
&lt;/p&gt;</content></item><item><title>[Resolved] K8s cluster outage</title><link>https://status.preprod.ubika.io/issues/2025-10-20-1/</link><pubDate>Mon, 20 Oct 2025 16:00:00 +0200</pubDate><guid>https://status.preprod.ubika.io/issues/2025-10-20-1/</guid><category>2025-10-20T17:40:00+02:00</category><description>&lt;p&gt;Dear Customer, Dear Partner,&lt;/p&gt;
&lt;p&gt;Our filtering cluster hosted in Gravelines is currently having Control Plane issue and does not deploy anymore configuration updates. We decided to remove it from our load balancing to avoid outdated configurations running.&lt;/p&gt;
&lt;p&gt;A case is ongoing with our hoster. Service remains operational in Strasbourg cluster.&lt;/p&gt;
&lt;p&gt;The Ubika Support Team&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;The Gravelines cluster in back on production.
&lt;span class="faded"&gt;(17:40 — Oct 20)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;p&gt;Dear Customer, Dear Partner,&lt;/p&gt;
&lt;p&gt;Our filtering cluster hosted in Gravelines is currently having Control Plane issue and does not deploy anymore configuration updates. We decided to remove it from our load balancing to avoid outdated configurations running.&lt;/p&gt;
&lt;p&gt;A case is ongoing with our hoster. Service remains operational in Strasbourg cluster.&lt;/p&gt;
&lt;p&gt;The Ubika Support Team&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;The Gravelines cluster in back on production.
&lt;span class="faded"&gt;(17:40 — Oct 20)&lt;/span&gt;
&lt;/p&gt;</content></item></channel></rss>