Slow download speeds on Battlenet

Is it just Battlenet or are other services affected? If just them could be slow upload on their end or specific route between you and them.

Just Battlenet, I have no problems downloading from Steam, for example. So who can I report this problem to? What kind of diagnostics can I run to pinpoint which hub(s) is/are bottlenecking my speeds? I don't like to keep toggling on VPN to get around this since changing connections will interrupt my other services.

Your other services? What do have running alongside Battlenet? Just wondering if there is any odd interaction there.

Nothing bandwidth intensive, just standard logged in services like Discord, Xbox app, or sitting idly in an online game. I could have all that running and my downloads on Steam would still reach the top end of what I would expect, however, they have recently been abysmal on Battlenet.

I would first check your download limits in Battlenet itself, just to be sure no throttle was set. Could unplug Gateway for a few minutes and then boot backup to see if that makes a difference once everything is freshly registered.

Model of  Gateway?

Are you connected directly to it or have your own router or anything in between?

When the issue started did anything else happen at that time?

May have to run a ping test to the Battlenet servers to see the route it is taking and if there are any hops that show an issue.

Since you see improvement with VPN, I would run a ping test with that on to compare differences.

Had a similar issue with Microsoft gamepass.  I don’t download much from it but I would say the speed was a third to half of what the connection supports.  Steam is fine.  Even if you can prove Att isn’t giving the best path to download servers, it’s a stretch to get them to take action, but if you can gather evidence, share it here please. @JefferMC might make suggestions on what useful data to collect.  Personally though I’d rather be playing than wasting time playing detective.  

To diagnose this, I would try to capture traceroutes to the BattleNet servers.  It would be nice to have traceroutes when there's not a problem and when there is.  I'd try it with Cloudflare WARP on and off to see what the difference is (which really can only be that the DNS name translates to a different IP address).

If you can establish that there is congestion or chaotic routing in the AT&T network, then we can try to get someone to send a ticket to the core networking teams.  Ideally, I would like to have multiple people with the same complaint and similar traceroutes to help build the case.

If we find the issue is in a peering network, we can ask AT&T not to use that peer, but that's a real longshot.

If the case we build is that the issue is inside the BattleNet network, then you can give them the evidence and hope they'll look into it (When they do have a problem, odds are they already know and are just trying to divert people while they try to clean it up).

Thanks JefferMC, I'll try to provide that info. I actually did a tracert with and without WARP, but lost the screenshot a few days before starting this thread, I'll do it again next time there is a game update (Call of Duty on Battlenet). There was a Pre-Release Content download today for an upcoming patch, but resource monitor showed that it was downloading from Akamai CDNs, which had no problems reaching near max expected download speeds (patch-day downloads are direct from Battlenet servers, so I'll find out then).

The slow download speed happened again with today's patch.

Here is the tracert

And here is the tracert to the same IP with WARP active (note: when the download resumed, it connected to the same network but different host, where only the 4th octet differed)

It looks like things are a little worse from a latency perspective (of ICMP TTL responses, at least) using WARP. 

with today's patch.

With a patch to "Call of Duty?"  Do you think that's coincidence?