Charter Spectrum → Re: [Speed Issues] Level3 The Planet

This isn't charter's problem. Send an email to ThePlanet about it.

here is my speed test for 10m/1m to the charter texas speed test
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 0.58Mb/s
running 10s inbound test (server to client) . . . . . . 2.69Mb/s

------ Web100 Detailed Analysis ------
100 Mbps FastEthernet link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 171.01 msec; the Packet size = 1460 Bytes; and
No packet loss was observed.
This connection is network limited 99.99% of the time.
Contact your local network administrator to report a network problem

web100 reports TCP Performance Enhancement Settings are:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [24.158.213.21] but Client says [192.168.0.100]

now this morning i had full 10meg service
so i don't see how this isn't a charter problem

Well, you are a running a speedtest in Texas,.. which is most likely running into these routing issues plaguing you. It isn't Charters equipment that is causing your issues.

Though, as I mentioned before it would be helpful to get a Charter Network Engineer, or to contact the Service where your latency is dropping out, IE: theplanet.com, . While it isn't Charters problem directly, they could help if you could contact the appropriate person. You are having poor performance using their service, and in that it is there problem to provide you with adequate service.

If this was isolated to a handful of websites, then no big deal,.. but if it is the majority of your HSI experience then, well, something needs to be done.

I would recommend trying different speed tests, that are not routed through Texas, if possible, to determine your true speed through the network.

Perhaps www.speedtest.net/index.php might provide some solutions, though you might get routed through the same servers on the way.

well charter says they cant help me if it is outside of their network so i am wondering if any of the troubled spots in this route is on charters network

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 8 ms 9 ms 11 ms 10.98.224.1
3 12 ms 11 ms 9 ms 71-15-32-1.dhcp.slid.la.charter.com [71.15.32.1]

4 10 ms 9 ms 10 ms 71.14.172.1
5 11 ms 12 ms 10 ms nworla1wce1-gige7-1.wcg.net [64.200.57.49]
6 19 ms 20 ms 18 ms hstntx1wcx3-pos9-3-oc48.wcg.net [64.200.210.241]

7 23 ms 24 ms 22 ms dllstx1wcx3-pos14-0-oc192.wcg.net [64.200.210.65
]
8 25 ms 23 ms 23 ms 64.200.249.130
9 24 ms 23 ms 24 ms te-4-2.car2.Dallas1.Level3.net [4.68.110.13]
10 23 ms 25 ms 24 ms ae-23-56.car3.Dallas1.Level3.net [4.68.122.175]

11 306 ms 307 ms 310 ms att-level3-oc48.Dallas1.Level3.net [4.68.127.106
]
12 342 ms 391 ms 339 ms tbr2-p010501.dlstx.ip.att.net [12.123.16.14]
13 330 ms 332 ms 329 ms tbr1-cl6.sl9mo.ip.att.net [12.122.10.89]
14 336 ms 338 ms 356 ms tbr1-cl4.wswdc.ip.att.net [12.122.10.29]
15 353 ms 349 ms 351 ms tbr2-cl27.wswdc.ip.att.net [12.122.9.150]
16 366 ms 348 ms 343 ms tbr2-cl15.n54ny.ip.att.net [12.122.10.53]
17 348 ms 342 ms 335 ms gar1-p370.nwrnj.ip.att.net [12.123.0.157]
18 315 ms 321 ms 325 ms att-gige.esd1.nwr.nac.net [12.119.140.26]
19 341 ms 350 ms 342 ms 3.ge-3-0-0.gbr2.nwr.nac.net [209.123.11.189]
20 344 ms 344 ms 506 ms 0.so-0-3-0.gbr1.oct.nac.net [209.123.11.233]
21 364 ms 374 ms 378 ms www.dslreports.com [209.123.109.175]

not really, no. Charter can assist you about 2 hops off the network. (line 6) And that is only if crap is timing out and failing. the slow times are pretty much uncontrollable, esp that far out.

What are the results of a 100 or so continuous ping of dslreports?

Pinging dslreports.com [209.123.109.175] with 32 bytes of

Reply from 209.123.109.175: bytes=32 time=307ms TTL=48
Reply from 209.123.109.175: bytes=32 time=303ms TTL=48
Reply from 209.123.109.175: bytes=32 time=306ms TTL=48
Reply from 209.123.109.175: bytes=32 time=302ms TTL=48
Reply from 209.123.109.175: bytes=32 time=319ms TTL=48
Reply from 209.123.109.175: bytes=32 time=322ms TTL=48
Reply from 209.123.109.175: bytes=32 time=435ms TTL=48
Reply from 209.123.109.175: bytes=32 time=313ms TTL=48
Reply from 209.123.109.175: bytes=32 time=299ms TTL=48
Reply from 209.123.109.175: bytes=32 time=289ms TTL=48
Reply from 209.123.109.175: bytes=32 time=292ms TTL=48
Reply from 209.123.109.175: bytes=32 time=310ms TTL=48
Reply from 209.123.109.175: bytes=32 time=337ms TTL=48
Reply from 209.123.109.175: bytes=32 time=351ms TTL=48
Reply from 209.123.109.175: bytes=32 time=348ms TTL=48
Reply from 209.123.109.175: bytes=32 time=333ms TTL=48
Reply from 209.123.109.175: bytes=32 time=323ms TTL=48
Reply from 209.123.109.175: bytes=32 time=333ms TTL=48
Reply from 209.123.109.175: bytes=32 time=326ms TTL=48
Reply from 209.123.109.175: bytes=32 time=337ms TTL=48
Reply from 209.123.109.175: bytes=32 time=332ms TTL=48
Reply from 209.123.109.175: bytes=32 time=329ms TTL=48
Reply from 209.123.109.175: bytes=32 time=332ms TTL=48
Reply from 209.123.109.175: bytes=32 time=322ms TTL=48
Reply from 209.123.109.175: bytes=32 time=317ms TTL=48
Reply from 209.123.109.175: bytes=32 time=317ms TTL=48
Reply from 209.123.109.175: bytes=32 time=318ms TTL=48
Reply from 209.123.109.175: bytes=32 time=326ms TTL=48
Reply from 209.123.109.175: bytes=32 time=311ms TTL=48
Reply from 209.123.109.175: bytes=32 time=307ms TTL=48
Reply from 209.123.109.175: bytes=32 time=313ms TTL=48
Reply from 209.123.109.175: bytes=32 time=324ms TTL=48
Reply from 209.123.109.175: bytes=32 time=315ms TTL=48
Reply from 209.123.109.175: bytes=32 time=330ms TTL=48
Reply from 209.123.109.175: bytes=32 time=330ms TTL=48
Reply from 209.123.109.175: bytes=32 time=332ms TTL=48
Reply from 209.123.109.175: bytes=32 time=331ms TTL=48
Reply from 209.123.109.175: bytes=32 time=326ms TTL=48
Reply from 209.123.109.175: bytes=32 time=335ms TTL=48
Reply from 209.123.109.175: bytes=32 time=328ms TTL=48
Reply from 209.123.109.175: bytes=32 time=330ms TTL=48
Reply from 209.123.109.175: bytes=32 time=318ms TTL=48
Reply from 209.123.109.175: bytes=32 time=319ms TTL=48
Reply from 209.123.109.175: bytes=32 time=311ms TTL=48
Reply from 209.123.109.175: bytes=32 time=310ms TTL=48
Reply from 209.123.109.175: bytes=32 time=303ms TTL=48
Reply from 209.123.109.175: bytes=32 time=306ms TTL=48
Reply from 209.123.109.175: bytes=32 time=311ms TTL=48
Reply from 209.123.109.175: bytes=32 time=314ms TTL=48
Reply from 209.123.109.175: bytes=32 time=310ms TTL=48
Reply from 209.123.109.175: bytes=32 time=319ms TTL=48
Reply from 209.123.109.175: bytes=32 time=319ms TTL=48
Reply from 209.123.109.175: bytes=32 time=345ms TTL=48
Reply from 209.123.109.175: bytes=32 time=340ms TTL=48
Reply from 209.123.109.175: bytes=32 time=341ms TTL=48
Reply from 209.123.109.175: bytes=32 time=348ms TTL=48
Reply from 209.123.109.175: bytes=32 time=347ms TTL=48