[Transactionnal Email] - Delivering Issue
Scaleway Transactional Email had a delivering issue that affected some emails in the Elements products. Scaleway identified the issue and restored outbound traffic. The incident is resolved and lasted about 3 hours and 6 minutes.
State
Resolved
Started
Lasted
3 h 6 min
Worst impact
Degraded
Timeline
3 updatesIdentified
1 h 42 min 55%
Monitoring
1 h 24 min 45%
Updates
Times in UTCAs posted by Scaleway
All emails have now been sent, and traffic is back to normal.
We have identified the issue and successfully restored outbound traffic. The problem was caused by a network configuration that failed to apply properly. We applied fix, which resolved the situation, and outgoing emails should start clearing and sending out gradually.
Some customers may experience emails getting stuck while processing or sending. We are actively working to resolve the issue and sincerely apologize for the inconvenience caused.
Affected components
2Scaleway in the last 90 days
Full historyIncidents in 90 days
61
Days with an incident
32
Median duration
7 h 41 min
This incident
60% shorter than the median
Other Scaleway incidents
All incidentsScaleway·[Serverless Functions/Containers] - [nl-ams] - Connectivity issues
Scaleway Serverless Containers in the nl-ams region had connectivity problems. Some containers returned HTTP 5xx errors, were stuck in creating or updating, or lost Private Network connectivity. Scaleway reports the incident resolved. It lasted about 4 hours and 29 minutes.
Scaleway·CKPT (pl-waw) Traces ingestion is degraded
Scaleway Cockpit traces ingestion is degraded on the pl-waw region. This incident is resolved. It lasted 2 hours and 38 minutes.
Scaleway·[VPC] - [FR-PAR-1] Metadata API through VPC is experiencing slow response time
Scaleway reports slow response time on the Metadata API through VPC in the fr-par-1 region. DNS over TCP through VPC may also be slow. Scaleway reports that the situation should now be back to normal and is monitoring it.
Scaleway·[SERVERLESS] - [fr-par] - Some Serverless Containers are unreachable
Some Serverless Containers in the fr-par region were unreachable. The affected components were fr-par-1, fr-par-2, fr-par-3, and Serverless Container. Scaleway reports that the incident is resolved and that it lasted about 4 hours and 10 minutes.
Scaleway·[LOAD BALANCER] - [PAR1] - Monitoring PN down leading to autohealing mechanism stopped
Scaleway reports that Load Balancer creation and configuration do not work in the fr-par-1 region. The provider also reports that Load Balancer auto-healing stopped in fr-par-1. Scaleway states that the situation should be back to normal and continues to monitor it.
Follow Scaleway
Your coding agent knows when Scaleway is down, and tells you when a failure is theirs, not yours. You can also get Scaleway incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "scaleway" and tell me if Scaleway has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=scaleway/feed subscribe https://outages.cc/feed.xml?providers=scalewayFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane