Status impact color legend
- Black impact: None
- Yellow impact: Minor
- Red impact: Major
- Blue impact: Maintenance
[Serverless] - serverless gateways down on multiple clusters
Incident
Report for Scaleway
Resolved
This incident has been resolved.
Monitoring
We have now applied the fix to all our Functions and Containers clusters, which addresses the issues caused by the Kapsule incidents earlier today.
We can see the 5xx error rate has now returned to normal, and that the clusters are stable.
We can see the 5xx error rate has now returned to normal, and that the clusters are stable.
Update
Following the incident last night, the gateways to a number of our serverless clusters are not coming back up.
This problem first occurred this morning, and was resolved at around 13:45, but it has since reappeared. We are investigating and trying to mitigate where possible.
This problem first occurred this morning, and was resolved at around 13:45, but it has since reappeared. We are investigating and trying to mitigate where possible.
Update
We are continuing to work on a fix for this issue.
Identified
Following the incident last night, the gateways to a number of our serverless clusters are not coming back up.
This problem first occurred this morning, and was resolved at around 13:45, but it has since reappeared. We are investigating and trying to mitigate where possible.
This problem first occurred this morning, and was resolved at around 13:45, but it has since reappeared. We are investigating and trying to mitigate where possible.
Monitoring
As a result of the incident last night, some gateway pods in our clusters in fr-par were in a crash loop, meaning they would start, run for a couple of minutes, then die. Requests were partially routed to these gateway pods, but would then fail.
The result was that some users could not connect to their functions and containers running on these clusters.
We have found a temporary solution and are working on a long-term fix. The temporary solution should solve the problem, and connectivity should be back to normal, but we are closely monitoring the situation.
The result was that some users could not connect to their functions and containers running on these clusters.
We have found a temporary solution and are working on a long-term fix. The temporary solution should solve the problem, and connectivity should be back to normal, but we are closely monitoring the situation.
Identified
The issue has been identified and a fix is being implemented.
Investigating
Following the incident last night, the gateways to a number of our serverless clusters are not coming back up.
We are investigating.
We are investigating.
This incident affected: Elements - AZ (fr-par-1, fr-par-2, fr-par-3) and Elements - Products (Serverless Functions).