[BookMyName] PHP emergency migration — multiple service regressions
This incident has been resolved.
The latest update from Scaleway.
State
Resolved
Started
9 d ago
2026-10-23 14:24 UTC
Lasted
4 days
until 2026-10-27 10:36 UTC
Worst impact
Degraded
Timeline
2 updatesIdentified
4 days 100%
Updates
Times in UTCAs posted by Scaleway
This incident has been resolved.
On 2026-10-21, a critical PHP RCE (CVE-2026-109618/109619, CVSS 9.2) forced an emergency migration of the BookMyName services. The migration introduced PHP compatibility regressions in legacy code, impacting customers since 2026-10-21.
Affected components
2Follow 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