Horrible Ping


#1

My ping is horrible.

Im on the East coast in Pennsylvania. I pinged dreamhost.com, mywibsite, and several others in the DHSOTM listed on the panel and they are very slow. Telnet, SSH, FTP are also slow. Control panel is also notoriously slow.

The average ping was 100ms - 124ms.

Its very annoying. I was careful to check for high pings before signing up. I visited some of the webpages and they loaded fairly fast.

Why the drastic change in high latencies?

Is anyone else experiencing this… especially those on the
East Coast???

DH is a good host. I like them and I would hate to leave just because of ping issues. But I would signup with anyone that could provide what DH is providing in the East coast. anyone know of good, reputable, and dependable hosts that provide ssh, large disk space, large bandwidth (atleast 100gb), cgi, perl, php, maybe python, ssi, secure ssl, mysql ect.???

Thanks


#2

Me too - I’m just outside Philadelphia. A trace route reveals the bottlenecks:

[code] 3 10 ms 8 ms 9 ms ge-2-4-ur02.wallingford.pa.panjde.comcast.net [68.86.218.193]
4 9 ms 8 ms 9 ms po70-ar01.wallingford.pa.panjde.comcast.net [68.86.208.190]
5 10 ms 9 ms 9 ms po90-ar01.401nbroadst.pa.panjde.comcast.net [68.86.208.29]
6 13 ms 14 ms 12 ms 68.86.211.14
7 14 ms 13 ms 14 ms 12.119.53.49
8 16 ms 17 ms 15 ms tbr1-p012401.phlpa.ip.att.net [12.123.137.45]
9 15 ms 15 ms 15 ms tbr1-cl8.n54ny.ip.att.net [12.122.2.17]
10 12 ms 13 ms 13 ms ggr1-p360.n54ny.ip.att.net [12.123.1.121]
11 14 ms 14 ms 14 ms so1-1-0-622M.ar1.NYC1.gblx.net [208.51.134.5]
12 84 ms 83 ms 82 ms so0-0-0-622M.ar1.LAX3.gblx.net [67.17.73.38]
13 253 ms 99 ms 97 ms GE1-GX.dreamhost.com [67.17.162.162]
14 92 ms * * dreamhost.com [66.33.201.141]
15 96 ms 97 ms 103 ms dreamhost.com [66.33.201.141]

Trace complete.[/code]Everything moves along nicely until it crosses of from New York to Los Angeles. Then things slow to a crawl. As I said in another thread, the power outages experienced in LA a probably have probably caused secondary issues in the California area. I imagine things will get back to normal in the near future.


Simon Jessey
Keystone Websites | si-blog


#3

[/quote]

East Coast??? <<

Same irratic pings from Minneapolis. Things zip along just fine to Chicago and the next hop to LA grinds nearly to a halt.

As the other poster surmised, I’m sure it’s due to yesterday’s power outage. Hope the routes get straightened out soon.

Dave


#4

Keep in mind folks that yesterdays massive power outage in Califonia (which did effect DH) could be causing other issues. I know DH said they lost some equipment and were working on geting spares in place, but the backbone providers (level3, Global Crossing and such) could have issues as well. That could account for the higher latencies you are seeing.


#5

“As the other poster surmised, I’m sure it’s due to yesterday’s power outage. Hope the routes get straightened out soon.”

Yes, thats what I had in mind too.

What is the average ping for those of you in the East Coast? Does it have a large impact on the functionality of your website? The average ping for most east coast hosters is 40 - 60ms. Being that im a new customer im just curious. Is there anything you could do to decrease latencies on your end in normal circumstances or is it better to just look for hosting on the east coast? I was wondering if anyone knows of East coast hosters that provide such a rich array of features.

Thanks


#6

compare this http://www.untuckedshirts.com/ (someones site on DH)

–> to this http://primeacademics.dreamhosters.com/ (my temporary address before I register my free domain)

the images on undtuckedshirts are more than 50kb Infact one is 184kb. these images loaded fairly fast. Most of my images on my site are less than 20kb with a few exceptions in that some are 80-90kb yet they load very slow.

Could this be due to untuckedshirts.com being on a diferent server or perhaps he is on a dedicated server?

Thanks


#7

Ping times from Minnepolis/St. Paul as of 4:56pm CDT on a T1 circuit:

Ping dreamhost.com (66.33.201.141) …
1 Addr:66.33.201.141, RTT: 89ms, TTL: 54
2 Addr:66.33.201.141, RTT: 90ms, TTL: 54
3 Addr:66.33.201.141, RTT: 90ms, TTL: 54
4 Addr:66.33.201.141, RTT: 89ms, TTL: 54
5 Addr:66.33.201.141, RTT: 89ms, TTL: 54
6 Addr:66.33.201.141, RTT: 89ms, TTL: 54
7 Addr:66.33.201.141, RTT: 83ms, TTL: 54
8 Addr:66.33.201.141, RTT: 91ms, TTL: 54
9 Addr:66.33.201.141, RTT: 88ms, TTL: 54
10 Addr:66.33.201.141, RTT: 93ms, TTL: 54

That’s almost what it was when I decided to move over to DH. So, maybe things are settling down after the outage.

My old host was probably 10ms faster in pings, but overall site speed was better on DH (as the sales / support guy said it would be).

Dave


#8

hmm perhaps for you because youre in a midwest state…

but im in pittsburgh and my ping is 100ms.

its not going down… i suppose thats the normal ping rate…

oh wait i take that back… i pinged another hosting company LA which was hit by the outage and their ping is 80ms.

hmm… any other east coasters still lagging?

…DH is nearing strike three for me…

~regards


#9

From my Seattle home Comcast line:
PING dreamhost.com (66.33.201.141): 56 data bytes
64 bytes from 66.33.201.141: icmp_seq=1 ttl=51 time=52.415 ms
64 bytes from 66.33.201.141: icmp_seq=2 ttl=51 time=50.728 ms
64 bytes from 66.33.201.141: icmp_seq=3 ttl=51 time=50.541 ms
64 bytes from 66.33.201.141: icmp_seq=4 ttl=51 time=54.416 ms
64 bytes from 66.33.201.141: icmp_seq=5 ttl=51 time=50.704 ms
64 bytes from 66.33.201.141: icmp_seq=6 ttl=51 time=51.473 ms
64 bytes from 66.33.201.141: icmp_seq=7 ttl=51 time=52.376 ms
64 bytes from 66.33.201.141: icmp_seq=8 ttl=51 time=47.165 ms
64 bytes from 66.33.201.141: icmp_seq=9 ttl=51 time=57.321 ms
^C
dreamhost.com ping statistics —
10 packets transmitted, 9 packets received, 10% packet loss
round-trip min/avg/max = 47.165/51.904/57.321 ms
Quicksilver:~ user$ ping tank.dreamhost.com
PING tank.dreamhost.com (66.33.208.12): 56 data bytes
64 bytes from 66.33.208.12: icmp_seq=0 ttl=51 time=50.21 ms
64 bytes from 66.33.208.12: icmp_seq=1 ttl=51 time=53.086 ms
64 bytes from 66.33.208.12: icmp_seq=2 ttl=51 time=69.396 ms
64 bytes from 66.33.208.12: icmp_seq=3 ttl=51 time=86.786 ms
64 bytes from 66.33.208.12: icmp_seq=4 ttl=51 time=52.02 ms
64 bytes from 66.33.208.12: icmp_seq=6 ttl=51 time=57.271 ms
64 bytes from 66.33.208.12: icmp_seq=7 ttl=51 time=56.168 ms
64 bytes from 66.33.208.12: icmp_seq=8 ttl=51 time=86.006 ms
64 bytes from 66.33.208.12: icmp_seq=9 ttl=51 time=54.275 ms
64 bytes from 66.33.208.12: icmp_seq=10 ttl=51 time=55.114 ms
64 bytes from 66.33.208.12: icmp_seq=11 ttl=51 time=57.988 ms
^C
tank.dreamhost.com ping statistics —
12 packets transmitted, 11 packets received, 8% packet loss
round-trip min/avg/max = 50.21/61.665/86.786 ms
Quicksilver:~ user$

SSH on tank.dreamhost.com pinging dreamhost.com
PING dreamhost.com (66.33.201.141): 56 data bytes
64 bytes from 66.33.201.141: icmp_seq=0 ttl=63 time=23.6 ms
64 bytes from 66.33.201.141: icmp_seq=1 ttl=63 time=35.4 ms
64 bytes from 66.33.201.141: icmp_seq=2 ttl=63 time=36.0 ms
64 bytes from 66.33.201.141: icmp_seq=3 ttl=63 time=18.4 ms
64 bytes from 66.33.201.141: icmp_seq=4 ttl=63 time=54.5 ms
64 bytes from 66.33.201.141: icmp_seq=5 ttl=63 time=27.3 ms
64 bytes from 66.33.201.141: icmp_seq=6 ttl=63 time=25.2 ms
64 bytes from 66.33.201.141: icmp_seq=7 ttl=63 time=25.2 ms
64 bytes from 66.33.201.141: icmp_seq=8 ttl=63 time=26.9 ms
64 bytes from 66.33.201.141: icmp_seq=9 ttl=63 time=13.3 ms
64 bytes from 66.33.201.141: icmp_seq=10 ttl=63 time=22.3 ms
64 bytes from 66.33.201.141: icmp_seq=11 ttl=63 time=70.6 ms

dreamhost.com ping statistics —
13 packets transmitted, 12 packets received, 7% packet loss
round-trip min/avg/max = 13.3/31.5/70.6 ms


#10

pinging dreamhost.com [66.33.201.141] with 32 bytes

reply from 66.33.201.141: bytes=32 time=97ms TTL=49
reply from 66.33.201.141: bytes=32 time=94ms TTL=49
reply from 66.33.201.141: bytes=32 time=93ms TTL=49
reply from 66.33.201.141: bytes=32 time=92ms TTL=49

ping statistics for 66.33.201.141:
Packets: Sent = 4, Received = 4, Lost = 0 (0% lo
approximate round trip times in milli-seconds:
Minimum = 92ms, Maximum = 97ms, Average = 94ms


pinging tank.dreamhost.com [66.33.201.141] with 32 bytes

reply from 66.33.201.141: bytes=32 time=97ms TTL=49
reply from 66.33.201.141: bytes=32 time=94ms TTL=49
reply from 66.33.201.141: bytes=32 time=93ms TTL=49
reply from 66.33.201.141: bytes=32 time=92ms TTL=49

ping statistics for 66.33.201.141:
Packets: Sent = 4, Received = 4, Lost = 0 (0% lo
approximate round trip times in milli-seconds:
Minimum = 92ms, Maximum = 97ms, Average = 94ms

mysite

Pinging primeacademics.dreamhosters.com [64.111.99.80] with 32 bytes of data:

Reply from 64.111.99.80: bytes=32 time=101ms TTL=49
Reply from 64.111.99.80: bytes=32 time=92ms TTL=49
Reply from 64.111.99.80: bytes=32 time=99ms TTL=49
Reply from 64.111.99.80: bytes=32 time=91ms TTL=49
Reply from 64.111.99.80: bytes=32 time=93ms TTL=49
Reply from 64.111.99.80: bytes=32 time=93ms TTL=49
Reply from 64.111.99.80: bytes=32 time=105ms TTL=49
Reply from 64.111.99.80: bytes=32 time=101ms TTL=49
Reply from 64.111.99.80: bytes=32 time=93ms TTL=49
Reply from 64.111.99.80: bytes=32 time=95ms TTL=49
Reply from 64.111.99.80: bytes=32 time=96ms TTL=49
Reply from 64.111.99.80: bytes=32 time=94ms TTL=49
Reply from 64.111.99.80: bytes=32 time=93ms TTL=49

Ping statistics for 64.111.99.80:
Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 91ms, Maximum = 105ms, Average = 95ms