A little help please!

[jimnyc]

One of the servers I host websites with is very slow for me. Although I have tested from various servers around the country, support still states that the issue is on my end. I would appreciate it if anyone could "ping" the IP address below and paste their results here.

The IP address is 69.73.183.192

To perform the test, do the following:


1- Open a DOS prompt
2- Type in "ping 69.73.183.192" without the quotes
3- Once it's complete, click on the "c:\" icon in the upper left hand corner of your screen. A dropdown list will come up - choose "Edit" then "Mark"
4- Now highlight what you want to copy and leave it highlighted
5- Go back to the dropdown list and choose "Edit" then "Copy"
6- Paste results here

If that is too complicated, just write down the "minimum, maximum and average" results which is the last line returned.

Thanks!

[Kathianne]

One of the servers I host websites with is very slow for me. Although I have tested from various servers around the country, support still states that the issue is on my end. I would appreciate it if anyone could "ping" the IP address below and paste their results here.

The IP address is 69.73.183.192

To perform the test, do the following:



If that is too complicated, just write down the "minimum, maximum and average" results which is the last line returned.

Thanks!I'd try, but don't know how to get a dos prompt on a mac.

[Immanuel]

One of the servers I host websites with is very slow for me. Although I have tested from various servers around the country, support still states that the issue is on my end. I would appreciate it if anyone could "ping" the IP address below and paste their results here.

The IP address is 69.73.183.192

To perform the test, do the following:



If that is too complicated, just write down the "minimum, maximum and average" results which is the last line returned.

Thanks!


Pinging 69.73.183.192 with 32 bytes of data:

Reply from 69.73.183.192: bytes=32 time=201ms TTL=54
Reply from 69.73.183.192: bytes=32 time=209ms TTL=54
Reply from 69.73.183.192: bytes=32 time=203ms TTL=54
Reply from 69.73.183.192: bytes=32 time=198ms TTL=54

Ping statistics for 69.73.183.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 198ms, Maximum = 209ms, Average = 202ms


Hope that helps.

Not sure what it all means speed-wise.

Immie

[jimnyc]

I'd try, but don't know how to get a dos prompt on a mac.

Try reading this, maybe that'll help? http://www.vcn.com/knowledgebase/article.php?id=081


Hope that helps.

Not sure what it all means speed-wise.

Immie

It means you are getting the same slow results to the server as I am. Thanks!

[Kathianne]

Try reading this, maybe that'll help? http://www.vcn.com/knowledgebase/article.php?id=081



It means you are getting the same slow results to the server as I am. Thanks!

Here's what I got, hope it helps:

Ping has started ...

PING 69.73.183.192 (69.73.183.192): 56 data bytes
64 bytes from 69.73.183.192: icmp_seq=0 ttl=51 time=226.794 ms
64 bytes from 69.73.183.192: icmp_seq=1 ttl=51 time=222.423 ms
64 bytes from 69.73.183.192: icmp_seq=3 ttl=51 time=224.208 ms
64 bytes from 69.73.183.192: icmp_seq=4 ttl=51 time=233.049 ms
64 bytes from 69.73.183.192: icmp_seq=5 ttl=51 time=222.407 ms
64 bytes from 69.73.183.192: icmp_seq=6 ttl=51 time=229.415 ms
64 bytes from 69.73.183.192: icmp_seq=7 ttl=51 time=220.843 ms
64 bytes from 69.73.183.192: icmp_seq=8 ttl=51 time=227.959 ms
64 bytes from 69.73.183.192: icmp_seq=9 ttl=51 time=218.932 ms

--- 69.73.183.192 ping statistics ---
10 packets transmitted, 9 packets received, 10% packet loss
round-trip min/avg/max/stddev = 218.932/225.114/233.049/4.272 ms

[jimnyc]

Yep, that helps! You are also seeing ping times upwards of 200ms. If you were to perform the same test to this site it would be between 30-50ms.

[Mr. P]

Pinging 69.73.183.192 with 32 bytes of data:

Reply from 69.73.183.192: bytes=32 time=181ms TTL=51
Reply from 69.73.183.192: bytes=32 time=183ms TTL=51
Reply from 69.73.183.192: bytes=32 time=180ms TTL=51
Reply from 69.73.183.192: bytes=32 time=186ms TTL=51

Ping statistics for 69.73.183.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 180ms, Maximum = 186ms, Average = 182ms

[jimnyc]

Thank you, Mr. P! You're seeing the high latency too. I'm just recording the results from people from various points in the country to further prove my point to my host.

[Dilloduck]

Every time I try to run it it closes before it finishes

[jimnyc]

Every time I try to run it it closes before it finishes

You would need to open the dos prompt and run it. Sounds like you're running it from the "run" prompt, which will open a window and run it, then close it upon completion.

At any rate, it appears the problem was just resolved moments ago as my times have returned to normal. Let's hope it stays that way!

[Dilloduck]

You would need to open the dos prompt and run it. Sounds like you're running it from the "run" prompt, which will open a window and run it, then close it upon completion.

At any rate, it appears the problem was just resolved moments ago as my times have returned to normal. Let's hope it stays that way!

You are accurate as usual--I'll try to stay out of the "technical assistance" department from here on out . :laugh2:

[Dilloduck]

You are accurate as usual--I'll try to stay out of the "technical assistance" department from here on out . :laugh2:


Pinging 69.73.183.192 with 32 bytes of data:

Reply from 69.73.183.192: bytes=32 time=42ms TTL=51
Reply from 69.73.183.192: bytes=32 time=41ms TTL=51
Reply from 69.73.183.192: bytes=32 time=42ms TTL=51
Reply from 69.73.183.192: bytes=32 time=40ms TTL=51

Ping statistics for 69.73.183.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% l
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 42ms, Average = 41ms
Im bad uh huh :dance:

[jimnyc]

You are accurate as usual--I'll try to stay out of the "technical assistance" department from here on out . :laugh2:

Nope, you did it correctly the 2nd time around!

It's frustrating for me. I've been doing computers/networking for well over 15 years now. When they say "the problem is on your end" - even though I give them all the proof in the world, there's only so much more I can do! I started this thread, one on their own forums, and one on a technical site. All 3 places reported back with the slowdown. I also gave them graphs and reports from places all over the country.

The final one that had them see it my way is when I had them run the reports to that server, then run it to this server, and compare the results. The servers are in the same datacenter but were giving drastically different results. Shortly thereafter the problem was fixed.

90% of the time when this happens it's because of another site that is hosted on the same server. If they suddenly have a HUGE traffic spike, or a script that is failing, or they're sending out 500,000 emails - then everyone on the server suffers as a result. I understand they don't want to immediately terminate/suspend another account, as we are all paying customers, but it's not fair that we all suffer. If someone has that much traffic, or needs that many resources for their site to operate, they should upgrade to a dedicated server.

Okay, rant over.

[Immanuel]

Thank you, Mr. P! You're seeing the high latency too. I'm just recording the results from people from various points in the country to further prove my point to my host.

I don't think I have my location anywhere on site. You may have seen it before, but just in case you have not, I'm near Tampa, FL. If that helps at all. :dunno: What is a millisecond or two anyway. :)

Immie

[Mr. P]

Just did this one......


Pinging 69.73.183.192 with 32 bytes of data:

Reply from 69.73.183.192: bytes=32 time=11ms TTL=51
Reply from 69.73.183.192: bytes=32 time=11ms TTL=51
Reply from 69.73.183.192: bytes=32 time=11ms TTL=51
Reply from 69.73.183.192: bytes=32 time=18ms TTL=51

Ping statistics for 69.73.183.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 18ms, Average = 12ms

[5stringJeff]

Pinging 69.73.183.192 with 32 bytes of data:

Reply from 69.73.183.192: bytes=32 time=60ms TTL=48
Reply from 69.73.183.192: bytes=32 time=50ms TTL=48
Reply from 69.73.183.192: bytes=32 time=56ms TTL=48
Reply from 69.73.183.192: bytes=32 time=55ms TTL=48

Ping statistics for 69.73.183.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 60ms, Average = 55ms

[5stringJeff]

Jim, it seems that the ping times very suddenly got quicker. So maybe the problem is intermittent?

[KarlMarx]

Pinging 69.73.183.192 with 32 bytes of data:
Reply from 69.73.183.192: bytes=32 time=49ms TTL=49
Reply from 69.73.183.192: bytes=32 time=45ms TTL=49
Reply from 69.73.183.192: bytes=32 time=46ms TTL=49
Reply from 69.73.183.192: bytes=32 time=47ms TTL=49
Ping statistics for 69.73.183.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 49ms, Average = 46ms