[APPLE SILICON] - FR-PAR-1 - Macs cannot reach Scaleway public API
Apple Silicon Macs in fr-par-1 cannot reach the Scaleway public API. Scaleway reports that it is investigating the incident. Scaleway advises customers to avoid a reinstall or a reboot of the Macs at this time.
State
Investigating
Started
Ongoing for
4 h 58 min
Worst impact
Partial outage
Timeline
1 updateInvestigating
4 h 58 min 100%
Updates
Times in UTCAs posted by Scaleway
Apple Silicon on par1 cannot reach the public scaleway API. This impacts some workflows on the macs and customers should avoid triggering a reinstall or a reboot for the time being.
Affected components
4Scaleway in the last 90 days
Full historyIncidents in 90 days
81
Days with an incident
44
Median duration
16 h 59 min
This incident
71% shorter than the median
Other Scaleway incidents
All incidentsScaleway·[GENERATIVE API] - [GLOBAL] - Increased error rate for model DeepSeek v4.1 Flash 1017
Scaleway reports more errors for the model DeepSeek v4.1 Flash 1017. The Generative API is degraded. Scaleway is investigating the problem.
Scaleway·[IAM] - Cannot add or update organization-level policy rules
Scaleway reports that users cannot add or update IAM policy rules with organization-level permission sets. The incident is resolved. It lasted 67 minutes.
Scaleway·[Generative API] - [global] - GLM-5.3 timeouts
Scaleway reports that requests to the GLM-5.3 model in the Generative API returned timeout errors globally. Scaleway reports that this incident is resolved after 43 hours and 3 minutes.
Scaleway·[VPS] - Paris - servers stuck in maintenance
Scaleway Dedibox VPS instances in Paris do not work when they stay in the vps.states.maintenance status. Scaleway reports that the incident is resolved. The incident lasted from 13 November 2026 to 16 November 2026.
Scaleway·[Transactional Email] - world - Delayed email delivery to Microsoft domains (Outlook/Hotmail)
Scaleway Transactional Email delivery to Microsoft consumer domains (Outlook and Hotmail) was delayed. All sending pools were affected. Scaleway reported the incident as resolved on 2026-11-16. The incident lasted about 3 days and 14 hours.
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.live/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.live/feed.xml?providers=scaleway/feed subscribe https://outages.live/feed.xml?providers=scalewayFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane