Spice300
Premium
join:2006-01-10
edit:
May 13th, @06:02PM
| reply to moonpieboy
Re: Parents Experencing Speed Issues on Wild Blue
Your trace route shows that it was run from MIT to your parents computer. The IP at hop 12 in your second trace route:
wildblue-msp.customer.alter.net (157.130.115.230) 40.280 ms 40.533 ms 40.440 ms
does not look like it is related to the Laredo gateway. Although I am not confident since I do not recall seeing a trace route to the gateway, I think your parents are using the the satellite Wildblue-1, the Duluth gateway and beam 130 or 131. Does "MSP3.ALTER.NET" mean the server is located in Mississippi? I thought the Duluth gateway was located in Minnesota. Do you know when your parents got service from WB? If it was before April 2007, then they are probably using the satellite Anik-F2, otherwise WB-1 is the best guess.
The latencies on hop 19 of 1600 ms and 2368 ms are higher than average on WB but are within reasonable range. Remember the signal must travel more than 22,000 miles to or from the satellite 4 times for a round trip. Add in the slowness of the gateway and one gets our lousy latency.
We need your parents to run upload and download speed tests at Test My Network and post the results here before we can determine if their speeds are atypically slow.
The proxy has been causing slow download speeds for some of us since December 2007. If they stop using the proxy, the download speed increases to normal.
--
Value Pack, beam 31, Riverside gateway |
|
grohgreg
Dunno. Ask The Chief
join:2001-07-05
Dawson Springs, KY
| said by Spice300  :Does "MSP3.ALTER.NET" mean the server is located in Mississippi? MSP3 is quite likely Minneapolis-St Paul
//greg//
--
HN7000S/74cm/1w/ProPlus - G16/1250H/Germantown - NAT 66.82.187.152/Gateway 66.82.25.10/DNS 66.82.4.12 and 66.82.4.8 - Firefox 3 - AVG+Firewall v7.5 |
|
Siryak
join:2005-11-26 | I am beginning to think it is not just him. I am here on Beam 40 and my speeds are still about what it is showing above and I'm on the Pro-Pack. I just tested at 6:00 AM and they are still below 1mb. |
|
Island Jeff
join:2005-07-18
 ·TDS
 ·WildBlue
| Are all those WB hops failing to respond to ICMP for you as well? That does look very odd compared to mine on the old bird where they all respond.
9 208.175.175.34 (208.175.175.34) 2.139 ms 2.370 ms 2.244 ms
10 dal-core-01.inet.qwest.net (205.171.25.13) 2.103 ms 2.248 ms 2.236 ms
11 ewr-edge-04.inet.qwest.net (205.171.17.50) 41.695 ms 41.871 ms 42.085 ms
12 63.227.232.222 (63.227.232.222) 96.108 ms 96.023 ms 95.945 ms
13 10.242.110.1 (10.242.110.1) 96.198 ms 96.190 ms 96.114 ms
14 10.242.100.1 (10.242.100.1) 96.140 ms 96.100 ms 96.416 ms
15 10.242.30.27 (10.242.30.27) 96.432 ms 96.482 ms 96.196 ms
16 10.242.30.1 (10.242.30.1) 96.370 ms 97.692 ms 96.820 ms
17 10.242.20.2 (10.242.20.2) 96.543 ms 97.088 ms 97.007 ms
18 67-54-18y-xx.cust.wildblue.net (67.54.18y.xx) 1257.470 ms 1257.292 ms 1257.153 ms
again
8 er1-te-2-1.dallasequinix.savvis.net (204.70.204.145) 1.981 ms 2.293 ms 2.659 ms
9 208.175.175.34 (208.175.175.34) 1.677 ms 2.541 ms 2.687 ms
10 dal-core-01.inet.qwest.net (205.171.25.13) 2.948 ms 2.985 ms 2.831 ms
11 ewr-edge-04.inet.qwest.net (205.171.17.50) 41.979 ms 41.422 ms 41.546 ms
12 63.227.232.222 (63.227.232.222) 96.009 ms 96.007 ms 95.903 ms
13 10.242.110.1 (10.242.110.1) 95.855 ms 96.084 ms 96.223 ms
14 10.242.100.1 (10.242.100.1) 96.181 ms 96.103 ms 96.121 ms
15 10.242.30.27 (10.242.30.27) 95.852 ms 96.013 ms 95.979 ms
16 10.242.30.1 (10.242.30.1) 96.386 ms 96.345 ms 96.273 ms
17 10.242.20.2 (10.242.20.2) 96.831 ms 97.491 ms 96.632 ms
18 67-54-18y-xx.cust.wildblue.net (67.54.18y.xx) 1288.285 ms 1868.613 ms 1868.436 ms
If ICMP is set to the lowest priority, it makes me wonder if they're doing some network reconfiguration there or some other maintenance that has things up in the air or very overloaded.
--
Very happy TDS DSL user | Wildblue in Lake Michigan |
|
