![]() |
|
|||||||
| Chit Chat Public Talk about any thing you want! This forum is public. |
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||||||||||
|
|||||||||||
|
Ping Response Time
Is this a normal pring response Time for Matrix or is this abnormally high? I live in San Diego, CA;
Pinging matrixreseller.com [65.57.231.246] with 32 bytes of data: Reply from 65.57.231.246: bytes=32 time=101ms TTL=39 Reply from 65.57.231.246: bytes=32 time=135ms TTL=39 Reply from 65.57.231.246: bytes=32 time=105ms TTL=39 Reply from 65.57.231.246: bytes=32 time=101ms TTL=39 Ping statistics for 65.57.231.246: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 101ms, Maximum = 135ms, Average = 110ms |
|
#2
|
||||||||||||
|
||||||||||||
|
I'm also in San Diego and I get the following:
Pinging matrixreseller.com [65.57.231.246] with 32 bytes of data: Reply from 65.57.231.246: bytes=32 time=118ms TTL=46 Reply from 65.57.231.246: bytes=32 time=117ms TTL=46 Reply from 65.57.231.246: bytes=32 time=119ms TTL=46 Reply from 65.57.231.246: bytes=32 time=117ms TTL=46 Ping statistics for 65.57.231.246: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 117ms, Maximum = 119ms, Average = 117ms I was having some speed issues over the last couple of days, but I don't know if it had anything to do with the weather we've had, or what... I'm no expert with this kind of stuff, but my guess is some of it may have to do with our distance from Matrix, and possibly some bad connectivity in the middle. Someone spoke of Cogent as a possible funky connection, and in doing a traceroute I see that much of our connection to Florida is through Cogent. Anyhow, are you having speed issues? |
|
#3
|
|||||||||||
|
|||||||||||
|
This is what I get - I am in the UK:
Ping 65.57.231.246 [freebsd2.vortechhosting.com] Round trip time to 65.57.231.246: 78 ms Round trip time to 65.57.231.246: 62 ms Round trip time to 65.57.231.246: 63 ms Round trip time to 65.57.231.246: 62 ms Round trip time to 65.57.231.246: 63 ms Round trip time to 65.57.231.246: 62 ms Round trip time to 65.57.231.246: 63 ms Round trip time to 65.57.231.246: 62 ms Round trip time to 65.57.231.246: 63 ms Round trip time to 65.57.231.246: 78 ms Average time over 10 pings: 65.6 ms |
|
#4
|
||||||||||||
|
||||||||||||
|
Singapore ...
Pinging matrixreseller.com [65.57.231.246] with 32 bytes of data: Reply from 65.57.231.246: bytes=32 time=300ms TTL=39 Reply from 65.57.231.246: bytes=32 time=311ms TTL=39 Reply from 65.57.231.246: bytes=32 time=270ms TTL=38 Reply from 65.57.231.246: bytes=32 time=271ms TTL=38 Ping statistics for 65.57.231.246: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 270ms, Maximum = 311ms, Average = 288ms Tracing route to matrixreseller.com [65.57.231.246] over a maximum of 30 hops: 1 <10 ms <10 ms <10 ms 192.168.1.1 2 20 ms 30 ms 20 ms 192.168.100.1 3 30 ms 20 ms 20 ms 192.168.101.6 4 31 ms 20 ms 20 ms 203.117.160.33 5 20 ms 30 ms 20 ms ge3-0-gsrtl2.starhub.net.sg [203.118.0.7] 6 20 ms 30 ms 20 ms pos1-0-gsrts2.starhub.net.sg [203.118.1.242] 7 30 ms 20 ms 20 ms vlan903-cat6ts1-rsm2.starhub.net.sg [203.118.3.3] 8 30 ms 20 ms 20 ms f1-0-r26.starhub.net.sg [203.118.3.137] 9 20 ms 30 ms 30 ms 61.8.232.61 10 20 ms 30 ms 30 ms ge-0-0-0.r00.sngpsi01.sg.bb.verio.net [61.8.234.61] 11 200 ms 200 ms 231 ms p1-0-1-1.r81.mlpsca01.us.bb.verio.net [129.250.4.161] 12 230 ms 211 ms 210 ms p16-1-1-0.r20.mlpsca01.us.bb.verio.net [129.250.2.247] 13 200 ms 201 ms 200 ms p16-1-1-0.r20.snjsca04.us.bb.verio.net [129.250.5.9] 14 201 ms 200 ms 190 ms so-1-0-0.edge1.SanJose1.Level3.net [209.245.146.241] 15 200 ms 190 ms 201 ms so-5-0-0.gar1.SanJose1.level3.net [209.244.3.137] 16 201 ms 200 ms 200 ms so-7-0-0.mp1.SanJose1.Level3.net [64.159.1.73] 17 290 ms 290 ms 291 ms so-0-2-0.mp1.Orlando1.Level3.net [64.159.0.29] 18 291 ms 290 ms 300 ms gige9-0.hsipaccess1.Orlando1.Level3.net [64.159.0.34] 19 280 ms 281 ms 270 ms 67.30.136.2 20 290 ms 291 ms 290 ms 66.103.132.6 21 271 ms 320 ms 310 ms freebsd2.vortechhosting.com [65.57.231.246] Trace complete. Last edited by Scroller : 02-15-2003 at 03:00 AM. |
|
#5
|
|||||||||||
|
|||||||||||
|
jmbeach,
Do you have any of your clients complaining abount load time on your site(s)? Brian |
|
#6
|
||||
|
||||
|
Man thats high, I have sent Scroller's traceroute over to my router admin. Pings don't tell me much but traceroute we can see were the problem starts and try and reroute it.
__________________
Brad Pugh http://www.vortechhosting.com ------ Local System/Network Monitor http://nagios.hsphere.cc/ Login:guest Pass:guest XML FEED http://nagios.hsphere.cc/feed.xml ------ My Other Life:
|
|
#7
|
||||||||||||
|
||||||||||||
|
Brian,
No, I just signed up last Saturday, so most of the sites I host aren't here yet for my customers to complain, but I did have some huge network slowdown earlier this week. Again not sure if it was the storm that had anything to do with it, or perhaps Adelphia's services not being all that great. The last couple of days have been good, though. I'm still waiting on my nameserver propagation before moving sites here. To give you an example, though, of ping and traceroute to Florida versus ping and traceroute to my current server in Los Angeles: -------------------- ping to Matrix Pinging 216.157.140.66 with 32 bytes of data: Reply from 216.157.140.66: bytes=32 time=118ms TTL=110 Reply from 216.157.140.66: bytes=32 time=117ms TTL=110 Reply from 216.157.140.66: bytes=32 time=116ms TTL=110 Reply from 216.157.140.66: bytes=32 time=116ms TTL=110 Ping statistics for 216.157.140.66: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 116ms, Maximum = 118ms, Average = 116ms ---------------------- Ping to Los Angeles host Pinging siteassemble.com [12.158.169.235] with 32 bytes of data: Reply from 12.158.169.235: bytes=32 time=39ms TTL=110 Reply from 12.158.169.235: bytes=32 time=30ms TTL=110 Reply from 12.158.169.235: bytes=32 time=27ms TTL=110 Reply from 12.158.169.235: bytes=32 time=28ms TTL=110 Ping statistics for 12.158.169.235: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 27ms, Maximum = 39ms, Average = 31ms ---------------------- traceroute to Matrix -------------------------- Tracing route to 216.157.140.66 over a maximum of 30 hops 1 11 ms 11 ms 11 ms ca-crlsca-cuda2-c7a-a-gate.crlsca.adelphia.net [68.70.250.1] 2 11 ms 11 ms 11 ms 68.70.63.213 3 16 ms 15 ms 17 ms 24.52.223.137 4 14 ms 15 ms 15 ms 66.170.128.5 5 15 ms 16 ms 15 ms unk-426d0385.adelphiacom.net [66.109.3.133] 6 16 ms 14 ms 14 ms p3-00-00-00.n0.lax00.adelphiacom.net [66.109.0.129] 7 23 ms 22 ms 19 ms p3-00-02-00.n0.sjc75.adelphiacom.net [66.109.0.21] 8 22 ms 23 ms 23 ms p3-00-00-00.r0.sjc75.adelphiacom.net [66.109.0.134] 9 22 ms 24 ms 22 ms hamptonroads.com [66.11.3.202] 10 24 ms 23 ms 23 ms paix.cogentco.com [198.32.176.131] 11 24 ms 24 ms 24 ms p6-0.core01.sfo01.atlas.cogentco.com [66.28.4.145] 12 24 ms 24 ms 23 ms p4-0.core01.sjc01.atlas.cogentco.com [66.28.4.94] 13 36 ms 35 ms 35 ms p13-0.core01.lax01.atlas.cogentco.com [66.28.4.73] 14 39 ms 38 ms 37 ms p5-0.core01.san01.atlas.cogentco.com [66.28.4.78] 15 60 ms 58 ms 61 ms p6-0.core01.iah01.atlas.cogentco.com [66.28.4.5] 16 117 ms 117 ms 117 ms p15-0.core01.tpa01.atlas.cogentco.com [66.28.4.46] 17 116 ms 117 ms 118 ms p5-0.core01.mco01.atlas.cogentco.com [66.28.4.141] 18 117 ms 118 ms 118 ms g0-2.na01.b006686-0.mco01.atlas.cogentco.com [66.250.13.6] 19 118 ms 118 ms 120 ms ColoSolutions.demarc.cogentco.com [38.112.1.194] 20 122 ms 120 ms 118 ms 66.103.132.6 21 117 ms 119 ms 118 ms 216.157.140.66 ----------------- traceroute to host in Los Angeles ----------------------- Tracing route to siteassemble.com [12.158.169.235] over a maximum of 30 hops: 1 11 ms 11 ms 12 ms ca-crlsca-cuda2-c7a-a-gate.crlsca.adelphia.net [68.70.250.1] 2 12 ms 11 ms 11 ms 68.70.63.213 3 15 ms 12 ms 13 ms 24.52.223.137 4 16 ms 15 ms 15 ms 66.170.128.5 5 15 ms 16 ms 16 ms unk-426d0385.adelphiacom.net [66.109.3.133] 6 17 ms 13 ms 13 ms unk-426d0392.adelphiacom.net [66.109.3.146] 7 18 ms 15 ms 15 ms gigabitethernet1-1-202.ipcolo2.LosAngeles1.Level3.net [166.90.146.93] 8 16 ms 15 ms 15 ms gigabitethernet5-0.core2.LosAngeles1.Level3.net[209.244.10.45] 9 13 ms 15 ms 14 ms att-level3-oc48.LosAngeles1.Level3.net [64.152.193.82] 10 24 ms 22 ms 23 ms gbr5-p90.la2ca.ip.att.net [12.123.28.193] 11 26 ms 23 ms 25 ms tbr1-p013501.la2ca.ip.att.net [12.122.11.137] 12 26 ms 26 ms 26 ms tbr2-cl3.sffca.ip.att.net [12.122.10.25] 13 25 ms 25 ms 25 ms gbr2-p40.sffca.ip.att.net [12.122.11.86] 14 25 ms 25 ms 25 ms gar1-p370.sffca.ip.att.net [12.123.13.61] 15 28 ms 28 ms 27 ms 12.126.195.22 16 31 ms 30 ms 31 ms uds2.heraklesdata.net [12.158.168.6] 17 30 ms 29 ms 27 ms 235.169.158.12.datastreamusa.com [12.158.169.235 So, it's clear to see that the best bet is to be physically closer to your host, granted he's got great servers, and a great connection, but so far in my research, not one host in California that offers HSphere comes close to Matrix. Plus, depending on where your customers and potential visitors to your site(s) are, if they're on the eastern side of the US, then they'll have no speed issues. Hey, keep me up to date if you have any speed/network issues. I do plan on keeping a close eye on this because my clients certainly wouldn't stand for it if their sites were bogging. Good luck! |
|
#8
|
|||||||||||
|
|||||||||||
|
Tracing route to matrixreseller.com [65.57.231.246]
over a maximum of 30 hops: 1 2 ms 3 ms 3 ms brian [192.168.2.1] 2 30 ms 23 ms 26 ms 10.66.0.1 3 10 ms 10 ms 11 ms pwsdca1-rtr1-fe2-6.san.rr.com [24.25.192.70] 4 13 ms 11 ms 11 ms WCSDCA1-GSR1-SRP0.san.rr.com [24.25.196.1] 5 18 ms 25 ms 15 ms pop2-las-P7-0.atdn.net [66.185.137.169] 6 15 ms 50 ms 15 ms bb2-las-P1-0.atdn.net [66.185.137.162] 7 47 ms 47 ms 25 ms bb2-sun-P5-0.atdn.net [66.185.152.23] 8 22 ms 35 ms 60 ms pop2-sun-P1-0.atdn.net [66.185.140.195] 9 21 ms 23 ms 22 ms Level3.atdn.net [66.185.147.18] 10 24 ms 25 ms 21 ms so-0-0-0.gar1.SanJose1.level3.net [209.247.8.157 ] 11 22 ms 22 ms 22 ms so-7-0-0.mp1.SanJose1.Level3.net [64.159.1.73] 12 88 ms 89 ms 91 ms so-0-1-0.mp2.Orlando1.Level3.net [64.159.0.26] 13 88 ms 90 ms 89 ms gige9-1.hsipaccess1.Orlando1.Level3.net [64.159. 0.42] 14 92 ms 94 ms 90 ms 67.30.136.2 15 90 ms 89 ms 93 ms 66.103.132.6 16 103 ms 104 ms 103 ms matrixreseller.com [65.57.231.246] |
|
#9
|
|||||||||||
|
|||||||||||
|
I have just 2 sites being hosted on Matrix reseller plan. No issues yet..... Speed seems to be ok......I plan on staying with Matrix for awhile. They have great support and amazing prices....I've been put through the ringer with other hosts. No support, and major downtime!
|
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Can you ping me now? | awen | Chit Chat Public | 12 | 04-22-2005 08:13 AM |
| Yes we're in Ping Zine! | admin | News and Announcements | 2 | 04-30-2004 10:02 AM |
| IP Address to Ping | Allen | Chit Chat Public | 14 | 09-16-2003 02:10 PM |
| Question - ping vs. HTTP? | sandgnat | Chit Chat Public | 2 | 04-28-2003 10:47 AM |