RESOLVED: Issues Accessing Editor/Studio

What to do

• Check whether you use Wix Wix Editor, Wix Studio. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 10m it lasted.

  Anything that failed between 2026-07-07 14:25 UTC and 2026-07-07 14:35 UTC may need a replay.

• Subscribe to Wix's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=wix works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Wix 5

1. investigatingJul 7, 2026, 2:25 PM UTC

   We are currently investigating this issue.

   provider

2. identifiedJul 7, 2026, 2:26 PM UTC

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

   provider

3. monitoringJul 7, 2026, 2:29 PM UTC

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

   provider

4. resolvedJul 7, 2026, 2:35 PM UTC

   This incident has been resolved.

   provider

5. postmortemJul 9, 2026, 1: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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.