Degraded / minor incident Scaleway status
scaleway.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
Scaleway's status page shows “Degraded / minor incident” in nl-ams-1 and nl-ams-2; the vendor is resolved. User reports haven't spiked, so wide impact isn't visible yet.
confidence: low Vendor: minor issue · users: normal · routing: no data.
- Vendor status page Degraded / minor incident · 6 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP AS12876: routing data not loaded on this view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: nl-ams-1, nl-ams-2, nl-ams-3
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 30 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | 15 h 21 min |
Evidence
- Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
- Vendor stage: resolved on “[Serverless Functions/Containers] - [nl-ams] - Connectivity issues”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside Scaleway's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: no data. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).
Who depends on whom
We don't map other services that depend on Scaleway. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Scaleway, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Scaleway. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
[Serverless Functions/Containers] - [nl-ams] - Connectivity issues
minor resolved · started · resolved
6 updates
- identified
The scheduled maintenance https://status.scaleway.com/incidents/f7lpf0j1c2sq did not go as planned. Since 09:50 UTC, Serverless Containers services might have faced connectivity issues. Create and update operations were impacted as well.
- identified
Serverless Container, Serverless Functions are impacted.
- identified
Connectivity has been back to normal since 11:06 UTC. We are continuing to monitor the situation. We are still working on restoring create and update operations, which remain impacted.
- identified
As of 12:00 UTC, containers shouldn't be stuck anymore in "creating" or "updating" status for an abnormal duration. Some containers with VPC support might have lost connectivity to resources inside the Private Network. A redeployment of the container triggered by users could help solving the situation, but we are investigating. Sorry again for any inconvenience.
- monitoring
VPC connectivity issues are now stabilized. Unlike stated previously, only Serverless Containers product is impacted. We are now monitoring the situation. Thanks for your understanding.
- resolved
Incident is resolved now. Impacts for users were limited to nl-ams region, and Serverless Containers product: - From 10:00 UTC to 11:05 UTC: users received HTTP 5xx errors while calling their containers - From 10:00 UTC to 12:00 UTC: some containers were stuck in creating/updating - From 09:20 UTC to 12:20 UTC: some containers with VPC support lost connectivity to resources in their PN These were all unexpected impacts of the following maintenance: https://status.scaleway.com/incidents/f7lpf0j1c2sq. The upgrade was partially applied, since we stopped it to stabilize the situation. While the situation is stable now, some work will still need to be done to fully complete the maintenance in the future, but we will postpone it for now. In more details: a faulty step during our maintenance caused 1) our gateways to misbehave and start returning HTTP 503 errors and 2) VPC attached containers t
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.