Monthly Bandwidth Transfer shows a very strange value
Hi,
For only one account, the Monthly Bandwidth Transfer shows a very strange value. It says that it has used 50 GB from 60 GB. But I have really no clue at all how that is possible.
If I check these statistics, it confirms it:
[Removed]
And if I check here, it says that from the third of December, it has suddenly raised a lot:
[Removed]
But the visitors count isn't grown, and neither is the bandwith? That what it says here:
[Removed]
Also, these statistics shows that there is no excessive bandwith usage:
[Removed]
I thought, maybe it calculates the external backups in the user bandwith but that's not http traffic and it isn't the case for other accounts.
So can someone please help me figure this out?
Thanks in advance!
-
Hello :) Could you attach the images directly to the post instead of linking to a third-party URL so we can take a closer look? Thank you. 0 -
Yes, numbers of images are the places where they were in my first post 0 -
The following document can help explain differences in bandwidth usage reports: Apparent Discrepancies in Bandwidth Usage Statistics - Documentation - cPanel Documentation Thank you. 0 -
Thanks, but that document talks mostly about few MB's difference because cPanel also measures the header etc. In that case cPanel says that there is more bandwidth used then then awstats for example says. And apparantly, awstats logs the requested file size, not the actual transferred bytes. So in that case, awstats could show a lot more then cPanel says. But in my case, cPanel measures 60 GB in comparison with 30 GB by awstats. Something else must be going on. Any other idea? Thanks 0 -
It's difficult to determine exactly why the bandwidth discrepancy occurred without reviewing the affected system. Could you verify if the issue was isolated to a single month, or if it continues to persist in the following months? Thank you. 0 -
It happened every month but seems to be a bot problem. They ate all the bandwidth. So problem solved. 0 -
I am happy to see you were able to address the issue. Thank you for updating us with the outcome. 0
Please sign in to leave a comment.
Comments
7 comments