Scaleway Status
Real-time updates of Scaleway issues and outages
Scaleway status is Partially Degraded Service
Scaleway Elements - Products
Scaleway Elements - Products
Cockpit
Domains
Edge service
Instances
Serverless Container
You're checking on Scaleway - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
We are currently investigating this issue.
Recently Resolved Incidents
Customer databases were unavailable between 8.54 am and 9.26 am. Our team had already fix but still monitoring this issue.
Customer may experience 503 errors on edge service.
While putting in production a new IXP, they forgot to update the ACL on their side but we were still able to reach the RS, so we announced our prefixes but the other members of the IXP weren’t able to send traffic to us, leading to blackhole of 20Gbps.
On a small subset of our fr-par infrastructure, between 2026-08-17 09:20 UTC and 2026-08-17 16:15 UTC, some containers attached to a Private Network were not able to reach resources inside that PN. This issue is likely due to a faulty deployment, that we have reverted at 2026-08-17 16:15 UTC.
Containers should now be able to reach resources in their Private Network as before.
If your container has faced issues like "timeouts" or "connection error" while trying to reach a resource through their private endpoint during the time range above, the issues are likely linked. If you still continue to face these errors, feel free to open a support ticket.
We sincerely apologize for any inconvenience.
Customers may have experienced connectivity issues affecting some instances in the PL-WAW-2 region, preventing access via VPC. The issue was caused by a misconfiguration applied to an internal component. A fix was applied, and connectivity has been restored.
403 errors may be returned for several pipelines, due to cache synchronization issue
Since 10:10 AM, our communication with AFNIC registry for TLDs (.fr, .bzh, .alsace, .paris, .wf, .yt, .tf, .pm) is unstable.
Operations on domains from AFNIC may get errors. We are working on identifying the problem.
Scaleway Security team identified that resources behind *.fr-par.scw.cloud may be blacklisted by the security vendor ESET.
Scaleway is in discussion with ESET to remediate the situation as soon as possible.
Scaleway Outage Survival Guide
Scaleway Components
Scaleway Elements - Products
Scaleway Elements - Products
Account
BMaaS
APIs
Apple Silicon
Audit Trail
Scaleway Glacier
Billing
Block Storage
Cockpit
We are currently investigating this issue.
Container Registry
Data Warehouse
Elements - Products
Databases
Developer Tools
Domains
Scaleway Security team identified that resources behind *.fr-par.scw.cloud may be blacklisted by the security vendor ESET.
Scaleway is in discussion with ESET to remediate the situation as soon as possible.
Edge service
Customer may experience 503 errors on edge service.
403 errors may be returned for several pipelines, due to cache synchronization issue
Elastic Metal
Elements Console
Environmental Footprint
File Storage
Generative API
IAM
Instances
Customers may have experienced connectivity issues affecting some instances in the PL-WAW-2 region, preventing access via VPC. The issue was caused by a misconfiguration applied to an internal component. A fix was applied, and connectivity has been restored.
IoT Hub
Jobs
Kafka
Kubernetes Kapsule
Load Balancer
Managed Inference
Messaging and Queuing
Network
Object Storage
Observability
Public Gateway
Secret Manager
Serverless Container
On a small subset of our fr-par infrastructure, between 2026-08-17 09:20 UTC and 2026-08-17 16:15 UTC, some containers attached to a Private Network were not able to reach resources inside that PN. This issue is likely due to a faulty deployment, that we have reverted at 2026-08-17 16:15 UTC.
Containers should now be able to reach resources in their Private Network as before.
If your container has faced issues like "timeouts" or "connection error" while trying to reach a resource through their private endpoint during the time range above, the issues are likely linked. If you still continue to face these errors, feel free to open a support ticket.
We sincerely apologize for any inconvenience.
Serverless Functions
Serverless-Database
Customer databases were unavailable between 8.54 am and 9.26 am. Our team had already fix but still monitoring this issue.
Transactional Email
VPC
Customers may have experienced connectivity issues affecting some instances in the PL-WAW-2 region, preventing access via VPC. The issue was caused by a misconfiguration applied to an internal component. A fix was applied, and connectivity has been restored.
Web Hosting
Website
Clusters for Apache Spark™
Scaleway Elements - AZ
fr-par-1
On a small subset of our fr-par infrastructure, between 2026-08-17 09:20 UTC and 2026-08-17 16:15 UTC, some containers attached to a Private Network were not able to reach resources inside that PN. This issue is likely due to a faulty deployment, that we have reverted at 2026-08-17 16:15 UTC.
Containers should now be able to reach resources in their Private Network as before.
If your container has faced issues like "timeouts" or "connection error" while trying to reach a resource through their private endpoint during the time range above, the issues are likely linked. If you still continue to face these errors, feel free to open a support ticket.
We sincerely apologize for any inconvenience.
fr-par-2
On a small subset of our fr-par infrastructure, between 2026-08-17 09:20 UTC and 2026-08-17 16:15 UTC, some containers attached to a Private Network were not able to reach resources inside that PN. This issue is likely due to a faulty deployment, that we have reverted at 2026-08-17 16:15 UTC.
Containers should now be able to reach resources in their Private Network as before.
If your container has faced issues like "timeouts" or "connection error" while trying to reach a resource through their private endpoint during the time range above, the issues are likely linked. If you still continue to face these errors, feel free to open a support ticket.
We sincerely apologize for any inconvenience.
fr-par-3
On a small subset of our fr-par infrastructure, between 2026-08-17 09:20 UTC and 2026-08-17 16:15 UTC, some containers attached to a Private Network were not able to reach resources inside that PN. This issue is likely due to a faulty deployment, that we have reverted at 2026-08-17 16:15 UTC.
Containers should now be able to reach resources in their Private Network as before.
If your container has faced issues like "timeouts" or "connection error" while trying to reach a resource through their private endpoint during the time range above, the issues are likely linked. If you still continue to face these errors, feel free to open a support ticket.
We sincerely apologize for any inconvenience.
nl-ams-1
nl-ams-2
nl-ams-3
pl-waw-1
pl-waw-2
pl-waw-3
it-mil-1
Scaleway Dedibox - Products
Dedibox
While putting in production a new IXP, they forgot to update the ACL on their side but we were still able to reach the RS, so we announced our prefixes but the other members of the IXP weren’t able to send traffic to us, leading to blackhole of 20Gbps.
Hosting
SAN
Dedirack
Dedibackup
Domains
RPN
Dedibox Console
Dedibox VPS
Scaleway Dedibox - Datacenters
DC1
While putting in production a new IXP, they forgot to update the ACL on their side but we were still able to reach the RS, so we announced our prefixes but the other members of the IXP weren’t able to send traffic to us, leading to blackhole of 20Gbps.
DC2
While putting in production a new IXP, they forgot to update the ACL on their side but we were still able to reach the RS, so we announced our prefixes but the other members of the IXP weren’t able to send traffic to us, leading to blackhole of 20Gbps.
DC3
While putting in production a new IXP, they forgot to update the ACL on their side but we were still able to reach the RS, so we announced our prefixes but the other members of the IXP weren’t able to send traffic to us, leading to blackhole of 20Gbps.
DC4
While putting in production a new IXP, they forgot to update the ACL on their side but we were still able to reach the RS, so we announced our prefixes but the other members of the IXP weren’t able to send traffic to us, leading to blackhole of 20Gbps.
DC5
While putting in production a new IXP, they forgot to update the ACL on their side but we were still able to reach the RS, so we announced our prefixes but the other members of the IXP weren’t able to send traffic to us, leading to blackhole of 20Gbps.
AMS
Scaleway Miscellaneous
Excellence
Product-4-DN
BookMyName
Since 10:10 AM, our communication with AFNIC registry for TLDs (.fr, .bzh, .alsace, .paris, .wf, .yt, .tf, .pm) is unstable.
Operations on domains from AFNIC may get errors. We are working on identifying the problem.