Bandbreitennutzungs und warteschlange unterschiedliche werte[Translation-Bandwidth usage...

After starting a Google sheet to track this issue...I see now that the issue is more complicated than what appeared to be just a simple divide by 100 error based on game updates once I started examining the differences over time compared to the activities
that I did on my console yesterday/today:

• Play Destiny 2 - usage is ca 1.76x less than actual
• Watch Netflix - usage is ca 79x less than actual
• Watch YouTube - usage varied from ca 52 to 111x less than actual
• Xbox Speedtest - usage is ca 16x less than actual
• Play PUBG - usage is ca 5.7x less than actual
• idle (at dashboard, in settings) - usage is ca 1.75x less than actual
• Game updates - usage is ca 99x less than actual
  

I'm going to continue tracking different activities with each new Dashboard release to see if/when there is any improvement in tracked bandwidth usage.

My usage for November overall was ca 30x less than actual. So far for December it's ca 20x less than actual. If you need to know how much bandwidth you are using then I recommend using a router that includes that kind of tracking given that the Xbox console
is now totally inaccurate for that purpose.

Based on the dramatic change in monthly total for my console(s) in the Dashboard Preview program...it appeared to me that the coding change and/or error in monthly total began sometime in August 2019.

I'll be tracking the data in a Google spreadsheet going forward so I have a better record of the actual observations that I've been making and reporting via Insider Hub problem reports.

"If you need to know how much bandwidth you are using then I recommend using a router that includes that kind of tracking given that the Xbox console is now totally inaccurate for that purpose."

I use an app provided by my ISP to get overall monthly bandwidth usage, but miss the convenience of checking the XBox option.

As an example, before doing one of the many weekly OS updates of ASA Insider builds +- 450MB, I would check the stats, before and after download, and usually see 1-2MB had been downloaded.

Anyone on a monthly data cap could easily exceed their cap if they have a large game library updating. The last RDR2 update was >7GB which did not show up in the XBox stats, but did in the ISP app.

Thanks Frathos, I posted about this issue on Reddit XBox Insider Forum and I'm still waiting for acknowledgment
that it is a problem.

I first noticed this about 3-4 months ago, but as you will see from replies to my post the issue has been around in Insider builds for longer than that.

Everytime I do an update I use Report a problem to get some attention to this annoying issue.

The more reports the better.

Respectfully XBF Brad A...something has changed in the code for tracking bandwidth usage as it is now grossly incorrect (by what appears to be a factor of 100 for game/app updates). The Total usage this period is no longer an estimate for the console only...it's
a very tiny fraction of the actual usage. I have done many game/app download tests (one for every new Dashboard Preview release) and the result is pretty much exactly the same every time now...it appears that the sum added is the download total divided by
100 so no wonder the monthly total is grossly inaccurate.

Workaround in the meantime until Microsoft dev team fix the issue if ever: multiply the value by 20 as a rough guesstimate to your total monthly usage.

Note(s):

• I changed the multiplier mentioned above tonight (Dec 21, 2019 Sat. evening) when I realized that my original x100 estimate is grossly more than what my router is showing for my Xbox One console in the last month so maybe game/app usage/downloads is tracked
  differently.
• I haven't been tracking my tests in a Google sheet which I will do from now forwards to get a better idea of the exact number differences noted.
  
• The x20 noted above is derived from the data I captured tonight from console and router.
• The hourly data is showing wildly different multipliers for the differences between tracked values so the problem may be more complicated than just a simple divide by 100 error as I originally suspected based on just examining the difference for game downloads/updates.