RESOLVED: Multiple Issues with Wix Services in European Region
On September 15th at 8:27 AM UTC, some users in Europe experienced errors when accessing [Wix.com](http://Wix.com), logging in, and viewing live sites, as well as issues using site features such as Bookings, Stores and Payments. All functionality was fully restored within approximately 30 minutes. The root cause was an infrastructure change intended to remove unused resources in one of our European data center regions. Those resources were still serving live traffic. We regularly decommission and clean up infrastructure that is no longer needed. In this case, the change was made in a region that had already been largely retired, and the resources targeted for removal were believed to be unused. That assumption was not fully verified before the change was applied, and configuration that was still routing European traffic was removed. Requests arriving in that region could not reach the services behind them, which led to errors across a number of Wix products. Our monitoring detected the
The latest update from Wix.
State
Resolved
Started
48 d ago
2026-09-15 08:35 UTC
Lasted
42 min
until 2026-09-15 09:17 UTC
Worst impact
Major outage
Timeline
5 updatesInvestigating
16 min 39%
Identified
5 min 12%
Monitoring
21 min 49%
Updates
Times in UTCAs posted by Wix
On September 15th at 8:27 AM UTC, some users in Europe experienced errors when accessing [Wix.com](http://Wix.com), logging in, and viewing live sites, as well as issues using site features such as Bookings, Stores and Payments. All functionality was fully restored within approximately 30 minutes. The root cause was an infrastructure change intended to remove unused resources in one of our European data center regions. Those resources were still serving live traffic. We regularly decommission and clean up infrastructure that is no longer needed. In this case, the change was made in a region that had already been largely retired, and the resources targeted for removal were believed to be unused. That assumption was not fully verified before the change was applied, and configuration that was still routing European traffic was removed. Requests arriving in that region could not reach the services behind them, which led to errors across a number of Wix products. Our monitoring detected the
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are aware that users are experiencing multiple issues with Wix Services and we are currently investigating it. Further updates to follow shortly.
Affected components
3Wix in the last 90 days
Full historyIncidents in 90 days
6
Days with an incident
6
Median duration
1 h 5 min
This incident
36% shorter than the median
Other Wix incidents
All incidentsWix·RESOLVED: Some Users Are Experiencing Issues With Multiple Services
This incident has been resolved.
Wix·RESOLVED: Some Elements not Appearing on Wix Harmony Live Sites
This incident has been resolved.
Wix·RESOLVED: SMS Delivery Delays on Twilio Side
Issue with SMS Delivery Delays on Twilio side is resolved, and is no longer impacting Wix services. Please refer to Twilio Status Page for additional information: https://status.twilio.com/
Wix·RESOLVED: Wix Sites Loading Slow in Some Regions
This incident has been resolved.
Wix·RESOLVED: Issues opening Wix Editors and dashboards
This incident has been resolved.
Follow Wix
Your coding agent knows when Wix is down, and tells you when a failure is theirs, not yours. You can also get Wix 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 "wix" and tell me if Wix 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=wix/feed subscribe https://outages.cc/feed.xml?providers=wixFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane