Status impact color legend
- Black impact: None
- Yellow impact: Minor
- Orange impact: Major
- Blue impact: Maintenance
[AMS] - AMS container registry pull/push may fail for some requests
Incident
Report for Scaleway
Resolved
This incident has been resolved.
Update
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.
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.
Update
We are continuing to investigate this issue.
Investigating
We are investigating some slight error rate on AMS registry
This incident affected: Elements - AZ (nl-ams-1) and Elements - Products (Container Registry, Serverless Functions and Containers, Jobs).