This is how we work to ensure the stability and performance of Clonable

We continue to develop Clonable to ensure that international websites run as quickly, stably, and reliably as possible. That’s why we continuously invest in our infrastructure and the way we manage server traffic, connections, and security.

Recently, we’ve implemented several technical improvements to reduce unnecessary server load, better handle connection issues, and protect Clones from unwanted traffic. We’re also working on new features that give customers more insight and control.

Why are we investing in these improvements?

A Clone’s performance depends in part on the connection to the original website and the capacity of the servers involved. This can lead to various situations:

• High server load: Traffic from Clonable can put additional strain on the original server.

• Blocked Connections: Hosting providers or firewalls may block requests from Clonable when they detect high traffic. Learn how to prevent IP blocks from Clonable .

• Connection issues: A disrupted connection can cause a Clone to temporarily malfunction.

• Speed Issues: Problems with server capacity or connections can affect a Clone’s load time.

To minimize the impact of these situations, we are improving various parts of our infrastructure.

What improvements have we made?

• Circuitbreaker: Ensures that traffic is blocked early on in the event of network issues, thereby reducing the load on the original website.

• New runtime: Ensures that Clonable can better handle large numbers of concurrent visitors, so that peak traffic on a single Clone has less impact on other websites.

• Improved WAF: Helps detect and block malicious bots, crawlers, and other unwanted traffic, so that traffic via the Clones puts less strain on the system.

• Advanced WordPress subfolder proxy: processes traffic for translated WordPress subfolders more efficiently, reducing the load on the original server. See how to set up the Advanced Subfolder Proxy.

• Cloudflare integration: Enables the use of Cloudflare for a Clone, for example, for a custom firewall (WAF) or subfolder routing. Depending on the configuration, this can reduce the load on the original server.

• Allowlist and blocklist: These features let you block or allow IP addresses yourself, making it easier to control who can view your Clones.

What are we currently working on?

In addition to the improvements we’ve implemented, we’re further optimizing various components:

• Refining the WAF: Expanding existing WAF rules and blocklists to block even more malicious traffic, in order to prevent abuse via the Clones.

What else is on the agenda?

• Public uptime monitoring: insight into the availability of Clonable servers, so customers can quickly see if there’s an outage.

• Better support for connection issues: We’re exploring ways to help customers identify and resolve connection issues on their own. We’re also looking into improvements to our after-hours support.

• Performance Tracing: makes it easier to gain insight into the speed of Clonable.

Are you having problems with your Clone?

First, check whether the original website is accessible and whether your hosting provider or firewall might be blocking requests from Clonable .

Having trouble? Contact our support team. Please specify which Clone you’re using and what issues you’re experiencing. We’ll be happy to help you identify the cause.