Jump to content
MDDHosting Forums

Slow Pings any reason why?


Recommended Posts

Hi,

 

After the DDoS its been around 24 hours, yet the ping times seem to be a lot compared to before.

 

Earlier it was in the range of around 400-500ms but post the downtime it has risen to around 700ms

 

http://www.pingdom.com/reports/hgs5b5n9hkb1/check_overview/?name=Fresco

 

Any reason why?

 

Also is there any reason why Fresco has much higher ping time compared to other servers of MDD?

Link to comment
Share on other sites

1. You shouldn't worry about what Pingdom gets for pings, you should worry about what *you* get for pings.

2. They're literally in the exact same cabinet, connected to the exact same switch so the PINGS are the same, it's the response time that can differ.

3. If you feel your site is slow, just open a ticket and we'll be happy to shift you to Gemini.

 

C:\>ping fresco.supportedns.com

Pinging fresco.supportedns.com [173.248.191.250] with 32 bytes of data:
Reply from 173.248.191.250: bytes=32 time=41ms TTL=54
Reply from 173.248.191.250: bytes=32 time=44ms TTL=54
Reply from 173.248.191.250: bytes=32 time=46ms TTL=54
Reply from 173.248.191.250: bytes=32 time=57ms TTL=54

Ping statistics for 173.248.191.250:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 41ms, Maximum = 57ms, Average = 47ms

C:\>ping gemini.supportedns.com

Pinging gemini.supportedns.com [173.248.191.128] with 32 bytes of data:
Reply from 173.248.191.128: bytes=32 time=42ms TTL=54
Reply from 173.248.191.128: bytes=32 time=41ms TTL=54
Reply from 173.248.191.128: bytes=32 time=46ms TTL=54
Reply from 173.248.191.128: bytes=32 time=40ms TTL=54

Ping statistics for 173.248.191.128:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 40ms, Maximum = 46ms, Average = 42ms

C:\>ping echo.supportedns.com

Pinging echo.supportedns.com [173.248.187.2] with 32 bytes of data:
Reply from 173.248.187.2: bytes=32 time=41ms TTL=54
Reply from 173.248.187.2: bytes=32 time=40ms TTL=54
Reply from 173.248.187.2: bytes=32 time=44ms TTL=54
Reply from 173.248.187.2: bytes=32 time=42ms TTL=54

Ping statistics for 173.248.187.2:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 40ms, Maximum = 44ms, Average = 41ms

Link to comment
Share on other sites

I just pinged all three, including my vps, and was surprised to see the ping times here from the west coast just a few ms higher than yours (averaging about 50ms on all four servers). I'm 1,000 miles away from the data center, about the same distance as Indianapolis, I guess. Since a blink of an eye takes 400ms, 50ms is pretty fast.

 

A tracert shows I'm routed through Roadrunner's servers to Los Angeles, then San Jose on Level3, then into Denver, so its a pretty direct route.

Link to comment
Share on other sites

I just pinged all three, including my vps, and was surprised to see the ping times here from the west coast just a few ms higher than yours (averaging about 50ms on all four servers). I'm 1,000 miles away from the data center, about the same distance as Indianapolis, I guess. Since a blink of an eye takes 400ms, 50ms is pretty fast.

 

A tracert shows I'm routed through Roadrunner's servers to Los Angeles, then San Jose on Level3, then into Denver, so its a pretty direct route.

Yeah, we have no control over your forward route... If memory serves me (I could be wrong) you're on a VPS so if you want, log into it and ping your home IP :) If you're not on a VPS I can do it for you if you open a ticket and ask for me :)
Link to comment
Share on other sites

Yeah, we have no control over your forward route... If memory serves me (I could be wrong) you're on a VPS so if you want, log into it and ping your home IP :) If you're not on a VPS I can do it for you if you open a ticket and ask for me :)

 

I am on a VPS. I had not thought of checking the route from the server to me. Ping shows the same average of about 51ms, and the tracert looks to be the reverse routing of my forward route (home IP modified because I'm paranoid):

 

traceroute to 76.169.*.* (76.169.*.*), 30 hops max, 40 byte packets
1  173.248.191.242 (173.248.191.242)  0.062 ms  0.084 ms  0.053 ms
2  vlan139.car1.Denver1.Level3.net (4.53.12.245)  0.481 ms  0.514 ms  0.558 ms
3  vlan51.ebr1.Denver1.Level3.net (4.69.147.94)  0.340 ms  0.338 ms  0.463 ms
4  ae-3-3.ebr2.SanJose1.Level3.net (4.69.132.57)  25.484 ms  25.522 ms  25.512 ms
5  ae-82-82.csw3.SanJose1.Level3.net (4.69.153.26)  25.677 ms  25.689 ms  25.663 ms
6  ae-3-80.edge1.SanJose3.Level3.net (4.69.152.144)  26.020 ms  26.040 ms  26.039 ms
7  ROADRUNNER.edge1.SanJose3.Level3.net (4.53.208.34)  25.932 ms  25.909 ms  25.886 ms
8  ae-1-0.cr0.sjc10.tbone.rr.com (66.109.6.140)  25.686 ms  25.655 ms  25.639 ms
9  ae-4-0.cr0.lax00.tbone.rr.com (66.109.6.7)  35.046 ms  34.981 ms  35.102 ms
10  66.109.6.213 (66.109.6.213)  36.562 ms  41.165 ms  41.099 ms
11  ae1.vnnyca2-rtr1.socal.rr.com (66.75.147.2)  39.773 ms  47.141 ms  47.103 ms
12  lag4.oxnrca1-rtr1.socal.rr.com (66.75.147.31)  42.335 ms  42.387 ms  42.409 ms
13  ge17-0-oxnrca1-ars2.socal.rr.com (76.169.20.30)  4279.079 ms  4206.884 ms  4210.857 ms
14  cpe-76-169-217-09.socal.res.rr.com (76.169.*.*)  49.083 ms  53.288 ms  53.304 ms

Link to comment
Share on other sites

Thank you for the detailed description and option to shift to gemini. From my end the average ping on fresco comes to around 360-450ms while that on gemini comes to between 350-420. So I dont see much of a difference from my end. But most of my clients / users accessing the site are from US so if I see the pingdom pings there is a drastic difference. I think I will wait and watch before taking a call.
Link to comment
Share on other sites

Thank you for the detailed description and option to shift to gemini. From my end the average ping on fresco comes to around 360-450ms while that on gemini comes to between 350-420. So I dont see much of a difference from my end. But most of my clients / users accessing the site are from US so if I see the pingdom pings there is a drastic difference. I think I will wait and watch before taking a call.

I'll be happy to show you pings from all around the country to any of the servers if you wish, I'll just have to get with people in different parts of the country and ask them to ping them and then ask for their location as well.

 

I'll do this over the next few days and post it up :)

Link to comment
Share on other sites

Los Angeles, CA:

PING echo.supportedns.com (173.248.187.2): 56 data bytes
64 bytes from 173.248.187.2: icmp_seq=0 ttl=57 time=40.701 ms
64 bytes from 173.248.187.2: icmp_seq=1 ttl=57 time=42.791 ms
64 bytes from 173.248.187.2: icmp_seq=2 ttl=57 time=41.743 ms
64 bytes from 173.248.187.2: icmp_seq=3 ttl=57 time=40.182 ms
64 bytes from 173.248.187.2: icmp_seq=4 ttl=57 time=40.655 ms

--- echo.supportedns.com ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 40.182/41.214/42.791/0.939 ms

PING gemini.supportedns.com (173.248.191.128): 56 data bytes
64 bytes from 173.248.191.128: icmp_seq=0 ttl=57 time=40.699 ms
64 bytes from 173.248.191.128: icmp_seq=1 ttl=57 time=40.665 ms
64 bytes from 173.248.191.128: icmp_seq=2 ttl=57 time=41.108 ms
64 bytes from 173.248.191.128: icmp_seq=3 ttl=57 time=41.588 ms
64 bytes from 173.248.191.128: icmp_seq=4 ttl=57 time=40.561 ms

--- gemini.supportedns.com ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 40.561/40.924/41.588/0.381 ms

PING fresco.supportedns.com (173.248.191.250): 56 data bytes
64 bytes from 173.248.191.250: icmp_seq=0 ttl=57 time=41.571 ms
64 bytes from 173.248.191.250: icmp_seq=1 ttl=57 time=42.052 ms
64 bytes from 173.248.191.250: icmp_seq=2 ttl=57 time=41.486 ms
64 bytes from 173.248.191.250: icmp_seq=3 ttl=57 time=42.488 ms
64 bytes from 173.248.191.250: icmp_seq=4 ttl=57 time=42.460 ms

--- fresco.supportedns.com ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 41.486/42.011/42.488/0.424 ms

 

Indianapolis, Indiana:

PING echo.supportedns.com (173.248.187.2): 56 data bytes
64 bytes from 173.248.187.2: icmp_seq=0 ttl=54 time=46.775 ms
64 bytes from 173.248.187.2: icmp_seq=1 ttl=54 time=45.138 ms
64 bytes from 173.248.187.2: icmp_seq=2 ttl=54 time=40.850 ms
64 bytes from 173.248.187.2: icmp_seq=3 ttl=54 time=41.281 ms
64 bytes from 173.248.187.2: icmp_seq=4 ttl=54 time=44.189 ms

--- echo.supportedns.com ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 40.850/43.647/46.775/2.268 ms

PING gemini.supportedns.com (173.248.191.128): 56 data bytes
64 bytes from 173.248.191.128: icmp_seq=0 ttl=54 time=61.443 ms
64 bytes from 173.248.191.128: icmp_seq=1 ttl=54 time=41.221 ms
64 bytes from 173.248.191.128: icmp_seq=2 ttl=54 time=41.978 ms
64 bytes from 173.248.191.128: icmp_seq=3 ttl=54 time=42.420 ms
64 bytes from 173.248.191.128: icmp_seq=4 ttl=54 time=46.707 ms

--- gemini.supportedns.com ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 41.221/46.754/61.443/7.589 ms
PING fresco.supportedns.com (173.248.191.250): 56 data bytes


64 bytes from 173.248.191.250: icmp_seq=0 ttl=54 time=41.686 ms
64 bytes from 173.248.191.250: icmp_seq=1 ttl=54 time=218.249 ms
64 bytes from 173.248.191.250: icmp_seq=2 ttl=54 time=43.488 ms
64 bytes from 173.248.191.250: icmp_seq=3 ttl=54 time=45.830 ms
64 bytes from 173.248.191.250: icmp_seq=4 ttl=54 time=41.769 ms

--- fresco.supportedns.com ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 41.686/78.204/218.249/70.038 ms

 

Boston, MA:

Pinging echo.supportedns.com [173.248.187.2] with 32 bytes of data: 
Reply from 173.248.187.2: bytes=32 time=69ms TTL=56 
Reply from 173.248.187.2: bytes=32 time=67ms TTL=56 
Reply from 173.248.187.2: bytes=32 time=66ms TTL=56 
Reply from 173.248.187.2: bytes=32 time=68ms TTL=56 
Reply from 173.248.187.2: bytes=32 time=80ms TTL=56 

Ping statistics for 173.248.187.2: 
   Packets: Sent = 5, Received = 5, Lost = 0 (0% loss), 
Approximate round trip times in milli-seconds: 
   Minimum = 66ms, Maximum = 80ms, Average = 70ms

Pinging fresco.supportedns.com [173.248.191.250] with 32 bytes of data: 
Reply from 173.248.191.250: bytes=32 time=65ms TTL=56 
Reply from 173.248.191.250: bytes=32 time=66ms TTL=56 
Reply from 173.248.191.250: bytes=32 time=67ms TTL=56 
Reply from 173.248.191.250: bytes=32 time=74ms TTL=56 
Reply from 173.248.191.250: bytes=32 time=65ms TTL=56 

Ping statistics for 173.248.191.250: 
   Packets: Sent = 5, Received = 5, Lost = 0 (0% loss), 
Approximate round trip times in milli-seconds: 
   Minimum = 65ms, Maximum = 74ms, Average = 67ms

Pinging gemini.supportedns.com [173.248.191.128] with 32 bytes of data: 
Reply from 173.248.191.128: bytes=32 time=68ms TTL=56 
Reply from 173.248.191.128: bytes=32 time=67ms TTL=56 
Reply from 173.248.191.128: bytes=32 time=68ms TTL=56 
Reply from 173.248.191.128: bytes=32 time=67ms TTL=56 
Reply from 173.248.191.128: bytes=32 time=66ms TTL=56 

Ping statistics for 173.248.191.128: 
   Packets: Sent = 5, Received = 5, Lost = 0 (0% loss), 
Approximate round trip times in milli-seconds: 
   Minimum = 66ms, Maximum = 68ms, Average = 67ms

 

Will update with more soon.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...