High Download Speeds Slow webpage load times

Please provide specific examples and empirical evidence of what you're talking about.

All evidence I'm mentioning has been observed on a desktop directly connected to the modem via Ethernet. Slow web page load times, online games getting dropped then reconnected after a few moments (League of Legends, Hearthstone). Stuttering when streaming games NVIDIA Shield via moonlight application. None of this began occurring until late Friday evening.

"Slow" is not empirical, it's subjective.  Empirical would be something like "The LoL login page used to load in 2 seconds, now it takes 15.5 seconds and not all the images render."

Have you tried doing traceroutes to the server addresses to see if you can see any points of increased latency?  Can you provide us such traceroutes?

What did you think changing the default DNS would accomplish?

Images on sites such as reddit are going from instantly loading when going to the page to take upwards of 15-20 seconds to load. As I mentioned previously in League of legends I will sometimes receive a 'issues reaching the server. Attempting to reconnect.' error which goes away after about 10-15 seconds. 

As for changing DNS, it was simply troubleshooting in case the slow load times were caused by a DNS issue....

Hi @kave294

We understand you're concern. Let's get the help you need.

We appreciate that you've tried few troubleshooting steps. To begin with, you need to check your DNS settings. Typically, DNS settings should be set to obtain DNS information from the AT&T servers. In some situations, you may have to force DNS to resolve your issues, but the below settings not the preferred setting, just try this and let us know how it works.
 

Windows 11

1. Right-click on the Start Menu.
2. Choose Settings.
3. In the Settings menu choose Network & Internet.
4. Select the Connection type (ethernet, wireless, etc.).
5. Click Edit next to DNS server assignment, verify Automatic (DHCP) is selected.
6. Click Save.

Windows 10

1. Right-click on the Start Menu.
2. Click the Network Connections option in the menu.
3. Any Network Connections available on that computer will display.
4. Right-click on the connection that the customer is using (such as, Wi-Fi, Ethernet, and so on) and select Properties.
5. Double click Internet Protocol Version 4, or make sure that is the only option checked and select Properties.
6. Ensure both Obtain an IP Address automatically and Obtain a DNS server address automatically are selected.
7. Click OK.

Whatever the windows operating system that you use, ensure both Obtain an IP Address automatically and Obtain a DNS server address automatically are selected.

Thank you for contacting AT&T Community & Forums!

Maria, AT&T Community Specialist.

I've switched my DNS back to automatic, and my load times to web pages are 2-5 seconds longer than using the Google DNS.

Hi @kave294

Let's help find out what's causing this. 

After reviewing your concern and trying to resolve through the Community Forums, it looks like you may need more account specific support.  To assist you best, we encourage you to review our Contact Us page to identify what method you’d prefer to reach out for this account level help.  You can call, chat, or reach out via social media, and we can review your specific issue and provide you support.  We’re sorry we weren’t able to resolve your concern directly in the forums, but let us know if we can assist with anything else.

Thank you for contacting AT&T Community Forums,
Maria, AT&T Community Specialist.

I really wouldn't bother contacting support at this point.  There's nothing they can help you with other than rebooting or factory resetting your gateway (which you can try).  If you continue to have this problem for an extended period and have a decent amount of information in the form of traceroutes, ping histories, etc., then it might be time to try to contact them to get a ticket opened.

For now, "tracert 104.160.131.3" in a cmd window and post the response.  It would have been great to do this when everything is fine (if that still happens) and when you're having issues.  You could also keep a CMD window up doing "PING -t 104.160.131.3" just to see what you get.

(I got this IP address for LoL off the web; I'm not sure it's current.  You'd have to ask LoL support.)

Here are the results of the tracert

Tracing route to 104.160.131.3 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  dsldevice.attlocal.net [192.168.1.254]
  2     1 ms     1 ms     1 ms  162-197-52-1.lightspeed.livnmi.sbcglobal.net [162.197.52.1]
  3     1 ms     1 ms    <1 ms  71.151.199.186
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    11 ms    11 ms    12 ms  32.130.19.227
  7    12 ms    12 ms    11 ms  12.245.40.38
  8    58 ms    58 ms    57 ms  ae1.er02.chi01.riotdirect.net [104.160.143.91]
  9    57 ms    57 ms    57 ms  ae2.er02.lax01.riotdirect.net [104.160.159.186]
 10    57 ms    57 ms    58 ms  ae1.er01.lax01.riotdirect.net [104.160.151.134]
 11    57 ms     *        *     104.160.141.51
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

I also ran a tracert to the ip address used by the Hearthstone North American Server. Results:

Tracing route to 24.105.30.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  dsldevice.attlocal.net [192.168.1.254]
  2     1 ms     1 ms    <1 ms  162-197-52-1.lightspeed.livnmi.sbcglobal.net [162.197.52.1]
  3     1 ms    <1 ms    <1 ms  71.151.199.186
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    14 ms    15 ms    15 ms  32.130.17.75
  8     *       12 ms    12 ms  ggr6.cgcil.ip.att.net [12.122.133.193]
  9    12 ms    12 ms    14 ms  12.246.90.154
 10     *     1720 ms   946 ms  ae1-br02-eqch2.as57976.net [137.221.69.35]
 11    61 ms    61 ms     *     et-0-0-3-br02-eqla1.as57976.net [137.221.65.4]
 12    61 ms    60 ms    61 ms  137.221.68.87
 13    61 ms    61 ms    61 ms  lax-eqla1-ia-bons-02.as57976.net [137.221.66.3]
 14     *       59 ms    59 ms  24.105.30.129