[fr-par-1] - Unable to execute actions on Instances
Some actions cannot be applied on Instances on fr-par-1, resulting in resources stucks in a transient state.
- 首次回应
- 约 0 分钟后首次回应
- 处理进展
- 2 条公开更新
- 数据影响
- 未知
- 补偿与善后
- 来源未提及补偿
修复:This incident has been resolved.
供应商数据集
13 个已采集套餐。请用下表筛选;“月均价”用于横向比较,实际下单以“实际付款”列的周期和总价为准。
套餐数据库
显示实际付款周期、总价、开通费与最低期限;月均仅比较周期租金,不含一次性费用。筛选和排序在本地完成。
| 套餐 / 供应商 | 实际付款 | 月均价 | CPU | 内存 | 存储 | 流量 / 端口 | 库存 | 地区 | IPv4 |
|---|---|---|---|---|---|---|---|---|---|
| COMPUTE3-X12C-24G Scaleway · 虚拟机 / VPS · CPU 分配未知 · compute3 | EUR 0.3511 / 1 小时 地区价格:fr-par-1 | 按 730 小时估算月均 EUR 256.303 | 12 vCPU | 24 GB | 228881 MiB 类型未知 · 临时盘 | 未知 4000 Mbps | 未知 | Paris (fr-par-1), fr-par-1 | 未知 |
| COMPUTE3-X16C-32G Scaleway · 虚拟机 / VPS · CPU 分配未知 · compute3 | EUR 0.4682 / 1 小时 地区价格:fr-par-1 | 按 730 小时估算月均 EUR 341.786 | 16 vCPU | 32 GB | 305175 MiB 类型未知 · 临时盘 | 未知 4000 Mbps | 未知 | Paris (fr-par-1), fr-par-1 | 未知 |
| COMPUTE3-X24C-48G Scaleway · 虚拟机 / VPS · CPU 分配未知 · compute3 | EUR 512.3176 / 1 个月 地区价格:fr-par-1 | 月均 EUR 512.3176 | 24 vCPU | 48 GB | 457763 MiB 类型未知 · 临时盘 | 未知 6000 Mbps | 未知 | Paris (fr-par-1), fr-par-1 | 未知 |
| COMPUTE3-X2C-4G Scaleway · 虚拟机 / VPS · CPU 分配未知 · compute3 | EUR 42.705 / 1 个月 地区价格:fr-par-1 | 月均 EUR 42.705 | 2 vCPU | 4 GB | 38146 MiB 类型未知 · 临时盘 | 未知 500 Mbps | 未知 | Paris (fr-par-1), fr-par-1 | 未知 |
| COMPUTE3-X32C-64G Scaleway · 虚拟机 / VPS · CPU 分配未知 · compute3 | EUR 0.9363 / 1 小时 地区价格:fr-par-1 | 按 730 小时估算月均 EUR 683.499 | 32 vCPU | 64 GB | 610351 MiB 类型未知 · 临时盘 | 未知 8000 Mbps | 未知 | Paris (fr-par-1), fr-par-1 | 未知 |
| COMPUTE3-X48C-96G Scaleway · 虚拟机 / VPS · CPU 分配未知 · compute3 | EUR 1,019.81 / 1 个月 地区价格:fr-par-1 | 月均 EUR 1,019.81 | 48 vCPU | 96 GB | 915527 MiB 类型未知 · 临时盘 | 未知 16000 Mbps | 未知 | Paris (fr-par-1), fr-par-1 | 未知 |
| COMPUTE3-X4C-8G Scaleway · 虚拟机 / VPS · CPU 分配未知 · compute3 | EUR 85.41 / 1 个月 地区价格:fr-par-1 | 月均 EUR 85.41 | 4 vCPU | 8 GB | 76293 MiB 类型未知 · 临时盘 | 未知 1000 Mbps | 未知 | Paris (fr-par-1), fr-par-1 | 未知 |
| COMPUTE3-X64C-128G Scaleway · 虚拟机 / VPS · CPU 分配未知 · compute3 | EUR 1.8726 / 1 小时 地区价格:fr-par-1 | 按 730 小时估算月均 EUR 1,366.998 | 64 vCPU | 128 GB | 1220703 MiB 类型未知 · 临时盘 | 未知 16000 Mbps | 未知 | Paris (fr-par-1), fr-par-1 | 未知 |
| COMPUTE3-X6C-12G Scaleway · 虚拟机 / VPS · CPU 分配未知 · compute3 | EUR 128.1588 / 1 个月 地区价格:fr-par-1 | 月均 EUR 128.1588 | 6 vCPU | 12 GB | 114440 MiB 类型未知 · 临时盘 | 未知 1500 Mbps | 未知 | Paris (fr-par-1), fr-par-1 | 未知 |
| COMPUTE3-X8C-16G Scaleway · 虚拟机 / VPS · CPU 分配未知 · compute3 | EUR 0.2341 / 1 小时 地区价格:fr-par-1 | 按 730 小时估算月均 EUR 170.893 | 8 vCPU | 16 GB | 152587 MiB 类型未知 · 临时盘 | 未知 2000 Mbps | 未知 | Paris (fr-par-1), fr-par-1 | 未知 |
| COMPUTE3-X96C-192G Scaleway · 虚拟机 / VPS · CPU 分配未知 · compute3 | EUR 2,039.62 / 1 个月 地区价格:fr-par-1 | 月均 EUR 2,039.62 | 96 vCPU | 192 GB | 1220703 MiB 类型未知 · 临时盘 | 未知 16000 Mbps | 未知 | Paris (fr-par-1), fr-par-1 | 未知 |
| MEMORY3-X12C-96G Scaleway · 虚拟机 / VPS · CPU 分配未知 · memory3 | EUR 0.6798 / 1 小时 地区价格:fr-par-1 | 按 730 小时估算月均 EUR 496.254 | 12 vCPU | 96 GB | 228881 MiB 类型未知 · 临时盘 | 未知 4000 Mbps | 未知 | Paris (fr-par-1), fr-par-1 | 未知 |
| MEMORY3-X16C-128G Scaleway · 虚拟机 / VPS · CPU 分配未知 · memory3 | EUR 0.9064 / 1 小时 地区价格:fr-par-1 | 按 730 小时估算月均 EUR 661.672 | 16 vCPU | 128 GB | 305175 MiB 类型未知 · 临时盘 | 未知 4000 Mbps | 未知 | Paris (fr-par-1), fr-par-1 | 未知 |
没有符合当前条件的套餐。试试放宽筛选。
购买与使用条款
只展示已从官方条款中明确提取的事实。没有出现的字段保持未知,不替供应商补充承诺。
这不表示没有限制或默认允许某种用途。下单前仍需查看供应商最新条款。
事故与善后证据
事故数量、回应速度、修复过程和补偿分开记录;不把一次事故直接换算成供应商总分。
采集范围:覆盖官方接口最近 50 条记录;本批最早记录 2026年6月19日 20:36Some actions cannot be applied on Instances on fr-par-1, resulting in resources stucks in a transient state.
修复:This incident has been resolved.
At 15h55, public switch s45-d14.dc3 has rebooted; public network connectivity was affected for 10 minutes for all servers attached to it.
Some instability and a down of the service, our team is in investigation to resolve the issue
Installations may result in errors, and changing to rescue mode may fail in the NL-AMS-2 region specifically. We are currently investigating the issue.
修复:This incident has been resolved.
Our service TEM has been down since 10:20 CEST It was resolved at 10:52 CEST
修复:This incident has been resolved.
Multiple products unavailable between 11:45 UTC and 12:00 UTC annotation audit trail cockpit containers datalab datawarehouse instance v1 k8s kafka kms mongo registry secrets
修复:This incident has been resolved.
Users might experiment infinite loops in responses in case of multi turn tool_call requests using model gemma-4-26b-a4b-it
修复:This incident has been resolved.
For an unknown reason, half of rack E6 room 103 is down (PAR1- DC2)
修复:This incident has been resolved.
July 28, 2026 — 09:02 CEST: Our monitoring system detected connectivity issues affecting multiple PRO2 hypervisors in FR-PAR-1. Several servers appeared unreachable.
原因:July 28, 2026 — 09:02 CEST: Our monitoring system detected connectivity issues affecting multiple PRO2 hypervisors in FR-PAR-1. Several servers appeared unreachable. July 28, 2026 — 09:14 CEST: The Scaleway Instances team began investigating the issue. July 28, 2026 — 09:14 CEST: Initial findings showed that the affe…
修复:July 28, 2026 — 09:02 CEST: Our monitoring system detected connectivity issues affecting multiple PRO2 hypervisors in FR-PAR-1. Several servers appeared unreachable. July 28, 2026 — 09:14 CEST: The Scaleway Instances team began investigating the issue. July 28, 2026 — 09:14 CEST: Initial findings showed that the affe…
Due to a network equipment failure, Dedibox servers in the following racks at the OPCORE datacenter are affected: - s202A-B7
原因:Due to a network equipment failure, Dedibox servers in the following racks at the OPCORE datacenter are affected: - s202A-B7
修复:The faulty switch has been replaced. Every server should now be reachable.
We are currently investigating an issue with the SSL certificates on imap.bookmyname.com and smtp.bookmyname.com. This issue may prevent some users from sending or receiving emails through these endpoints.
修复:This incident has been resolved.
Since around 1 PM UTC, some internal connections to Scaleway API on it-mil region started to fail. As a result: -Pushes to rg.it-mil.scw.eu are failing with HTTP 500 -Serverless Containers deployments are failing (resources stuck in creating) -etc. (list is not exhaustive)
[14:45] While upgrade our infra some of the clusters were unreachable
During compute instances incident on fr-par (cf. this status: https://status.scaleway.com/incidents/bsp2y5fysy9w), some jobs were interrupted during execution or were not executed at all. They ended in an Interrupted state with a reason technical_error. This happened intermittantly and only form some job runs only between 21/07/2026 22:00:00 CEST and 22/07/2…
Following incident on Compute instances (https://status.scaleway.com/incidents/bsp2y5fysy9w), a few Serverless Containers and namespaces on fr-par region have been stuck in transient statuses (updating/deleting) during the night. Not all resources were impacted, only a fraction on one part of our infrastructure (~1/10). On this part, impacted resources were…
修复:Incident is now resolved. Please read instructions in the previous message if your container or namespace has one of the following error messages. Sorry again for any inconvenience.
Product API is down for Kubernetes clusters
修复:This incident has been resolved.
Following a crash of one node on the block storage cluster at 20h15 UTC, some VMs are stuck. The oncall team is investigating it.
原因:**Incident Overview** On July 21, a block storage cluster incident affected the Instance product on FR-PAR-1 between 20:14 and 03:45 UTC. This incident caused a regional service degradation \(FR-PAR\), resulting in the following impacts: * Kapsule operations were unavailable on a regional level between 21:30 and 01:3…
修复:**Incident Overview** On July 21, a block storage cluster incident affected the Instance product on FR-PAR-1 between 20:14 and 03:45 UTC. This incident caused a regional service degradation \(FR-PAR\), resulting in the following impacts: * Kapsule operations were unavailable on a regional level between 21:30 and 01:3…
Some free domains may currently display a default hosting page or resolve incorrectly due to inconsistencies in domain mappings. Our teams are investigating and working to restore the correct configuration.
原因:Some free domains may currently display a default hosting page or resolve incorrectly due to inconsistencies in domain mappings. Our teams are investigating and working to restore the correct configuration.
修复:This incident has been resolved since 19:15 UTC.
Since around 12:30 PM UTC, several internal connections to the Scaleway API within the it-mil region are failing. As a result: - Pushes to rg.it-mil.scw.eu are failing and returning an "HTTP 500" error. - Serverless Containers deployments are failing (resources stuck in creating) (list is not exhaustive) Our team is actively working on a fix as we speak, we…
原因:Since around 12:30 PM UTC, several internal connections to the Scaleway API within the it-mil region are failing. As a result: - Pushes to rg.it-mil.scw.eu are failing and returning an "HTTP 500" error. - Serverless Containers deployments are failing (resources stuck in creating) (list is not exhaustive) Our team is a…
修复:The incident has been resolved and the situation is stable again since 16:30 UTC. Pushes to registry and containers deployment on the it-mil region are working again. Thank you for your patience on the matter.
A mandatory maintenance operation targeting one of the Block Storage is taking longer than planned. Some clients may experience latencies during write operations on sbs_5k and sbs_15K volumes. We are monitoring it and working to tune this operation to limit impact.
修复:This incident has been resolved.
Following a network issue, the product APIs were unavailable for a few minutes. The issue was immediately resolved by our teams.
修复:This incident has been resolved.
Pool creation throw error 500 when trying to create new pool. Our team is investigating.
修复:The issue has been resolved by our product team. Pools should now be created without any further issues.
11:13 CEST to 11:48 CEST Users may have experienced high error rates or timeouts during this 30-minute window. Our engineering team has identified and resolved the issue.
修复:This incident has been resolved.
A dedibox switch in DC5, room 1, rack A59 has an unstable connection to the upstream router. We need to replace the SFPs. This will result in a brief loss of connectivity for servers connected to this switch.
修复:This incident has been resolved.
Customers may encounter slowdowns in database cold starts, which can take up to 30 seconds.
修复:This incident has been resolved.
Installation/reinstallation and reboot workflows via API or console are not available for Apple Silicon. Currently in use mac are still operationals and reachable.
修复:This incident has been resolved.
Due to NotReady node, we lost all ingestion on it-mil-1 for ~1h Start at 13h20 -> Ended at 14h20
原因:Due to NotReady node, we lost all ingestion on it-mil-1 for ~1h Start at 13h20 -> Ended at 14h20
We are investigating an issue affecting login for some accounts that have multiple organizations linked to them. Accounts with a single organization are not impacted.
修复:This incident has been resolved.
Customers may experience gaps in logs from Scaleway products for the time range 10:30-12:00 CEST
修复:This incident has been resolved.
Customers may experience missing tags when listing tags on Container Registry regional endpoints. Pulling images by tag or digest is not impacted. The Container Registry API is not impacted and returns the correct list of tags.
修复:This incident has been resolved.
Customers may experience a partial outage of public connectivity on servers attached to the public switch Room 4 4-6 rack 1 in DC3.
修复:This incident has been resolved.
Customers may experience degraded performance when ingesting or querying traces in Cockpit in the fr-par region
修复:This incident has been resolved.
Customers may experience longer deployment creation times on Managed Inference in fr-par
修复:This incident has been resolved.
Starting from 07:30 CET, users may experience connectivity issues or failed requests when accessing their Serverless Containers in the nl-ams region. This issue is under investigation by our team.
修复:Update: Connectivity has been partially restored at around 9:30 AM. We are monitoring the situation.
Customers may experience unresponsiveness when using the mistral-medium-3.5-128b model due to an instability on an internal component.
原因:Customers may experience unresponsiveness when using the mistral-medium-3.5-128b model due to an instability on an internal component.
修复:This incident has been resolved.
Maintenance for security system update. A downtime of 10 min can be expected during the maintenance Date/time: July 9th from 16h to 17h
修复:This incident has been resolved.
Customers may experience failures when creating Spark clusters in the fr-par region due to an issue with an internal dependency.
原因:Customers may experience failures when creating Spark clusters in the fr-par region due to an issue with an internal dependency.
修复:This incident has been resolved.
Customers may experience a partial outage on public connectivity for a few minutes due to a reboot of the public switch s301-b5-2 in DC2.
原因:Customers may experience a partial outage on public connectivity for a few minutes due to a reboot of the public switch s301-b5-2 in DC2.
Customers may be unable to connect to their Dedibox VPS in the Paris location due to a locked state.
原因:Customers may be unable to connect to their Dedibox VPS in the Paris location due to a locked state.
修复:This incident has been resolved.
Customers may experience connectivity issues with Object Storage on it-mil-1.
修复:This incident has been resolved.
Today, between 9:12 AM and 10:15 AM (Paris time), customers experienced a high number of HTTP 503 errors on Edge Services pipelines with Object Storage backends due to DNS resolution issues affecting an internal component. This incident has now been resolved, and our teams are continuing to monitor the situation.
原因:Today, between 9:12 AM and 10:15 AM (Paris time), customers experienced a high number of HTTP 503 errors on Edge Services pipelines with Object Storage backends due to DNS resolution issues affecting an internal component. This incident has now been resolved, and our teams are continuing to monitor the situation.
修复:Today, between 9:12 AM and 10:15 AM (Paris time), customers experienced a high number of HTTP 503 errors on Edge Services pipelines with Object Storage backends due to DNS resolution issues affecting an internal component. This incident has now been resolved, and our teams are continuing to monitor the situation.
Customers may be unable to create new deployments due to a lack of available IP addresses on the MSGQ service in the fr-par region.
原因:Customers may be unable to create new deployments due to a lack of available IP addresses on the MSGQ service in the fr-par region.
修复:This incident has been resolved.
[~17h] Customers may experience a high amount of 503 errors on Edge Services pipelines with Object Storage backends due to DNS resolution issues on an internal component.
原因:[~17h] Customers may experience a high amount of 503 errors on Edge Services pipelines with Object Storage backends due to DNS resolution issues on an internal component.
Customers may experience failures when creating SEDB deployments due to a certificate-related error on an internal dependency.
原因:Customers may experience failures when creating SEDB deployments due to a certificate-related error on an internal dependency.
修复:This incident has been resolved.
Customers may experience service unavailability on Object Storage in it-mil-1 due to a routing issue.
原因:Customers may experience service unavailability on Object Storage in it-mil-1 due to a routing issue.
修复:This incident has been resolved.
Instances that were restored through snapshots can produce new snapshots, but cannot restore those snapshots. We are currently investigating this issue.
修复:Newly restored instances will not be affected by this issue. Impacted customers will be contacted individually with updates regarding the corrective maintenance on their snapshots.
Customers may experience transient 5xx errors when using the qwen3.6-35b-a3b model due to instabilities on an internal component.
原因:Customers may experience transient 5xx errors when using the qwen3.6-35b-a3b model due to instabilities on an internal component.
修复:This incident has been resolved.
Customers may experience slowness and errors when pulling/pushing images to the Container Registry in fr-par. Some pulls/pushes may take up to 30 minutes or fail entirely. This may also cause delays or failures in Serverless Containers and Functions deployments.
修复:This incident has been resolved.
Customers may experience transient 5xx errors when using the gemma4-26b-a4b-it model due to instabilities on an internal component. The problem has been identified and we are working on a fix. Retrying the requests after a short delay will succeed.
原因:Customers may experience transient 5xx errors when using the gemma4-26b-a4b-it model due to instabilities on an internal component. The problem has been identified and we are working on a fix. Retrying the requests after a short delay will succeed.
修复:This incident has been resolved.
Customers may experience instabilities when using the mistral-medium-3.5-128b model in the Generative APIs service in the fr-par region.
修复:This incident has been resolved.
社区证据
社区报告可以帮助判断事故范围、客服和善后,但它仍是社区证据。页面显示作者、时间、材料和官方关联,不把帖子标题直接写成平台结论。
这不表示社区没有讨论,也不表示口碑良好或糟糕。
本次来源记录
原始响应会随构建归档;摘要用于确认页面数据来自同一次原始响应。