UBIKA Service Status

[Resolved] Disruption Detected

Tue, 28 Apr 2026 08:50:00 +0100

Dear Customer, Dear Partner,

There are currently disruptions on the Cloud Protector platform.

All our teams are mobilized to get it back to 100% operational as soon as possible.

This ticket will be updated as the investigation progresses.

The Ubika Support Team

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. (11:10 — Apr 28)

[Resolved] Disruption Detected

Mon, 13 Apr 2026 11:10:00 +0200

Dear Customer, Dear Partner,

The Cloud Protector management console is currently unavailable, and our team is investigating the issue.

No impact is to be expected on traffic.

Console and API are back online at 11h30

This issue is caused by a OVH network incident. You can find more detail here : https://public-cloud.status-ovhcloud.com/incidents/4fqsbwrzpf5m

Impacts of the incident between 10:53 AM and 11:31 AM:

No impact on your asset traffic
Interrupted access to console.ubika.io and APIs
Log ingestion was impacted. Depending on the amount of traffic, logs may have been lost during the incident period.

[Resolved] Disruption Detected

Thu, 26 Mar 2026 11:40:00 +0100

Dear Customer, Dear Partner,

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.

We decided to deactivate Gravelines from production. The service is again fully operational. (11:59 — Mar 26)

The Gravelines cluster is back up and running. We are checking everything before reintroducing it in production. (13:40 — Mar 26)

The Gravelines cluster is back in production and now handling traffic again. (14:15 — Mar 26)

[Resolved] Logs and dashboard disrupted

Tue, 17 Feb 2026 17:47:39 +0200

Dear Customer, Dear Partner, There are currently disruptions on logs and dashboard access. All our teams are mobilized to get it back to 100% operational as soon as possible. This ticket will be updated as the investigation progresses. The Ubika Support Team

Access to logs and dashboards has been fully restored. During the disruption, all logs were ingested; only viewing them was affected.

[Resolved] Maintenance on Dec 15

Mon, 15 Dec 2025 06:00:00 +0100

Dear Customer, Dear Partner,

Maintenance is scheduled for Monday, December 15 at 6:00 a.m. (Europe/Paris time), and should last no longer than 3 hours. No interruptions are planned.

The Ubika Support Team

[Resolved] Disruption Detected

Wed, 10 Dec 2025 12:00:00 +0100

Dear Customer, Dear Partner,

Our filtering cluster hosted in Gravelines faced troubles to deploy new configuration updates. Hence, we decided to isolate it from production.

Please note that the service remains fully operational via our Strasbourg cluster, 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.

A case is ongoing with our hosting provider.

The Ubika Support Team

The Gravelines cluster in back on production. (20:00 — Dec 10)

[Resolved] Maintenance on Dec 8

Mon, 08 Dec 2025 06:00:00 +0000

Description: Software Upgrade
When: Expected Upgrade Start Date and Time: 8 December 2025 from 6:00am CET to 12:00pm CET
Business Impact: No impact on traffic side. This duration defines the Maintenance Window only and does not reflect a downtime duration. Interruption on management console should not last longer than 10 minutes.
Expected action(s) from customer: None.

We will be performing maintenance on the https://console.ubika.io/ website on Monday 8 December.

We apologize for the inconvenience caused by this upgrade. Please do not hesitate to contact our support team if you encounter any problems following this upgrade.

[Resolved] Availability issue AFTER CONFIGURATION UPGRADE

Fri, 07 Nov 2025 12:00:00 +0100

Dear Customer, Dear Partner,

Some asset are facing traffic logs loss on our Gravelines cluster. Cause is under investigation.

This have no impact on filtering efficiency and traffic passing through Cloud Protector.

The Ubika Support Team

We do not reproduce impact, but it seems that there are issues reported by customers that it has impact on traffic.

Gravelines cluster is now out of production to avoid side effects (15:50 — Nov 7)

Our second cluster now exhibits the same behaviour. You may encounter 504 HTTP error in particular if WAF configurations are frequently reloaded.

We enabled back the Gravelines cluster as there is no benefit of keeping it off. Investigations are ongoing with our hoster. (16:40 — Nov 7)

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.

Our hoster is investigating on the managed kubernetes infrastructures that seems to be the cause of the issue. (18:10 — Nov 7)

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. (20:55 — Nov 7)

[Resolved] K8s cluster outage

Fri, 31 Oct 2025 17:30:00 +0100

Dear Customer, Dear Partner,

Our filtering cluster hosted in Strasbourg 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.

A case is ongoing with our hoster. Service remains operational in Gravelines cluster.

The Ubika Support Team

The Strasbourg cluster in back on production. (20:05 — Oct 31)

[Resolved] K8s cluster outage

Mon, 20 Oct 2025 16:00:00 +0200

Dear Customer, Dear Partner,

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.

A case is ongoing with our hoster. Service remains operational in Strasbourg cluster.

The Ubika Support Team

The Gravelines cluster in back on production. (17:40 — Oct 20)

[Resolved] Maintenance on Sep 18

Thu, 18 Sep 2025 08:00:00 +0200

Description: Software Upgrade
When: Expected Upgrade Start Date and Time: 18 September 2025 at 8:00am CET to 10:00am CET
Business Impact: Users that use GeoIp or IpRep in blocking mode may experience a short perturbation. It should last less than 1 minute.
Expected action(s) from customer: None.

We will be performing maintenance on our filtering cluster on Thursday 18 September 2025.

We apologize for the inconvenience caused by this upgrade. Please do not hesitate to contact our support team if you encounter any problems following this upgrade.

Update: Maintenance is over at 09:15am CET - everything went well.

[Resolved] Maintenance on Sep 17 - Postponed

Wed, 17 Sep 2025 08:00:00 +0200

Description: Software Upgrade
When: Expected Upgrade Start Date and Time: 17 September 2025 at 8:00am CET to 10:00am CET
Business Impact: Users that use GeoIp or IpRep in blocking mode may experience a short perturbation. It should last less than 1 minute.
Expected action(s) from customer: None.

We will be performing maintenance on our filtering cluster on Thursday 17 September 2025.

We apologize for the inconvenience caused by this upgrade. Please do not hesitate to contact our support team if you encounter any problems following this upgrade.

UPDATE: Maintenance planned on Sep 17 is postponed

[Resolved] Maintenance on Sep 09

Tue, 09 Sep 2025 08:00:00 +0100

Description: Software Upgrade
When: Expected Upgrade Start Date and Time: 09 September 2025 at 8:00am CET to 10:00am CET
Business Impact: No impact on traffic side. Access to the management console may be disrupted. This duration defines the Maintenance Window only and does not reflect a downtime duration. Interruption on management console should not last longer than 10 minutes.
Expected action(s) from customer: None.

We will be performing maintenance on the https://console.ubika.io/ website on Thursday 09 September 2025.

We apologize for the inconvenience caused by this upgrade. Please do not hesitate to contact our support team if you encounter any problems following this upgrade.

[Resolved] DDoS attack

Sun, 03 Aug 2025 13:20:00 +0200

Dear Customer, Dear Partner,

A DDoS attack is ongoing since Friday, 01/08/2025, starting at 13:20 PM CEST.

The service remains operational. For now, the impact is very low. The disruptions are barely visible to the most sensitive probes. If the attack escalates, you can redirect your DNS to our new CNAME. You can find the CNAME in the asset configuration page.

The Ubika Support Team

Attack ended. (08:20 — Aug 4)

Attack remained under control with no visible impact.

[Resolved] Release causing latency

Tue, 22 Jul 2025 10:30:00 +0100

Dear Customer, Dear Partner,

Following a production release on our filtering clusters this morning, we observed a temporary increase in latency between 10:30 AM and 11:30 AM. The situation was fully resolved by 11:30 AM, and our teams have confirmed that all services are now stable.

This was an isolated and exceptional event.

Thank you for your understanding.

The Ubika Support Team

[Resolved] DDoS attack

Thu, 03 Jul 2025 08:20:00 +0200

Dear Customer, Dear Partner,

A DDoS attack is ongoing since Wednesday, 03/07/2025, starting at 8:20 AM CEST.

The service remains operational. Clients may encounter sporadic packet loss during TLS handshake. Browser usually recover well for such network errors at the cost of a small delay. API clients that do not retry on TCP error and monitoring probes may return errors.

We are currently investigating on a working workaround to this typology of attacks.

The Ubika Support Team

Attack ended. (08:20 — Jul 4)

New information have been collected and provided to OVHCloud to narrow down the root cause of the perturbations. Conclusions will be shared later after further analysis.

[Resolved] Network pertubations

Wed, 02 Jul 2025 14:23:00 +0200

Dear Customer, Dear Partner,

Network pertubations are ongoing on our cloud provider since Wednesday, 02/07/2025, starting at 14:23 CEST.

The service remains operational. Clients may have encountered sporadic 503 http response code. We decided to update our zoning configuration of Strasbourg zone at 15:45 CEST. There is no perturbations anymore.

We closly monitoring the incident and will update the status

The Ubika Support Team

End of network perturbations, there is no new impact to report. Zoning configuration of Strasbourg has been reset to original one.

[Resolved] DDoS attack

Wed, 02 Jul 2025 08:20:00 +0200

Dear Customer, Dear Partner,

A DDoS attack is ongoing since Wednesday, 02/07/2025, starting at 8:20 AM CEST.

We are currently investigating on a working workaround to this typology of attacks.

The Ubika Support Team

Attack has reduced. We do not notice disruptions anymore. (11:30 — Jul 2)

Further tests have been performed and shared with our OVHCloud taskforce to exclude various root causes of the perturbations. Conclusions will be shared later after further analysis.

[Resolved] DDoS attack

Thu, 22 May 2025 08:20:00 +0200

Dear Customer, Dear Partner,

A DDoS attack is ongoing since Thursday, 22/05/2025, starting at 8:20 AM CEST.

The service remains operationnal with minimal impact. We are currently investigating on the attack typology before applying a workaround planned in collaboration with our hoster OVHCloud to completely cut down the attack.

The Ubika Support Team

Analyze is ongoing. The workaround has been applied by OVHCloud. Service should improve for those that are the most impacted (API consumers). (10:21 — May 22)

Attack has ended. (08:20 — May 23)

Network dumps have been captured before and after the workaround was applied by OVHCloud. Analyze will continue in collaboration with OVHCloud to understand the root cause of the sporadic packet loss and retransmission that was observed during the attack and address it.

[Resolved] Disruption Detected

Mon, 12 May 2025 15:38:39 +0200

Investigating - We are investigating a potential issue that might affect the uptime of one our of services. We are sorry for any inconvenience this may cause you. This incident post will be updated once we have more information. This is an automatic post by a monitor bot.

[Resolved] DDoS attack

Wed, 12 Mar 2025 07:15:00 +0100

Dear Customer, Dear Partner,

A DDoS attack is ongoing since Wednesday, 12/03/2025, starting at 7:15 AM CET, targeting one of our customer.

IMPACT:

The service remain operational with a minor impact on the platform’s response time for browser clients.
However, probes and API clients may have issues contacting the service due to packet loss (without aggressive retries like web browser).

Update (11:00 — Mar 12)

Attack is still ongoing, but at very low rate. Impact should be nearly invisible for every workload.
We may have identified the source of the sporadic traffic loss, related to the attack typology. A fix will be deployed soon to address the issue.

Update (07:20 — Mar 13) ··

Attack ended at 7:15 AM CET on 13/03/2025. Traffic capture have been done both by UBIKA and OVH, various mitigations are studied to be more efficient at reducing the impact of those attacks.

The Ubika Support Team

[Resolved] Logs database maintenance

Thu, 27 Feb 2025 08:00:00 +0100

Description: Database Upgrade
When: Expected Upgrade Start Date and Time: 27 February 2025 at 8:00am CET to 14:00am CET
Business Impact: This duration defines the Maintenance Window only. No traffic interruption planned.

A corrective maintenance is planned to improve queries performance on business logs (traffic logs and security events).
No interruption of the filtering service is expected.

No loss of logs is expected during the update. However, the history of business logs will be unavailable for some hours, while they are asynchronously rewritten.

Migration of traffic logs is finished, all history data are available again. Migration of security events is ongoing with an ETA of 30 minutes. (11:05 — Feb 27)

Migration logs history is finished. (11:35 — Feb 27)

[Resolved] Maintenance on Feb 06

Thu, 06 Feb 2025 09:00:00 +0100

Description: Software Upgrade
When: Expected Upgrade Start Date and Time: 06 February 2025 at 9:00am CET to 10:00am CET
Business Impact: No impact on traffic side. Access to the management console may be disrupted. This duration defines the Maintenance Window only and does not reflect a downtime duration. Interruption on management console should not last longer than 10 minutes.
Expected action(s) from customer: None.

We will be performing maintenance on the https://console.ubika.io/ website on Thursday 06 February 2025.

We apologize for the inconvenience caused by this upgrade. Please do not hesitate to contact our support team if you encounter any problems following this upgrade.

[Resolved] Logs dataloss

Thu, 06 Feb 2025 06:52:00 +0100

A routine user operation stuck the logs server in a unreachable state.
Logs ingestion only recover after complete cluster reboot operation.

We apologize for the inconvenience

[Resolved] SYN flood attack

Tue, 04 Feb 2025 07:15:00 +0100

Dear Customer, Dear Partner,

A SYN Flood attack is ongoing since Tuesday, 04/02/2025, starting at 7:15 AM CET, targeting the load balancer upstream of the Cloud Protector infrastructure. The service remain operational with a minor impact on the platform’s response time. However, some probes turned red due to packet loss (without retries).

The Ubika Support Team

Update (08:00 — Feb 5)

The SYN Flood attack ended at 7:15 AM CET on Wednesday 05/02/2025.
Investigations to explain the packet loss are still ongoing with our hoster.

[Resolved] Maintenance on Jan 30

Thu, 30 Jan 2025 05:00:00 +0000

Description: Software Upgrade
When: Expected Upgrade Start Date and Time: 30 January 2025 at 5:00am CET to 6:00am CET
Business Impact: Risk of missing traffic logs during a 10 minutes time frame. Interruption on management console should not last longer than 10 minutes. This duration defines the Maintenance Window only and does not reflect a downtime duration.
Expected action(s) from customer: None.

We will be performing maintenance on the https://console.ubika.io/ website on Thursday 30 January.

We apologize for the inconvenience caused by this upgrade. Please do not hesitate to contact our support team if you encounter any problems following this upgrade.

[Resolved] Maintenance on Jan 14

Tue, 14 Jan 2025 08:30:00 +0000

Description: Software Upgrade
When: Expected Upgrade Start Date and Time: 14 January 2025 at 8:30am CET to 9:00am CET
Business Impact: No impact on traffic side. This duration defines the Maintenance Window only and does not reflect a downtime duration. Interruption on management console should not last longer than 10 minutes.
Expected action(s) from customer: None.

We will be performing maintenance on the https://console.ubika.io/ website on Tuesday 14 January.

We apologize for the inconvenience caused by this upgrade. Please do not hesitate to contact our support team if you encounter any problems following this upgrade.

[Resolved] SYN flood attack

Tue, 31 Dec 2024 07:23:00 +0100

Dear Customer, Dear Partner,

A SYN Flood attack occurred on Tuesday, 12/31/2024, starting at 7:00 AM, targeting the load balancer upstream of the Cloud Protector infrastructure. The service remained operational with a minor impact on the platform’s response time. However, some probes turned red due to packet loss (without retries). The attack was moderate and ended on Wednesday, 01/01/2025, at 7:00 AM.

The Ubika Support Team

[Resolved] Decommissioning of the CP NG intermediate platform (178.33.22.59) by the end of 2024.

Tue, 31 Dec 2024 00:00:00 +0000

As announced several times since the beginning of September, the “intermediate” CP NG platform will be decommissioned by the end of 2024. Please read this carefully.

Affected customers: You are using CP NG, and your asset is NOT showing up as “DNS redirected” in the console. Your DNS is redirected to 178.33.22.59.
Action required: We kindly remind you that you need to update your DNS records.

Information on how to proceed is available in the release note: https://documentation.ubikasec.com/waap-saas-en/2024-version-history.html#infrastructure-resilience-upgrade

[Resolved] Disruption Detected

Tue, 10 Dec 2024 04:41:13 +0100

[Resolved] Disruption Detected

Fri, 29 Nov 2024 18:06:43 +0100

[Resolved] Urgent logs database maintenance

Thu, 14 Nov 2024 08:00:00 +0100

Description: Database Upgrade
When: Expected Upgrade Start Date and Time: 14 November 2024 at 8:00am CET to 11:00am CET
Business Impact: This duration defines the Maintenance Window only. No traffic interruption planned.
Expected action(s) from customer: None.

A performance problem is currently affecting the business log ingestion platform (traffic logs and security events).

Corrective maintenance is scheduled for November 14, 2024 from 8am CET.
No interruption of the filtering service is expected.

No loss of logs is expected during the update. However, the history of business logs will be unavailable for 1 to 3 hours, while they are reimported asynchronously.

Database upgrade is finished. New logs are correctly processed. Reimport of history data will now be processed. (08:33 — Nov 14)

Import of history data is still ongoing without error. (11:10 — Nov 14)

Import is finished, all history data are available again. (12:51 — Nov 14)

[Resolved] Disruption Detected

Wed, 06 Nov 2024 18:03:40 +0100

[Resolved] Disruption Detected

Wed, 06 Nov 2024 12:07:39 +0100

[Resolved] Configuration deployment issues

Mon, 04 Nov 2024 13:51:41 +0100

The deprecated filtering service is facing deployment issues. New configuration deployments will not occur anymore, and traffic may face some instabilities until it’s fixed. (13:51 — Nov 4)

If you urgently need to deploy configuration changes, please redirect your DNS to the new platform as advised in previous communications. Information on how to proceed is available in the release note: https://documentation.ubikasec.com/waap-saas-en/2024-version-history.html#infrastructure-resilience-upgrade
More generally, it’s strongly advised to switch to the new platform in any cases.

Deployment issue is solved. An internal network was saturated, forbidding spawning of new containers. (09:40 — Nov 5)

[Resolved] Let’s Encrypt certificate expiration starting on 4 November

Mon, 04 Nov 2024 00:00:00 +0000

We kindly remind you that you need to update your DNS records to get the resiliency benefits from the last releases. Follow the direction that were provided in the previous communications. You can also get those instructions in the release note. Especially be careful about your firewall rules before updating your DNS records.

Information on how to proceed is available in the release note: https://documentation.ubikasec.com/waap-saas-en/2024-version-history.html#infrastructure-resilience-upgrade

You are especially concerned if your protected assets are not anymore reported as “DNS redirected” in the console.

[Resolved] Disruption Detected

Fri, 01 Nov 2024 21:56:39 +0100

[Resolved] Disruption Detected

Fri, 01 Nov 2024 21:45:42 +0100

[Resolved] Logs service interruption

Thu, 17 Oct 2024 15:53:00 +0000

We detected that the log service is currently not accessible. Dashboards and logs view are currently not available. Filtering service is not affected. (15:53 — Oct 17)
Log service is up again. (16:12 — Oct 17)

A wrong ansible log was run. Logs collection has been interrupted between 15:48 CEST and 16:12 CEST. Logs within this timeframe are lost.

[Resolved] Disruption Detected

Sun, 25 Aug 2024 15:10:40 +0200

[Resolved] Disruption Detected

Sat, 24 Aug 2024 23:51:42 +0200

[Resolved] Disruption Detected

Fri, 23 Aug 2024 22:07:41 +0200

[Resolved] Disruption Detected

Wed, 07 Feb 2024 23:02:41 +0100

[Resolved] Maintenance on Nov 2

Thu, 02 Nov 2023 05:30:00 +0000

Maintenance is scheduled for Thursday, November 2 at 5:30 a.m., and should last no longer than 1 hour.
No interruptions are planned, maintenance should be totally transparent.

Maintenance was longer than expected:

Instead of transparently migrating the compute cluster, we had to reconstruct it asside. Without interruption on running trafic.
Once this reconstruction was finished, traffic was switched to the new compute cluster. Thus, active connections have been interrupted by the load balancer reconfiguration. Thus some end-user clients may have seen disruption and reconnect around 08:20.

[Resolved] Major outage on runtime

Mon, 23 Oct 2023 17:40:00 +0000

Our monitoring reports protected applications down and runtime cluster going red. (17:40 — Oct 23)
Runtime cluster reports 100% CPU without significant network load. Investigation is going on.
Our private cloud reports runtime hosts as dead, runtime cluster is not reacheable any more (18:05 — Oct 23) .
The team decides to hard-reboot the runtime cluster.
Cluster is back and running (18:09 — Oct 23) .
Team will investigate during working hour on why the cluster went 100% CPU without traffic to avoid this situtaition again.

[Resolved] Major outage on runtime

Wed, 27 Sep 2023 09:50:00 +0000

We’re rolling out new docker runners. As instances roll one by one, there should be no service interruption. (08:00 — Sep 27)
First docker runner checked up and running. (09:09 — Sep 27)
Second runner up and running. (09:49 — Sep 27)
Shutting down third runner node. Containers does not balance to the second node as it should be. (09:50 — Sep 27)
Restarting third runner node. Runtime is back normal. (09:55 — Sep 27)
Rolling again second docker runner. Docker runner cluster state is now broken. As an emergency measure, starting to deploy the cluster from scratch to recover as fast as possible. (10:15 — Sep 27)
Cluster is back up and running. (11:08 — Sep 27)

Team is investigating on why the second node did not correctly join the cluster and why the cluster state broke at some point.