Incorrect traffic amount in bitdefender VPN stats issue

Hi everyone,

I have bitdefender VPN premium and it shows an incorrect download traffic amount.

It shows the traffic for the last month/week as 52GB when windows only shows 12GB of traffic that month.

This PC is a fresh windows 10 install for about a week now and I know I did not have 52GB of traffic in the last week as the PC mostly been idling and I haven't done much on it yet.

Find more posts tagged with

Comments

Petersl

My version of the bitdefender VPN app is 27.3.0.7(b).

Petersl

Hi everyone,

I still get the incorrect traffic amount displayed in the bitdefender VPN app, it shows 171GB traffic in the last month (I'm only been using the VPN app for 8 days now) but windows shows only 34,52GB traffic in the last 30 days.

It also show for today's traffic 43,3GB traffic but I only started using my PC at 10 am now and it has been idle for those 10 hours of the day. It also shows an incorrect amount for the ads and trackers blocked, as I haven't used a browser today yet how could it have blocked 306 ads and trackers?

I've tested this on a different PC as well that is on a different network and there is an discrepancy with the traffic there as well.

I'll tag @Alexandru_BD @camarie @dvsls

Petersl

This is the screenshot of the other PC I've tested this on, the traffic amount also shows a discrepancy.

Petersl

Hi everyone,

Yesterday Sunday the first of February it showed as monday instead of sunday in the bitdefender VPN connection time graph.

Maybe because it was the first of the month so it resets the graph. The first of next month will be a sunday so I'll check then if it also displays monday then.

Alexandru_BD

Hi,

I know there are currently some inconsistencies in these graphs, this also applies to scanned connections in Mobile Security, and the VPN, where the number of blocked ads and trackers displayed may be incorrect. A fix should be coming this week.

Regards

Petersl

Hi @Alexandru_BD

There's also a discrepancy with the IP address, I first thought this had to do with the DNS of my adaptor and when I changed my ethernet adaptors DNS to default instead of a manual configured one the IP address discrepancy was resolved but now it seems to be back even with the DNS set to automatic.