Bad tracert to Webair, what's up?

[Socks]

I'm trying to review this POV Porn site, and was just writing the owner to complain about the download speeds.. I thought I should attach a tracert so they can look it up, and I saw it was webair! Surprised really, I'm in Toronto, they host in NYC with you... 50k/s to max 85k/s over hours of downloading.. I have an 18mbit connection, fastest I can download is around 2,100k/s.

Seems extra weird because the pings aren't timing out? Doubt it's even a webair problem, no drama, just wanna know what the fuck is uppppppp

Tracing route to www.povporn.com [67.55.89.4]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 8 ms 8 ms 8 ms *.*.*.*
3 7 ms 7 ms 9 ms vl-201.gw03.grnsbr.phub.net.cable.rogers.com [66
.185.91.113]
4 22 ms 7 ms 9 ms gi-1-1-0.gw01.grnsbr.phub.net.cable.rogers.com [
66.185.81.49]
5 9 ms 13 ms 9 ms so-4-2-2.gw02.wlfdle.phub.net.cable.rogers.com [
66.185.81.42]
6 10 ms 9 ms 9 ms so-1-0-0.gw02.mtnk.phub.net.cable.rogers.com [66
.185.80.42]
7 31 ms 29 ms 27 ms pos-2-0.igw01.ny8th.phub.net.cable.rogers.com [6
6.185.81.102]
8 29 ms 27 ms 27 ms es0.nyc4.webair.net [198.32.118.59]
9 27 ms 27 ms 27 ms csa080.nyc.webair.net [209.200.31.85]
10 46 ms 45 ms 46 ms 67.55.89.4

Trace complete.

[TidalWave]

looks fine to me, the owner of that site may have an overloaded server or is maxing out his uplink on his server

[DateDoc]

seems ok here

traceroute to povporn.com (67.55.89.4), 64 hops max, 40 byte packets
1 0.536 ms 0.286 ms 0.234 ms
2 7.482 ms 19.009 ms 6.352 ms
3 66-214-102-5.static.reno.nv.charter.com (66.214.102.5) 18.226 ms 15.505 ms 6.268 ms
4 66-214-102-82.static.reno.nv.charter.com (66.214.102.82) 10.464 ms 7.806 ms 9.884 ms
5 so-9-1.car1.SanFrancisco1.Level3.net (4.78.240.33) 12.585 ms 10.724 ms 11.925 ms
6 ae-2-4.bar1.SanFrancisco1.Level3.net (4.69.133.150) 39.135 ms 11.166 ms 12.677 ms
7 ae-0-11.bar2.SanFrancisco1.Level3.net (4.69.140.146) 63.855 ms 22.594 ms 25.148 ms
8 ae-6-6.ebr2.SanJose1.Level3.net (4.69.140.154) 13.846 ms 24.524 ms 18.262 ms
9 ae-62-62.csw1.SanJose1.Level3.net (4.69.134.210) 23.967 ms 22.857 ms 17.001 ms
10 ae-1-69.edge1.SanJose3.Level3.net (4.68.18.16) 14.199 ms 18.020 ms 15.026 ms
11 4.68.111.162 (4.68.111.162) 192.324 ms 76.133 ms 20.301 ms
12 64.209.97.54 (64.209.97.54) 90.443 ms 89.169 ms 87.445 ms
13 csa080.nyc.webair.net (209.200.31.85) 91.074 ms 88.647 ms 86.306 ms
14 67.55.89.4 (67.55.89.4) 89.646 ms 86.271 ms 88.258 ms

[Socks]

Yeah it does seem strange.. 50k/s is pretty brutal to NYC at 1am though! Maybe they don't have burstable

[Iron Fist]

Good luck with that!

[Hotrow]

The whole thing is down now! Webair.com, the control panel, and a bunch of sites. Shit!

[Alky]

i don't really see anything wrong with the initial tracert unless i overlooked something.

50-80k/sec isn't THAT bad, and it could be any number of reasons, not just webair.

[GigoloShawn]

There's nothing wrong with your traceroute; unless your next hop denies ICMP, you may consider rebooting your modem, though.

[sumphatpimp]

just because you can type "tracert" at the command line, doesn't mean you know what to do with the results.
you have a lot of reading to do.

[brandonstills]

It's not a problem with the server it's webair's bandwidth. Their bandwidth sucks. I had a server briefly with them but canceled it right away when I was only able to upload and download at pathetic speeds.

[Net Money]

Originally Posted by brandonstills

It's not a problem with the server it's webair's bandwidth. Their bandwidth sucks. I had a server briefly with them but canceled it right away when I was only able to upload and download at pathetic speeds.

Many people have said that same thing.???

[Wiredoctor]

Originally Posted by brandonstills

It's not a problem with the server it's webair's bandwidth. Their bandwidth sucks. I had a server briefly with them but canceled it right away when I was only able to upload and download at pathetic speeds.

Very Interresting theory.

[Brad Mitchell]

Couple of different things, folks..

First of all, 9x out of 10 it's the ISP because you are inherently oversubscribed somewhere between your street corner and the first real hop out on your ISPs network.

Second of all, traces in are mostly useless. You could have a 5ms trace or a 100ms trace but at the same time could open up a 100k connection on the 5ms trace or a 1000k connection on the 100ms trace. Trace routes are the lowest priority packet type in terms of how and when routers respond to those requests. Traces are really only useful when identifying a total loss in connectivity or severe packet loss.

Another more likely scenario is that its a problem with that server, perhaps its overloaded, rotating log files, having some other error... If the trace was done after 8pm EST it's absolutely not a peak time for surfing (like 11-2 EST or 4-7EST)

Lastly, Webair like every other large host is in the business of selling bandwidth. In as much as there might be some ways to "save money" buying wholesale bandwidth the larger motivation is to have good connectivity so that your clients get as much throughput as possible.

Webair, just like my company or any other reputable host, makes more money by selling as much bandwidth as humanly possible which means there is an inherent motivation to have ideal performance versus sub-par network performance for small savings.

Cheers,

Brad