» View Event Details | Created
Resolved
The situation has been stable for several hours, we are closing the incident.
Update
The problem has been traced back to our supplier's S3 registry, a workaround has been put in place and deployments are back up and running.
Investigating
Deployments are currently failing on the osc-secnum-fr1 region. Our operators are currently investigating.
» View Event Details | Created
Resolved
We're back to a normal state. Incident is now considered as over, if you are still encountering issues please contact our support.
In Progress
Operations are still in progress. We will keep you updated.
In Progress
Operations are still in progress. We will keep you updated.
In Progress
The fix is actually progressively deployed, it will take some time to be entirely fixed on the osc-fr1 region. We will keep you updated.
In Progress
The root cause has been identified, a fix is currently being implemented.
Investigating
An incident is currently in progress on the osc-fr1 region, making it impossible to create, update or change plans on databases. All types of database are impacted. Our operators are currently investigating the root cause.
» View Event Details | Created
Resolved
We're back to a normal state. Incident is now considered as over, if you are still encountering issues please contact our support.
In Progress
The fix is actually progressively deployed. Some new databases still have issues to boot, we are actually looking to fix it.
In Progress
The root cause has been identified, a fix is currently being implemented.
Investigating
An incident is currently in progress on the osc-fr1 region, making it impossible to create, update or change plans on databases. All types of database are impacted. Our operators are currently investigating the root cause.
» View Event Details | Created
Resolved
The situation has been stable for the past 20 minutes, we consider the incident as closed.
Update
The situation is now back to normal, we are in contact with our infrastructure provider to determine the cause of the incident.
Investigating
Our operators have been alerted about problems reaching some databases and applications nodes. Investigations are in progress.
» View Event Details | Created
Resolved
Maintenance is now considered as completed. Don't hesitate to contact us on support if you notice any problems.
Update
The last public IP address 80.247.13.145 has been processed, we are now performing post-operation checks.
Update
The public IP address 80.247.12.255 has been processed, there are one last public IPs to be addressed.
Update
Public IP address 185.21.194.105 has been processed, 2 remaining public IPs need to be addressed.
Update
The operation was successfully executed on the public IP address 148.253.96.193. There are 3 remaining public IP addresses to be processed.
Update
The first stage of the operation has just been completed. The second part of the operation is now underway, we'll be working on each of our public IP addresses successively, possibly causing some network disruption (packet loss, slower performance).
Update
The maintenance operation has started. We will keep you informed of the progress of the operation on our status page: https://scalingostatus.com/details/3a15043a5c7cf
Scheduled
Planned maintenance will take place on the osc-secnum-fr1 region on March 7, 2024 from 20:00 CET to 22:00 CET. During this maintenance, the network access to the region will be degraded. The aim of this operation is to improve the stability and security of our network architecture.
You can follow the maintenance process and subscribe to updates through our status page: https://scalingostatus.com
Impact:
If you have any question, do not hesitate to reach us through the in-app support.
» View Event Details | Created
Resolved
All databases are back up and running. We performed the post incident checks. The incident is considered as over. If you still have issues please contact our support.
Investigating
One of our database host is mis-behaving. Our team has been alerted and the host is being restarted. Databases using Business plans will automatically failover. The automatic failover procedure may induce a short unavailability (a few seconds). Databases using Starter and Sandbox plans hosted on it will automatically be restarted after the successful restart of the node.
» View Event Details | Created
Resolved
The situation is now back to normal. Incident is now considered over. If you are still encountering an issue, please contact our support.
Update
A fix has been deployed, we are currently recovering from the incident and the databases that were stuck in a creating state are being processed. Our operators are still monitoring the situation
Update
Database creation is now working as expected again. Our operators are working on restoring the other operations and then fixing databases in transient states.
Investigating
Operations related to databases such as creation/plan update or database upgrades are currently not working as expected. Our operators are investigating and a root cause has been identified. We'll keep you updated
» View Event Details | Created
Resolved
The remaining databases have been processed
The incident is now considered as over. If you still face issues, please contact our support.
Update
Databases that were stuck in the creation step are being processed. Our operators are monitoring the situation until it comes back to normal.
Update
The database creation is now behaving as expected. Our operators are working on restoring the databases that are still in a transient state. We will keep you updated.
Investigating
The creation of database addons may fail. Our operators are currently investigating.
» View Event Details | Created
Resolved
Our post-incident checks show that all is good on Platform side. If you still have issues please contact our support.
In Progress
All databases are back up and running. We are performing the post incident checks.
In Progress
Databases are currently being restarted on the host
Investigating
One of our database host is mis-behaving. Our team has been alerted and the host is being restarted. Databases using Business plans will automatically failover. The automatic failover procedure may induce a short unavailability (a few seconds). Databases using Starter and Sandbox plans hosted on it will automatically be restarted after the successful restart of the node.
» View Event Details | Created
Resolved
The remaining databases in a transient state have been handled The incident is considered closed on our side.
If you are still facing issues, please contact Scalingo support.
Update
Our operators are still working on fixing transient status databases.
We will keep you updated
Update
The creation, upgrade and plan update operations are now behaving as expected. Databases that are still in a transient status due to the incident are being processed by our operators. We will keep you updated once they are back to the nominal situation.
Update
The root cause has been identified. This issue is only impacting PostgreSQL databases.
Our operators are currently working on a fix. We will keep you updated about any new information
Investigating
Some databases are stuck in creating, upgrading or plan updating operations. Our operators have been informed and are currently investigating.
We will keep you updated.
» View Event Details | Created
Resolved
Our post-incident checks show that all is good on Platform side. If you still have issues please contact our support.
Update
All databases are back up and running. We are performing the post incident checks.
Update
Databases are currently being restarted on the host
Investigating
One of our database host is mis-behaving. Our team has been alerted and the host is being restarted. Databases using Business plans will automatically failover. The automatic failover procedure may induce a short unavailability (a few seconds). Databases using Starter and Sandbox plans hosted on it will automatically be restarted after the successful restart of the node.
» View Event Details | Created
Resolved
The cause of this incident is linked to Outscale maintenance on their Object Storage: https://status.outscale.com/incidents/ty08cnrzyz1h
The deployments have been working since 45 minutes ago. Scaling operations have been working since 30 minutes ago. All is good on our side, We are closing the incident. If you still have issues please contact our support.
Update
This impact mostly deployments but it also impact scaling operations
In Progress
Deployments are currently failing on the osc-secnum-fr1 region. We have implemented a workaround
» View Event Details | Created
Resolved
Everything is back to normal. We are closing this incident. If you still have issues please contact our support.
Update
We've been seeing an improvement for over around 15 minutes now. We continue to monitor the situation and we are currently restoring components of the platform that is still impacted. On our infrastructure provider side the incident is still on-going: https://status.outscale.com/incidents/zrnzd9g3qk46
Update
The problem has been traced to our infrastructure provider. Their support teams have been alerted. They have reported the incident on their status page: https://status.outscale.com
Investigating
Network disruptions are currently being experienced on the osc-secnum-fr1 region. Our operators have been alerted and investigations have begun.
» View Event Details | Created
Resolved
The situation is back to normal state. If you still have any issue, please contact us via the support.
Update
A fix is being applied. We are monitoring the situation.
Investigating
A network degredation was seen on the osc-secnum-fr1 region. Our operators have been alerted and investigations have begun.
» View Event Details | Created
Resolved
All databases have been restarted and post-incident checks have been applied.
The incident is considered over on our side. If you are still facing issues, please contact our support.
Update
Almost all databases have been restarted.
Our operators are still working on restoring the last ones.
Update
Databases are currently being restarted on the host.
Investigating
One of our database host is mis-behaving. Our team has been alerted and the host is being restarted. Databases using Business plans will automatically failover. The automatic failover procedure may induce a short unavailability (a few seconds). Databases using Starter and Sandbox plans hosted on it will automatically be restarted after the successful restart of the node.
