Past Incidents

Monday 26th June 2023

No incidents reported

Sunday 25th June 2023

No incidents reported

Saturday 24th June 2023

No incidents reported

Friday 23rd June 2023

No incidents reported

Thursday 22nd June 2023

No incidents reported

Wednesday 21st June 2023

[PAR] Planned hypervisor reboot #2, scheduled 1 year ago

An hypervisor on the Paris region needs to be rebooted due to a kernel issue. The reboot will take place tonight (June 21, 2023) at 18:00 UTC. Services on that hypervisor are already migrated apart for a few of them. Impacted customers will shortly receive an email with more details.

EDIT 18:14 UTC: The maintenance is starting

EDIT 22:00 UTC: The maintenance is now over

[PAR] Planned hypervisor reboot, scheduled 1 year ago

An hypervisor on the Paris region needs to be rebooted due to a kernel issue. The reboot will take place tonight (June 21, 2023) at 20:00 UTC. Services on that hypervisor will be migrated starting at 18:00 UTC. Impacted users will shortly receive an email with more details.

EDIT 18:13 UTC: The maintenance is starting

EDIT 23:11 UTC: The maintenance is now over

Tuesday 20th June 2023

Deployments Deployments are experiencing issues

A deployment issue has been identified, we are working on a fix.

EDIT 20:43 UTC - fixed.

Access Logs Metrics/access logs storage layer issue

We are detecting some errors on our storage layer responsible for storing metrics and access logs data. We are investigating.

Edit 04:58 PM UTC: A storage node had a hardware issue, it has been rebooted.

Access Logs Maintenance: Metrics & Access-logs storage layer

We will start a maintenance this Tuesday designed to improve performance on our storage layer for metrics and access-logs. During the maintenance, you may not see latest datapoints and access-logs.

Maintenance will start 20 of June, at 03:30 PM UTC.

Edit 03:45 PM UTC: maintenance is starting.

Edit 04:58 PM UTC: maintenance is over.

Monday 19th June 2023

API MySQL add-ons creation stopped

MySQL add-on API started to timeout while trying to create add-ons. Currently created add-ons still work, though.

We are investigating the issue.

EDIT 09:00 PM UTC: the root cause has been corrected.