The XDN takes a breather while WPX system admins step in
Read the full story →
The XDN panel on the morning of October 14: the main domain’s rebuild spinning (blurred here for privacy), the four subdomains happily ON.
🕳️ How the toggle fell
Christopher opened ticket #517528 (“XDN toggled off”) asking the polite question: was this us? The screenshot showed the main domain’s XDN status spinning on “building” while all four subdomains - service, publications, newsletter, publicrelations - sat comfortably On.
The suspicion: the toggle-off happened upon the temporary suspension during the payment lapse - a side effect nobody ordered, discovered only because the builds stopped deploying. Nikolay G. at WPX tried resetting the XDN a few times on his end; it stayed stuck. The ticket now sits Escalated with the System Admins, whose window is Monday-Friday, 09:30-18:00 GMT+3.
🧘 Why this one is calm
Everything behind the XDN is intact: pages render, edits save, and the fellowship keeps meeting on Zoom as always. The XDN is a delivery layer, not the source of truth - when it unsticks, the queued changes simply appear. Worst case, a cache is a patience problem, not a data problem.
This continues the story told in the lights came back on - same hosting scare, next chapter. And the fuller background - why the site ever felt slow, and why it wasn’t AI - lives in the library: Why the site got slow.
One reset at a time.