All Client Sites Still Down – Clarification & Ongoing Issue (Account Unblocked but...)

Account Unblocked but Client Sites Still Down – Clarification & Ongoing Issue

Hello,

I’m posting to document what happened and to ask for clarification and assistance, as there is still an unresolved issue affecting my client sites.

I have been a Brizy user since June 20, 2021, and my account is fully paid, with the next payment due on July 25, 2027.

Initial Lockout and Immediate Impact

On January 12, 2026, I attempted to log in to Brizy Cloud to complete time-sensitive work on a client’s site that was due that morning. Instead of being able to access my account, I was presented with the following message:

“Your account has been blocked for security reasons.
One or more websites created under your account have been reported as SPAM, Phishing or Misleading.”

The consequences were immediate and devastating.

At that moment:

• All live client sites hosted under my Brizy Cloud account went offline simultaneously

• I lost access to the dashboard

• I lost access to backups and exports

• I lost access to billing and license management (I couldn’t even install the WordPress plugin I paid a lifetime license for)

• I lost access to in-platform support, which requires login

• I had no access to anything that I had paid for

This was a full account-wide shutdown, not a partial restriction.

Support Contact Timeline

I emailed Brizy support at approximately 10:00 AM on Sunday morning after discovering the lockout.

There was no official response for nearly 24 hours, and the first response from support did not arrive until approximately 5:00 AM Monday morning.

During this entire period, all client sites remained offline, and I had no access to backups, exports, or remediation tools.

Support Review and Identified Pages

After support review, my login access was restored. In the response I received, Basharat Reyaz stated that he personally reviewed my account and identified the following sites as not complying with the Acceptable Use Policy:

• A page displaying a “Flower of Life” title and image

• A page containing a free JavaScript-based media player (Webamp)
  https://webamp.org/

Both pages were:

• Non-commercial

• Contained no external links

• Contained no redirects

• Contained no forms

• Contained no downloads

• Collected no data

• Had no calls to action

Clarification Regarding the Policy Concern

After reviewing the Acceptable Use Policy myself, the only clause that appears potentially applicable is the section stating that, at Brizy’s discretion, websites with minimal content may be considered problematic.

I want to clarify that:

• Neither page functioned as a redirect

• Neither page linked externally

• Neither page attempted to mislead users

• Neither page posed a phishing, spam, or security risk

Given this, it appears the concern may have been related to page minimalism or lack of contextual framing, rather than any actual abusive or deceptive behavior. I am noting this so I can clearly understand the enforcement rationale and avoid similar false positives in the future.

Actions Taken Immediately After Access Was Restored

Once access was restored, I acted promptly and in good faith:

• I removed the “Flower of Life” page from Brizy Cloud entirely and moved it to my own independently hosted domain, since it was only an image and text.

• I unpublished the JavaScript Webamp player page, as it was specifically listed as a concern.

Ongoing Problem

Despite my account being unblocked and the above actions being completed:

• More than a day and a half later, all client sites hosted on Brizy Cloud remain down (all sites hosted on .com domains)

• There has been no restoration of service for those sites

• No additional timeline has been provided

It is now Tuesday, nearly 12:00 PM, and the situation remains unresolved.

The only site I have been able to bring back online is one where I:

• Purchased separate third-party hosting

• Repointed the domain away from Brizy Cloud

All other client sites hosted on Brizy Cloud remain unavailable