Wix incident

RESOLVED: Some Users Have Issues with Saving/Publishing Sites

Minor Resolved View vendor source →

Wix experienced a minor incident on May 7, 2026 affecting Wix Editor and Wix Studio, lasting 10h 15m. The incident has been resolved; the full update timeline is below.

Started
May 07, 2026, 11:36 AM UTC
Resolved
May 07, 2026, 09:51 PM UTC
Duration
10h 15m
Detected by Pingoru
May 07, 2026, 11:36 AM UTC

Affected components

Wix EditorWix Studio

Update timeline

  1. investigating May 07, 2026, 11:36 AM UTC

    We are currently investigating this issue.

  2. investigating May 07, 2026, 11:56 AM UTC

    We are continuing to investigate this issue.

  3. identified May 07, 2026, 11:59 AM UTC

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

  4. identified May 07, 2026, 12:06 PM UTC

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

  5. identified May 07, 2026, 12:23 PM UTC

    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.

  6. identified May 07, 2026, 01:55 PM UTC

    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.

  7. identified May 07, 2026, 03:57 PM UTC

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

  8. identified May 07, 2026, 05:44 PM UTC

    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.

  9. monitoring May 07, 2026, 06:12 PM UTC

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

  10. resolved May 07, 2026, 09:51 PM UTC

    This incident has been resolved.