Hello,
We have used DirectAdmin many times during the course of the last 7 Years in Shared and VPS Hosting accounts apart from H-Sphere and cPanel.
We have always noticed that Bandwidth calculation in DirectAdmin is about 3 times higher than in H-Sphere or cPanel. We have noticed this through our practical experience in managing many hosting accounts for many years.
We are using DirectAdmin now. We are noticing a bandwidth usage of about 3 GB per day. 2 weeks back, we had all these domains in 2 different hosting accounts with H-Sphere in one and cPanel in another for more than 18 months. We have never noticed a total bandwidth usage of more than 1 GB per day in both these accounts even after adding the usage in both these accounts together.
Kindly verify and do the necessary correction immediately so that users and reseller accounts do not get suspended due to the erroneous bandwidth calculation by the Hosting providers with DirectAdmin.
We like DirectAdmin more than any other Hosting panels but for this bug.
Thanks,
Lakshmanan
We have used DirectAdmin many times during the course of the last 7 Years in Shared and VPS Hosting accounts apart from H-Sphere and cPanel.
We have always noticed that Bandwidth calculation in DirectAdmin is about 3 times higher than in H-Sphere or cPanel. We have noticed this through our practical experience in managing many hosting accounts for many years.
We are using DirectAdmin now. We are noticing a bandwidth usage of about 3 GB per day. 2 weeks back, we had all these domains in 2 different hosting accounts with H-Sphere in one and cPanel in another for more than 18 months. We have never noticed a total bandwidth usage of more than 1 GB per day in both these accounts even after adding the usage in both these accounts together.
Kindly verify and do the necessary correction immediately so that users and reseller accounts do not get suspended due to the erroneous bandwidth calculation by the Hosting providers with DirectAdmin.
We like DirectAdmin more than any other Hosting panels but for this bug.
Thanks,
Lakshmanan