I’m hoping someone here, particularly anyone with experience troubleshooting Wix’s hosting or routing infrastructure, might have some insight into a very unusual issue we’re experiencing.
We manage several Wix Studio websites for single client. They’ve been running reliably for 2+ years, without a single major issue. That changed yesterday.
Around 5 PM EST on November 2, one of the websites became inaccessible.
Here’s what’s happening:
-
The homepage returns an HTTP 302 redirect to a URL ending in /facts.htm, which doesn’t exist.
-
Existing interior pages return HTTP 404 errors (no redirects).
-
All pages and content remain intact in the Wix editor.
-
The site was last published on October 16, with no known changes preceding the outage.
-
The other Wix websites we manage for this client are functioning normally.
What we’ve investigated:
-
Our client’s IT administrator verified the authoritative DNS configuration, including nameservers, A and CNAME records, and consistency across DNS servers.
-
No DNS changes have occurred since August.
-
We’ve reviewed custom code and URL redirects. No rule directing the homepage to
/facts.htmwas found. -
At Wix Support’s direction, we disconnected and reconnected the domain multiple times, without success.
-
The homepage’s redirect is occurring at the HTTP response level, before any browser-side scripts could execute.
One particularly unusual detail: /facts.htm matches a 3rd party tool link used by the client’s customers. Whether that’s connected is unknown, but it’s an odd coincidence.
Where things stand:
We’ve been working with Wix Support since approximately 10 PM yesterday. The issue was escalated to the specialized domains team at 10:47 PM, and the case has since been flagged as a priority. The offline/escalation team has yet to give us any updates, so we’re kind of running blind here with nothing to offer our client in terms of information.
We have yet to receive a technical finding, explanation, or estimated resolution time.
This is a business-critical website, and the outage is placing our client relationship at serious risk.
My questions for the community:
-
Has anyone encountered a Wix website suddenly returning an unexplained server-side 302 redirect alongside 404 errors on otherwise valid published pages?
-
Could an issue with Wix’s hostname-to-site mapping, edge routing, or published-site configuration explain both symptoms?
-
Has anyone successfully resolved a similar issue without requiring Wix’s internal engineering team?
I have a significant amount of Wix experience over the years and have never encountered anything like this.
Any insight, particularly from someone familiar with Wix’s routing infrastructure, would be greatly appreciated.
Thanks!