Wix incident

RESOLVED: Issues Accessing Editor/Studio

Major Resolved View vendor source →

Wix experienced a major incident on July 7, 2026 affecting Wix Editor and Wix Studio, lasting 9m. The incident has been resolved; the full update timeline is below.

Started
Jul 07, 2026, 02:25 PM UTC
Resolved
Jul 07, 2026, 02:35 PM UTC
Duration
9m
Detected by Pingoru
Jul 07, 2026, 02:25 PM UTC

Affected components

Wix EditorWix Studio

Update timeline

  1. investigating Jul 07, 2026, 02:25 PM UTC

    We are currently investigating this issue.

  2. identified Jul 07, 2026, 02:26 PM UTC

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

  3. monitoring Jul 07, 2026, 02:29 PM UTC

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

  4. resolved Jul 07, 2026, 02:35 PM UTC

    This incident has been resolved.

  5. postmortem Jul 09, 2026, 01:07 PM UTC

    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.