Review Time
Scala Hosting is extremely overpriced. If you choose cPanel, they add excessive fees and push customers toward their proprietary sPanel, which hardly anyone uses outside of their own clients. For example, 100 cPanel accounts cost $74 with Scala, while other providers charge only around $44 for the same number a huge and unjustified difference.
On top of that, their VPS plans are very expensive compared to competitors. Even reseller hosting is overpriced, and when you need an additional IP, they refuse and insist you must buy a VPS instead even if you don’t need one.
Their pricing strategy seems focused only on customers willing to pay high rates, rather than adopting a sustainable model where fair, repeated payments would bring them more long-term success.
We recently had a support ticket related to a WordPress Multisite setup. Initially, only one site was impacted. I want to acknowledge the effort of the representative who started the case by removing the affected site from the network and performing necessary cleanup. While this took some time, it helped stabilize the environment initially. The situation escalated when another technical support team member suggested creating individual subdomains with separate document roots for the child sites. This advice was technically inaccurate for a WordPress Multisite configuration and led to three additional child sites facing 403 errors, even though they had been functioning correctly. After that, another representative indicated that since the subdomains were loading from empty document roots, the affected sites would need to have their content exported or be rebuilt as standalone installations. Following this suggestion would have resulted in unnecessary rebuilds, as the issue stemmed from incorrect routing, not missing content. After we provided a detailed explanation of how WordPress Multisite subdomains function, the representative correctly reverted the affected subdomains back to the multisite document root, successfully restoring the three child sites. I appreciate the willingness to apply the right fix once the underlying structure was clarified. Lastly, I want to commend another team member who resolved the remaining issue with the affected site by adjusting the configuration and ensuring it was set up correctly as a standalone site. After this intervention, all websites began functioning as intended. Support was responsive and professional throughout the process, but this experience revealed some gaps in knowledge regarding WordPress Multisite at certain support levels. While the issue was ultimately resolved, it became more complicated than necessary due to earlier incorrect guidance.
We recently had a support ticket regarding a WordPress Multisite setup. Initially, only one site was affected. I want to recognize the effort of the representative who began addressing the issue by removing the impacted site from the network and performing necessary cleanup. Although this took some time, it helped stabilize the environment initially. The situation escalated when another technical support team member suggested creating individual subdomains with separate document roots for the child sites. This advice was technically incorrect for a WordPress Multisite configuration and resulted in three additional child sites encountering 403 errors, despite functioning correctly before. Following that, another representative indicated that since the subdomains were loading from empty document roots, the affected sites would need to have their content exported or be rebuilt as standalone installations. Following this suggestion would have led to unnecessary rebuilds, as the issue was due to incorrect routing, not missing content. After we provided a detailed explanation of how WordPress Multisite subdomains operate, the representative correctly reverted the affected subdomains back to the multisite document root, successfully restoring the three child sites. I appreciate the willingness to apply the right fix once the underlying structure was clarified. Lastly, I want to commend another team member who resolved the remaining issue with the affected site by adjusting the configuration and ensuring it was set up correctly as a standalone site. After this intervention, all websites began functioning as intended. Support was responsive and professional throughout the process, but this experience revealed some gaps in knowledge regarding WordPress Multisite at certain support levels. While the issue was ultimately resolved, it became more complicated than necessary due to earlier incorrect guidance.
I transitioned from another hosting service to a new provider, and everything has been excellent—smooth and fast. Recently, I faced an issue with a plugin that caused serious errors on my website. The support team responded in under five seconds and helped me identify the problem in less than 30 seconds, resolving it in another 30 seconds. There's no need to elaborate further; it's a five-star service. Best investment I've made this year.
Fantastic, round-the-clock support! No matter when you log in, there's always someone available to assist you. This is crucial for beginners like me. Since joining, I feel empowered to manage everything on the server. Additionally, the speed of my sites has significantly improved! I can't express my gratitude enough. You have to experience it for yourself!
Claim your business profile now and gain access to all features and respond to customer reviews.
