Who can fix this?

[Cubesteak]

Hello,

I'm wondering if anyone call tell me who to bark at in this situation.

I have a DSL line with PacBell/SBC, and I'm having AWFUL throughput to my webhost. Now, given that my upload is capped at 128, awful throughput means I'm seeing even less.

Sometime, when the packet faries smile upon me, I'm blessed with 3K a second upload. Most often though, I'm stuck in 30 BYTES per second hell.

A traceroute gives:

<--
Tracing route to PARCABUL [198.70.62.4]
over a maximum of 30 hops:

1 24 ms 26 ms 27 ms adsl-xxx-xxx-xxx-xxx.xx.xxx.pacbell.net [xxx.xxx.xxx.xxx]
2 24 ms 26 ms 26 ms dist1-vlan50.lsan03.pbi.net [64.161.163.214]
3 190 ms 27 ms 32 ms bb1-g1-0.lsan03.pbi.net [206.13.29.144]
4 24 ms 27 ms 26 ms sl-gw28-ana-13-0.sprintlink.net [144.228.75.161]

5 25 ms 26 ms 25 ms sl-bb24-ana-5-0.sprintlink.net [144.232.1.49]
6 25 ms 27 ms 25 ms sl-bb22-ana-13-0.sprintlink.net [144.232.1.149]

7 27 ms 26 ms 30 ms sprint-gw.la2ca.ip.att.net [192.205.32.185]
8 26 ms 26 ms 26 ms gbr3-p50.la2ca.ip.att.net [12.123.28.130]
9 54 ms 56 ms 53 ms gbr4-p90.sffca.ip.att.net [12.122.2.170]
10 53 ms 53 ms 53 ms gbr2-p100.sffca.ip.att.net [12.122.1.190]
11 52 ms 53 ms 53 ms ar1-p310.sfcca.ip.att.net [12.123.195.65]
12 94 ms 83 ms 78 ms 12.125.80.166
13 * * * Request timed out.
14 154 ms 112 ms 122 ms PARCABUL [198.70.62.4]

Trace complete.
-->

Now, I know that the 13th hop can just be blocking ICMP, or something like that - were it not for the abysmal throughput rate to them, I wouldn't think twice about it. Connections to other hosts, downloads or uploads are just fine (I feel weird calling 128 up, FINE, but... :cry: )

Of course, PacBell tells me that if I can get to the web page, then it isn't their problem. When I tell them that it isn't a web page, that it is an FTP session, they say "We don't support FTP". Yeah, right. Morons. You don't support FTP, thats why your support pages suggest FTPing the latest drivers for my NIC. Frickin' idiots. Cookbook style support sucks..

Anyway, I'm just wondering if it is appropriate to talk to my webhost about it - should they be going to THEIR ISP to try to resolve this? Maybe route across a different hop?

I just don't know if it makes sense to be barking up their tree - of course, if it doesn't get fixed, I'm going to have to vote with my feet, and find a different host. So, it is in their best interest to work with me on it, but...

Any thoughts or suggestions?

Not that you'll need it, but here is the basic config:

Sevearl machines of varying Windows 98 & WinXP
Linksys BEFSR41 router
Efficient Networks Speed Stream DSL Modem

Thanks fer yer help!

Cheers,
Cubesteak

[RobertZ]

Have you run uplaod test?
Your cap may be 128 but what are you actually getting?

The traceroute indicates an all clear to me.
So look at your upload speed else where then talk to the people actually hosting your site.
If they cant resolve it and you can uplaod other places just fine, it is time to move on.

[cyberskye]

:nod: You have decent latency until you hop off att. If you are uploading fine elsewhere, it is your webhosts isp or private network that is hosing you.

[zxc47]

Tracing route to 198.70.62.4 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 17 ms 9 ms 12 ms 10.60.0.1
3 9 ms 9 ms 9 ms CAE-IRM-7507-A-OC-3-600.sc.rr.com [24.31.193.61]

4 27 ms 8 ms 13 ms CAE-IRM-7507-A-OC-3-500.SC.RR.COM [24.31.193.2]

5 14 ms 15 ms 23 ms pop2-cha-P3-1.atdn.net [66.185.149.45]
6 13 ms 28 ms 14 ms bb1-cha-P0-1.atdn.net [66.185.138.80]
7 21 ms 22 ms 23 ms bb1-vie-P10-0.atdn.net [66.185.152.29]
8 22 ms 24 ms 20 ms bb2-vie-P11-0.atdn.net [66.185.152.207]
9 42 ms 43 ms 44 ms bb2-chi-P6-0.atdn.net [66.185.152.214]
10 42 ms 42 ms 45 ms aol-gw.cgcil.ip.att.net [192.205.32.237]
11 45 ms 42 ms 44 ms gbr3-p50.cgcil.ip.att.net [12.123.5.146]
12 84 ms 83 ms 85 ms gbr3-p10.sffca.ip.att.net [12.122.2.153]
13 85 ms 82 ms 86 ms gbr1-p50.sffca.ip.att.net [12.122.1.162]
14 85 ms 84 ms 86 ms ar1-p3110.sfcca.ip.att.net [12.123.195.69]
15 108 ms 166 ms 132 ms 12.125.80.162
16 * * * Request timed out.
17 151 ms 119 ms 118 ms 198.70.62.4

Trace complete.
get you a new host