Scaleway Status

Investigating: Serverless functions on nl-ams region are affected by this incident, as they are using registry from this region.

Despite retries done internally to push the images built from the clients codes, a few number of users might nonetheless see their function ending up in error, with the following message: "error on function build step : cannot push to scaleway container registry, retry later or contact support".

If that is the case, retrying later (5 min) should be enough to mitigate the issue, as registry errors are unlikely to happen multiple times in a row during 5 minutes timeframe.

If the issue continues after, please contact the support.

Investigating: We are continuing to investigate this issue.

Investigating: We are investigating some slight error rate on AMS registry

Investigating: Serverless functions on nl-ams region are affected by this incident, as they are using registry from this region.

Despite retries done internally to push the images built from the clients codes, a few number of users might nonetheless see their function ending up in error, with the following message: "error on function build step : cannot push to scaleway container registry, retry later or contact support".

If that is the case, retrying later (5 min) should be enough to mitigate the issue, as registry errors are unlikely to happen multiple times in a row during 5 minutes timeframe.

If the issue continues after, please contact the support.

Investigating: We are continuing to investigate this issue.

Investigating: We are investigating some slight error rate on AMS registry

Investigating: We've identified an incident that resulted in underbilling for Serverless Functions Consumption starting from May.

We apologize for any inconvenience this may have caused.

Current Situation:

We will be issuing accurate invoices for Serverless Functions Consumption usage starting from September, reflecting the correct usage and charges.

No surprises: we won't charge you for the underbilled months (May to August) to ensure your billing remains accurate and transparent.

Serverless Containers continue to be billed accurately, with no issues or disruptions.

Additional Resources:

For detailed information about Serverless Functions billing, please visit our documentation:

https://www.scaleway.com/en/docs/faq/serverless-functions/#how-am-i-billed-for-serverless-functions

Thank you for your understanding, and please don't hesitate to reach out with any questions or concerns.

Investigating: Serverless functions on nl-ams region are affected by this incident, as they are using registry from this region.

Despite retries done internally to push the images built from the clients codes, a few number of users might nonetheless see their function ending up in error, with the following message: "error on function build step : cannot push to scaleway container registry, retry later or contact support".

If that is the case, retrying later (5 min) should be enough to mitigate the issue, as registry errors are unlikely to happen multiple times in a row during 5 minutes timeframe.

If the issue continues after, please contact the support.

Investigating: We are continuing to investigate this issue.

Investigating: We are investigating some slight error rate on AMS registry

Identified: san-dc2-32.rpn.online.net is slowed down during a maintenance operation. Clients on this SAN can notice unusual slowness. We are closely monitoring it.

Resolved: This incident has been resolved.

Investigating: During the reboot of a switch, data replication didn't work correctly on the following machines and writes that occurred during the incident were not taken into account. The filesystem client side should still be consistent with the server state.

Server impacted were : rpn-san-hdd-17 rpn-san-hdd-18 rpn-san-hdd-19 rpn-san-hdd-20 rpn-san-hdd-21 rpn-san-hdd-22 rpn-san-hdd-23 rpn-san-hdd-24 rpn-san-hdd-25 rpn-san-hdd-26 rpn-san-hdd-27 rpn-san-hdd-28 rpn-san-hdd-29 rpn-san-hdd-30 rpn-san-hdd-31

Investigating: RPN-SAN dc3 lost network connectivity at 08:04 UTC, team is investigating

Resolved: RPN access was unrachable between 2024 Sep 16 22:26:03 UTC and 2024 Sep 16 22:30:26 UTC in s203b rack J13 DC2

Investigating: Serverless functions on nl-ams region are affected by this incident, as they are using registry from this region.

Despite retries done internally to push the images built from the clients codes, a few number of users might nonetheless see their function ending up in error, with the following message: "error on function build step : cannot push to scaleway container registry, retry later or contact support".

If that is the case, retrying later (5 min) should be enough to mitigate the issue, as registry errors are unlikely to happen multiple times in a row during 5 minutes timeframe.

If the issue continues after, please contact the support.

Investigating: We are continuing to investigate this issue.

Investigating: We are investigating some slight error rate on AMS registry

Resolved: This incident has been resolved.

Investigating: Console is now working, as well as project deletion.

Investigating: Flexible IPs, Elastic Metal APIs down in pl-waw-3. Console is unavailable for Elastic Metal worldwide and for VPCs. Abuses cannot be opened anymore, Projects cannot be deleted, and Private Networks cannot be deleted in pl-waw-3. Existing servers, private networks, and IPs are unaffected.

Resolved: This incident has been resolved.

Monitoring: RPN service on servers connected to DC3/S43/C5 down between 08:05 to 08:11 CEST.

Resolved: This incident has been resolved.

Investigating: PUB switch service is offline for dedibox located on DC3 room 4-5 rack F12 since 0:48 CEST.

Resolved: This incident has been resolved.

Investigating: During the reboot of a switch, data replication didn't work correctly on the following machines and writes that occurred during the incident were not taken into account. The filesystem client side should still be consistent with the server state.

Server impacted were : rpn-san-hdd-17 rpn-san-hdd-18 rpn-san-hdd-19 rpn-san-hdd-20 rpn-san-hdd-21 rpn-san-hdd-22 rpn-san-hdd-23 rpn-san-hdd-24 rpn-san-hdd-25 rpn-san-hdd-26 rpn-san-hdd-27 rpn-san-hdd-28 rpn-san-hdd-29 rpn-san-hdd-30 rpn-san-hdd-31

Investigating: RPN-SAN dc3 lost network connectivity at 08:04 UTC, team is investigating

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: Public access for rack A3 is back to normal We are still working on rack A2

Identified: The hardware has been replaced, configuration of the device ongoing.

Identified: We detected an hardware failure, the replacement is ongoing

Investigating: Servers in that rack currently have no network access and are unreachable.

Resolved: This incident has been resolved.

Investigating: Power issue in 103/C8/PARDC2 start: Sep 17 10:48:30 UTC end: Sep 17 11:10 UTC

The servers concerned have restarted : mac mini M2-M servers 62.210.195.2 -> 62.210.195.97

Resolved: This incident has been resolved.

Investigating: The switch s1-b4.dc5 located in DC5 room1 rack B4 rebooted unexpectedly. start: 2024 Sep 17 00:41 UTC end: 2024 Sep 17 00:44 UTC

Resolved: This incident has been resolved.

Investigating: The network device rebooted unexpectedly start: 2024 Sep 17 21:12 UTC end: 2024 Sep 17 21:13 UTC