Wix outage history

We are currently investigating this issue.

We are continuing to investigate this issue.

Monitoring telemetry shows normal performance across all services. We are continuing to observe system metrics closely.

This incident has been resolved.

We are aware that users are experiencing multiple issues with Wix Services and we are currently investigating it. Further updates to follow shortly.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

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 errors within minutes, our on-call team was engaged immediately, but, because the change had been made in a region that was being retired, it was not an obvious candidate for causing live traffic impact, and identifying it as the cause took longer than it should have. Once identified, we mitigated by shifting European traffic away from the affected region and serving it from other active regions, and restored the removed configuration in parallel. Once service was fully restored, traffic was returned to the affected region without further disruption. Following this incident, we are introducing automated validation that verifies whether a network resource is still in use before it can be removed, blocking the change from being merged if it is. We are also strengthening review requirements for infrastructure changes, and improving high availability and automatic failover between regions, including a faster way to move traffic out of a region when needed, so that similar issues can be contained before it affects users.

We are aware that some users are experiencing issues with elements missing on Wix Harmony Live Sites and are currently investigating it.

This incident has been resolved.

We've identified that issues with SMS Deliverability are related to incident on Twilio side. Please refer to Twilio for additional information: https://status.twilio.com/

We're seeing a decreased number of issues with SMS Deliverability that are related to incident on Twilio side. In case you still experience issues, please refer to Twilio for additional information: https://status.twilio.com/

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/

We are currently investigating this issue.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

We are continuing to work on a fix for this issue.

Our engineering team has identified the root cause of the issue and is actively executing multiple resolution paths to restore service as quickly as possible. Further updates to follow shortly.

A fix has been implemented and we are monitoring the results.

The underlying issue has been identified and fixed. Systems are currently recovering, though it may take a short time for all services to return to full capacity. We are continuing to monitor the situation closely.

We are continuing to monitor for any further issues.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

On July 7th at 2:10 PM UTC, some users experienced issues loading the Wix Editors. The issue also affected saving and publishing for some users during this period. All functionality was fully restored within approximately 20 minutes. The root cause was a deployment of a new version of one of our internal platform services that did not follow our standard gradual rollout process. Instead of being deployed incrementally across our infrastructure, as is our normal practice, the new version was released to all environments at once. This caused elevated latency in that service, which cascaded to the Editors. Our team identified the root cause quickly, rolled back the service to its previous stable version, and accelerated the recovery by restarting affected instances across our infrastructure. This fully resolved the issue. Wix continuously deploys updates across our microservice platform, the vast majority seamlessly and without any user impact. The safeguard that is specifically designed to prevent this type of issue was not applied in this case. Following this incident, we have introduced automated guardrails on the affected service to prevent new versions from causing latency spikes that propagate to dependent services. We have also strengthened our platform-wide rollout policies to enforce gradual deployment practices and make it harder to bypass monitoring and staged rollout checks in the future.

We are investigating issues with multiple services.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

On July 7th at 7:50 AM UTC, some users experienced issues loading the Wix Dashboard and Wix Editors. All functionality was fully restored within approximately 20 minutes. The root cause was an interaction between two events: a new automated database infrastructure optimization feature introduced on July 5th, and a routine planned traffic shift between data center regions carried out on the morning of July 7th. The new feature is designed to improve infrastructure efficiency by continuously monitoring database throughput usage and automatically adjusting capacity limits to reflect actual demand. On July 7th, before the day's planned traffic operations had taken place, the feature applied reduced capacity limits to several database clusters in one of our regions, based on the lower load observed earlier that morning. Shortly after, a routine planned traffic shift moved additional user traffic to that same region. The database clusters, now operating under reduced limits, received more load than those limits could accommodate, causing database response times to spike and errors to cascade across our dashboard and editors. Our team identified the root cause and resolved the incident by redirecting traffic to an unaffected region. We also provisioned new database nodes with higher capacity limits to restore full throughput in the impacted region. Following this incident, we have paused the automated optimization feature while we put additional safeguards in place. We have audited all database clusters where capacity adjustments were applied to confirm they are operating correctly. We are also implementing coordination checks to ensure that automated capacity adjustments and planned traffic operations are always validated against one another. We have additionally improved monitoring and alerting for automated infrastructure changes to enable faster detection and response if a similar situation were to arise in the future.

We are currently investigating this issue.

We are continuing to investigate this issue.

The issue has been resolved and we are continuing to monitor.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

The issue has been resolved. If you are still having issues with Harmony container content not loading, please contact Customer Care.

We are currently investigating this issue.

We are continuing to investigate this issue related to Stores Products and Checkout. We have identified an issue with our DB, and are currently working on reverting the changes that caused it.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating an issue with accessing live sites affecting some users.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.

This incident has been resolved.

The issue has been resolved

We are currently investigating this issue.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

Our engineers identified an issue caused by a corrupted version of the editor. This version has already been reverted, but users who attempted to publish their sites while it was active may still be affected. We are actively working on a fix.

The issue has been identified, and a fix is being deployed.

Our engineers identified an issue caused by a corrupted version of the editor. This version has already been reverted, but users who attempted to publish their sites while it was active may still be affected. We are still actively working on a fix.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

This incident has been resolved.

Some site visitors may experience issues on multiple services.

This incident has been resolved.