US Cable Support → Earthlink Cable > [TW] Spotty service and Destination net unreachable

[TW] Spotty service and Destination net unreachable

Is anyone else experiencing awful slowness and some totally unreachable websites? As an example, we cannot reach »www.pittsburghzoo.org on our Earthlink/Time Warner cable but we can over Verizon's 4G on our phones. This is just one example of a working website that returns a "Destination net unreachable" tracert.

I've also been experiencing some sort of packet loss that causes websites to partially load or not at all. Once refreshing a few times the same site will load, albeit slower than it should. Chrome reports "The connection to [insert site] was interrupted." This is on multiple machines on our network.

Just to be sure it wasn't our internal router, we took the router out of the picture and hooked up a laptop to the modem. We had internet service, but still getting these Destination Unreachable problems and slow speeds.

Have you tried changing DNS?

Yeah. Been through Open DNS (which was the original config) then to Earthlink, now to Google. The problem follows the IP as well. It's very bizarre.

So here's something really interesting. Right now, the Pittsburgh Zoo site is the only one I have stumbled on that I'm still not able to access. So I decided to look more closely at the Tracert data. After it leaves the Time Warner system it goes to an African server - literally over on the continent of Africa. No other tracerts I run, leave the continent. (see hop 14 and later below):

Tracing route to pittsburghzoo.org [198.144.36.150]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 7 ms 7 ms 8 ms 24.164.116.106
4 7 ms 7 ms 7 ms 24.164.102.224
5 7 ms 8 ms 7 ms 24.164.99.229
6 9 ms 7 ms 8 ms 24.164.111.235
7 8 ms 11 ms 9 ms 24.164.111.237
8 9 ms 9 ms 9 ms 24.164.112.77
9 11 ms 11 ms 11 ms 24.164.112.72
10 17 ms 15 ms 15 ms 65.29.1.28
11 25 ms 31 ms 27 ms 107.14.19.60
12 24 ms 27 ms 31 ms 66.109.6.20
13 24 ms 23 ms 23 ms 107.14.17.192
14 61 ms 56 ms 57 ms 154.54.11.145
15 72 ms 66 ms 65 ms 154.54.5.9
16 270 ms 208 ms 214 ms 154.54.89.90
17 228 ms 207 ms 214 ms 154.54.45.133
18 181 ms 207 ms 207 ms 154.54.83.170
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * 38.104.120.170 reports: Destination net unreachable.

Here's the whois on that block of African IPs:
»www.whois.com/whois/154.54.5.9

Here's an example of an IP that *is* working:
Tracing route to google.com [74.125.225.40]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 7 ms 8 ms 24.164.116.110
4 8 ms 7 ms 9 ms 24.164.102.224
5 8 ms 7 ms 7 ms 24.164.99.229
6 7 ms 7 ms 23 ms 24.164.111.235
7 10 ms 9 ms 9 ms 24.164.111.237
8 9 ms 9 ms 9 ms 24.164.112.77
9 12 ms 11 ms 11 ms 24.164.112.72
10 17 ms 16 ms 15 ms 65.29.1.28
11 25 ms 27 ms 23 ms 107.14.19.60
12 28 ms 27 ms 31 ms 66.109.6.20
13 23 ms 24 ms 23 ms 66.109.1.66
14 43 ms 28 ms 24 ms 74.125.48.109
15 30 ms 23 ms 25 ms 209.85.254.122
16 25 ms 26 ms 23 ms 209.85.250.28
17 31 ms 23 ms 25 ms 74.125.225.40

Trace complete.

You can see that it takes much fewer hops to reach Google which I assume is because Google has a lot of servers. In any case, other websites also do not leave the continent.

So my question is who's problem is this? It is Time Warner sending some bad redirect somehow?