Streaming & gaming fine, but web browsing painfully slow (packet loss)

Hey,

 

I'm on the TWC 50Mbps package in Concord, NC 28027.

 

Basically the internet is working perfectly fine for things like Netflix, YouTube, and gaming (PS4 and PC). However, web browsing is painfully slow, with some pages taking up to several minutes to load, or simply not loading at all.

 

I've tried changing DNS servers to Google DNS and OpenDNS, it doesn't make a difference. The problem occurs on both my PCs and my Android devices. If I connect my laptop via my tethering to my phone (T-Mobile LTE), all websites load perfectly fine.

 

LinkedIn is a website that is suffering the worst, so I ran traceroutes for both the cable and hotspot connections.

 

Time Warner Cable:

 

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>tracert www.linkedin.com

Tracing route to any-na.www.linkedin.com [2620:109:c002::6cae:a0a]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    19 ms     *       20 ms  2606:a000:0:4::8:65a
  3    17 ms    10 ms    16 ms  2606:a000:0:4::4:ac
  4    19 ms    15 ms    11 ms  2606:a000:0:4::a4
  5     *        *       20 ms  2001:1998:0:4::128
  6    14 ms    15 ms    17 ms  2001:1998::66:109:6:171
  7     *        *        *     Request timed out.
  8     *        *      280 ms  vl-52.car1.Atlanta2.Level3.net [2001:1900:1c:2::
3]
  9    28 ms    33 ms     *     2001:1900:1c::4e
 10     *        *       29 ms  vl-60.edge3.Washington4.Level3.net [2001:1900:15
:5::13]
 11     *        *        *     Request timed out.
 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.

C:\Windows\system32>

T-Mobile LTE hotspot:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>tracert www.linkedin.com

Tracing route to any-na.www.linkedin.com [108.174.10.10]
over a maximum of 30 hops:

  1     7 ms    38 ms     6 ms  192.168.43.1
  2    95 ms    39 ms   123 ms  10.164.150.49
  3    51 ms    62 ms   141 ms  10.168.132.5
  4    45 ms    77 ms    38 ms  10.168.132.11
  5   169 ms    41 ms    32 ms  10.164.167.224
  6   110 ms    38 ms    40 ms  10.164.165.107
  7   132 ms    47 ms    38 ms  128.177.108.241.available.zip.zayo.com [128.177.
108.241]
  8   172 ms    43 ms    52 ms  zayo-ntt.iad10.us.zip.zayo.com [64.125.14.70]
  9   174 ms    78 ms    60 ms  te-0-6-0-14.r04.asbnva02.us.ce.gin.ntt.net [165.
254.191.66]
 10     *        *        *     Request timed out.
 11   138 ms    42 ms    47 ms  108-174-10-10.fwd.linkedin.com [108.174.10.10]

Trace complete.

C:\Windows\system32>

 

Is there anything I can do on my end to solve this, or do I have to endure pain with the tech support guys...?

 

Cheers,

 

Su

3 REPLIES
Expert

Re: Streaming & gaming fine, but web browsing painfully slow (packet loss)

Turn off IPv6...

on all devices...

 

Re: Streaming & gaming fine, but web browsing painfully slow (packet loss)

First, don't use LinkedIn💁

Second, what he said (previous post)

-SPS
Expert

Re: Streaming & gaming fine, but web browsing painfully slow (packet loss)

[ Edited ]

mikeSullivan wrote:

First, don't use LinkedIn💁

Second, what She said (previous post)





 tracert to google.com, another to 209.18.47.61 which is your TWC DNS