digitalFAQ.com Forum

digitalFAQ.com Forum (https://www.digitalfaq.com/forum/)
-   Website and Server Troubleshooting (https://www.digitalfaq.com/forum/web-tech/)
-   -   Okay to use pings/tracerts to test server speeds? (https://www.digitalfaq.com/forum/web-tech/4470-pings-tracerts-test.html)

faustine 08-07-2012 12:43 AM

Hmm, I was wondering, if Tracerts and Pings, the ms reading is higher, .... will this mean its not good for Singapore?

From my Tracert for both Hawkhost and Stablehost,
Code:

TraceRoute to 50.23.66.3 [sjc.hawkhost.com]
Hop    (ms)    (ms)    (ms)            IP Address    Host name
1      1      0      0          8.9.232.73    xe-5-3-0.edge3.dallas1.level3.net 
2      0      0      0          4.69.145.140    ae-3-80.edge2.dallas3.level3.net 
3      0      0      0          4.59.36.94    softlayer-t.edge2.dallas3.level3.net 
4      14      1      0          173.192.18.208    ae7.bbr01.eq01.dal03.networklayer.com 
5      41      41      41          173.192.18.141    ae0.bbr01.cs01.lax01.networklayer.com 
6      64      41      41          173.192.18.167    ae7.bbr02.cs01.lax01.networklayer.com 
7      41      41      41          173.192.18.150    ae0.bbr02.eq01.sjc02.networklayer.com 
8      41      41      41          173.192.18.251    ae5.dar02.sr01.sjc01.networklayer.com 
9      42      50      42          50.23.118.133    po2.fcr01.sr01.sjc01.networklayer.com 
10      41      41      41          50.23.66.3    50.23.66.3-static.reverse.softlayer.com 
Trace complete

Hawkhost -- Singapore DC seems slower...
Code:

TraceRoute to 216.12.197.183 [sng.hawkhost.com]
Hop    (ms)    (ms)    (ms)            IP Address    Host name
1      0      0      0          206.123.64.42      - 
2      40      2      0          173.219.246.92    173-219-246-92-link.sta.suddenlink.net 
3      0      0      0          206.223.118.24    te1-5.bbr01.eq01.dal01.networklayer.com 
4      41      41      41          173.192.18.141    ae0.bbr01.cs01.lax01.networklayer.com 
5      223      223      223          50.97.18.168    ae0.bbr01.eq01.sng02.networklayer.com 
6      224      224      224          50.97.18.199    ae5.dar02.sr03.sng01.networklayer.com 
7      225      224      224          174.133.118.133    po2.fcr01.sr03.sng01.networklayer.com 
8      224      224      224          216.12.197.183    216.12.197.183-static.reverse.softlayer.com 
Trace complete

Stablehost faster?
Code:

TraceRoute to 199.96.156.70 [cp22.stablehost.com]
Hop    (ms)    (ms)    (ms)            IP Address    Host name
1      0      0      0          206.123.64.42      - 
2      31      0      0          64.124.196.225    xe-4-2-0.er2.dfw2.us.above.net 
3      3      3      3          77.67.71.165    ae2-109.dal33.ip4.tinet.net 
4      24      24      24          89.149.182.49    xe-1-2-0.phx10.ip4.tinet.net 
5      118      27      236          173.241.130.10    total-server-solutions-gw.ip4.tinet.net 
6      25      25      25          199.36.222.106      - 
7      25      25      25          199.96.156.70    cp22.stablehost.com 
Trace complete

Pings :
Code:

Ping 199.96.156.70 [cp22.stablehost.com]
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Average time over 10 pings: 25 ms

Code:

Ping 50.23.66.3 [sjc.hawkhost.com]
Round trip time to 50.23.66.3: 42 ms
Round trip time to 50.23.66.3: 41 ms
Round trip time to 50.23.66.3: 41 ms
Round trip time to 50.23.66.3: 41 ms
Round trip time to 50.23.66.3: 41 ms
Timed out
Round trip time to 50.23.66.3: 42 ms
Round trip time to 50.23.66.3: 41 ms
Timed out
Round trip time to 50.23.66.3: 42 ms
Average time over 10 pings: 33.1 ms

Code:

Ping 216.12.197.183 [sng.hawkhost.com]
Round trip time to 216.12.197.183: 225 ms
Round trip time to 216.12.197.183: 224 ms
Round trip time to 216.12.197.183: 224 ms
Round trip time to 216.12.197.183: 224 ms
Round trip time to 216.12.197.183: 224 ms
Round trip time to 216.12.197.183: 225 ms
Round trip time to 216.12.197.183: 224 ms
Round trip time to 216.12.197.183: 224 ms
Round trip time to 216.12.197.183: 224 ms
Round trip time to 216.12.197.183: 225 ms
Average time over 10 pings: 224.3 ms

Wooooo -- SG DC Hawkhost so slow?!?!

Now I'm confused... haha
Ping and Tracert -- Stablehost is the winner... but what is the significance of these numbers?

kpmedia 08-07-2012 02:10 AM

Understand that pings and traceroutes are not measurements of speed.

A ping is simply a question. Your computer asks "Server, are you there?" and the server either responds "Hello, here I am!" or there's no response. No response can mean (A) downtime, or (B) ICMP packets are blocked. ICMP packets are what a "ping" is using to communicate with. It's a verification of communication, not a speed test.

Traceroute is a method to see how communications is routing from router/switch/datacenter to router/switch/datacenter, along the path between your current location and the server being requested. It's drawing a map for you, showing how to navigate the maze to get from point A to point B. It's not a measure of speed. Some points along the path may block ICMP packets, so tracerts commonly have timeouts between the start and end.

At most, ping and tracert can be used to analyze latency, which is speed of requests back and forth. Unless you're running a game server, a streaming videos archive, or some sort of stock exchange application, latency isn't really an issue. For websites, it's really not that important, as long as you're within acceptable norms. We are, after all, talking in milliseconds -- 1/1000th of a second. So 130ms = 0.13 seconds. (Also understand browsers load content concurrently, so you cannot simply multiply latency times the number of requests to arrive at site speed. The math is not that simplistic!)

Speed is effected by routing times, but the ultimate determining factor of speed is the content itself. This server is 130ms from my location, but pages load in under 1 second. The forum loads in under 1.5 seconds. Both of those are excellent speeds. I can ping my ISPs server in 35ms, but its homepage loads like crap, and takes 2-3 seconds (at best). This is why server-side caching, and leveraging user-end caching (browser cache), is so important.

Anything above 150ms should be a concern. Anything in the 90-150ms range is on the higher end of acceptable, and would quality as "good". Anything below 90ms is "excellent". Opinions on what makes a "good" or "bad" number varies. And understand some people are clueless about what any of it means, and just give out random numbers, so be careful who you listen to. (There's a lot of inexperienced teens and college students out there writing on blogs and forums, pretending to be experts.)

You also need to test from your current physical location -- not using some online tool. Bring up DOS and run tracert against a domain (FQDN) or IP address. Same for ping. See what your local results are. Then test against from a multiple-location tool, such as Just-Ping.com.

The Hawkhost Singapore location is both slow, and losing lots of packets. They're in the Softlayer Singapore DC, and the Softlayer SG test server is fine. So I don't know what's wrong with the Hawkhost SG server at this moment.

faustine 08-07-2012 02:10 AM

Temp post to be moved
 
Tracert of Stablehost and Hawkhost -- vs -- our JaguarPC VPS node:

Code:

TraceRoute to 199.96.156.70 [cp22.stablehost.com]
Hop    (ms)    (ms)    (ms)            IP Address    Host name
1      0      0      0          206.123.64.42      - 
2      0      0      0          64.124.196.225    xe-4-2-0.er2.dfw2.us.above.net 
3      3      3      3          77.67.71.165    ae2-109.dal33.ip4.tinet.net 
4      24      24      24          89.149.182.49    xe-1-2-0.phx10.ip4.tinet.net 
5      25      25      25          173.241.130.10    total-server-solutions-gw.ip4.tinet.net 
6      27      25      25          199.36.222.106      - 
7      25      25      25          199.96.156.70    cp22.stablehost.com 
Trace complete

Code:

TraceRoute to 216.12.197.183 [sng.hawkhost.com] -  - Hawkhost Singapore
Hop    (ms)    (ms)    (ms)            IP Address    Host name
1      0      0      0          206.123.64.42      - 
2      0      0      0          173.219.246.92    173-219-246-92-link.sta.suddenlink.net 
3      1      0      0          206.223.118.24    te1-5.bbr01.eq01.dal01.networklayer.com 
4      41      41      41          173.192.18.141    ae0.bbr01.cs01.lax01.networklayer.com 
5      223      223      223          50.97.18.168    ae0.bbr01.eq01.sng02.networklayer.com 
6      224      224      224          50.97.18.199    ae5.dar02.sr03.sng01.networklayer.com 
7      224      225      224          174.133.118.133    po2.fcr01.sr03.sng01.networklayer.com 
8      224      224      224          216.12.197.183    216.12.197.183-static.reverse.softlayer.com 
Trace complete

Code:

TraceRoute to 50.23.66.3 [sjc.hawkhost.com] - Hawkhost CA San Jose
Hop    (ms)    (ms)    (ms)            IP Address    Host name
1      0      0      0          8.9.232.73    xe-5-3-0.edge3.dallas1.level3.net 
2      0      0      0          4.69.145.140    ae-3-80.edge2.dallas3.level3.net 
3      2      0      0          4.59.36.94    softlayer-t.edge2.dallas3.level3.net 
4      19      2      0          173.192.18.208    ae7.bbr01.eq01.dal03.networklayer.com 
5      52      41      41          173.192.18.141    ae0.bbr01.cs01.lax01.networklayer.com 
6      46      41      41          173.192.18.167    ae7.bbr02.cs01.lax01.networklayer.com 
7      41      41      41          173.192.18.150    ae0.bbr02.eq01.sjc02.networklayer.com 
8      41      41      41          173.192.18.251    ae5.dar02.sr01.sjc01.networklayer.com 
9      42      42      42          50.23.118.133    po2.fcr01.sr01.sjc01.networklayer.com 
10      41      41      41          50.23.66.3    50.23.66.3-static.reverse.softlayer.com 
Trace complete

Code:

TraceRoute to 209.140.18.169 [cybermind.com.sg]  --  JPC
Hop    (ms)    (ms)    (ms)            IP Address    Host name
1      0      0      0          206.123.64.42      - 
2      0      0      0          64.124.196.225    xe-4-2-0.er2.dfw2.us.above.net 
3      0      0      0          64.125.30.98    xe-3-1-0.cr2.dfw2.us.above.net 
4      5      5      5          64.125.26.134    xe-1-2-0.cr2.iah1.us.above.net 
5      81      19      19          64.125.31.49    xe-1-1-0.mpr3.atl6.us.above.net 
6      20      20      20          64.124.202.214    64.124.202.214.t00623-01.above.net 
7      20      20      20          206.220.172.26      - 
8      20      20      20          184.170.248.170      - 
9      20      20      20          209.140.17.38      - 
10      20      20      20          209.140.18.128    static-128-18.140.209.nocdirect.com 
11      20      20      20          209.140.18.169    static-169-18.140.209.nocdirect.com

But as of now server performance of JPC is not satisfactory -- slow and downloading PDF file after they shut off the old node.

Pings Stablehost / Hawkhost VS JPC's our own node:
Code:

Ping 199.96.156.70 [cp22.stablehost.com]
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Round trip time to 199.96.156.70: 25 ms
Average time over 10 pings: 25 ms

Code:

Ping 216.12.197.183 [sng.hawkhost.com]
Round trip time to 216.12.197.183: 225 ms
Round trip time to 216.12.197.183: 225 ms
Round trip time to 216.12.197.183: 224 ms
Round trip time to 216.12.197.183: 224 ms
Round trip time to 216.12.197.183: 224 ms
Round trip time to 216.12.197.183: 224 ms
Round trip time to 216.12.197.183: 225 ms
Round trip time to 216.12.197.183: 224 ms
Round trip time to 216.12.197.183: 224 ms
Round trip time to 216.12.197.183: 224 ms
Average time over 10 pings: 224.3 ms

Code:

Ping 50.23.66.3 [sjc.hawkhost.com]
Round trip time to 50.23.66.3: 41 ms
Round trip time to 50.23.66.3: 41 ms
Round trip time to 50.23.66.3: 41 ms
Round trip time to 50.23.66.3: 41 ms
Round trip time to 50.23.66.3: 41 ms
Timed out
Round trip time to 50.23.66.3: 41 ms
Round trip time to 50.23.66.3: 42 ms
Timed out
Round trip time to 50.23.66.3: 41 ms
Average time over 10 pings: 32.9 ms

Code:

Ping 209.140.18.169 [cybermind.com.sg]
Round trip time to 209.140.18.169: 20 ms
Round trip time to 209.140.18.169: 20 ms
Round trip time to 209.140.18.169: 20 ms
Round trip time to 209.140.18.169: 20 ms
Round trip time to 209.140.18.169: 20 ms
Round trip time to 209.140.18.169: 20 ms
Round trip time to 209.140.18.169: 20 ms
Round trip time to 209.140.18.169: 20 ms
Round trip time to 209.140.18.169: 20 ms
Round trip time to 209.140.18.169: 20 ms
Average time over 10 pings: 20 ms


kpmedia 08-07-2012 02:26 AM

The pings and traceroutes between JaguarPC and Stablehost / Hawkhost all look normal, to be honest.
And cybermind.com.sg loads extremely fast in a web browser.

faustine 08-07-2012 02:45 AM

ok, here goes! hot from my PC

Code:

Tracing route to sjc.hawkhost.com [50.23.66.3]
over a maximum of 30 hops:

  1    81 ms    79 ms    79 ms  10.208.2.236
  2    74 ms    79 ms    79 ms  203.116.22.194
  3  762 ms  172 ms  239 ms  203.117.35.65
  4    72 ms    78 ms    79 ms  203.117.36.17
  5  126 ms    69 ms    89 ms  203.117.36.26
  6    76 ms    79 ms    79 ms  v101.bbr01.eq01.sng02.networklayer.com [50.97.16.9]
  7  344 ms  236 ms  139 ms  ae1.bbr01.eq01.tok01.networklayer.com [50.97.18.164]
  8  918 ms  515 ms  269 ms  ae2.bbr02.eq01.sjc02.networklayer.com [50.97.18.160]
  9  267 ms  249 ms  247 ms  ae5.dar02.sr01.sjc01.networklayer.com [173.192.18.251]
 10  246 ms  238 ms  253 ms  po2.fcr01.sr01.sjc01.networklayer.com [50.23.118.133]
 11  243 ms  257 ms  238 ms  50.23.66.3-static.reverse.softlayer.com [50.23.66.3]

Trace complete.

Code:

Tracing route to sng.hawkhost.com [216.12.197.183]
over a maximum of 30 hops:

  1    93 ms  249 ms    71 ms  10.208.2.98
  2    78 ms    79 ms    73 ms  203.116.22.194
  3    83 ms    81 ms    83 ms  203.117.190.85
  4    70 ms    79 ms    79 ms  203.116.5.158
  5    79 ms    59 ms    68 ms  i-1-0-0.6ntp-core01.bi.telstraglobal.net [202.84.243.81]
  6    72 ms    68 ms    69 ms  i-0-1-0-0.istt02.bi.telstraglobal.net [202.84.243.110]
  7    76 ms    59 ms    69 ms  unknown.telstraglobal.net [202.126.128.18]
  8    73 ms    59 ms    79 ms  ae5.dar01.sr03.sng01.networklayer.com [50.97.18.197]
  9    76 ms    60 ms    68 ms  po1.fcr01.sr03.sng01.networklayer.com [174.133.118.131]
 10  106 ms    77 ms    98 ms  216.12.197.183-static.reverse.softlayer.com [216.12.197.183]

Trace complete.

Code:

Tracing route to cp22.stablehost.com [199.96.156.70]
over a maximum of 30 hops:

  1  388 ms    77 ms  214 ms  10.208.2.204
  2    68 ms    69 ms    58 ms  203.116.22.194
  3  350 ms    79 ms    99 ms  203.117.190.85
  4  100 ms    79 ms    97 ms  anutsi11.starhub.net.sg [203.118.3.227]
  5  508 ms  559 ms  259 ms  highwinds.com.any2ix.coresite.com [206.223.143.113]
  6  273 ms  449 ms  249 ms  e2-1.r1.ph.hwng.net [209.197.0.22]
  7  267 ms  259 ms  259 ms  unknown.hwng.net [209.197.5.154]
  8  258 ms  258 ms  259 ms  po5.bb2.cwie.10.2.phx0.cwie.net [64.38.200.5]
  9  277 ms  267 ms  278 ms  69.160.32.21
 10  302 ms  299 ms  609 ms  199.36.222.106
 11  796 ms  319 ms  379 ms  cp22.stablehost.com [199.96.156.70]

Trace complete.

Code:

Tracing route to cybermind.com.sg [209.140.18.169]
over a maximum of 30 hops:

  1  102 ms    79 ms    79 ms  10.208.2.236
  2    76 ms    59 ms    68 ms  203.116.22.194
  3    96 ms    89 ms  106 ms  203.117.35.65
  4  181 ms    79 ms    75 ms  203.117.35.205
  5    98 ms    97 ms    99 ms  203.117.34.34
  6  284 ms  259 ms  259 ms  te7-2.ccr02.sjc04.atlas.cogentco.com [38.104.140.249]
  7  307 ms  279 ms  279 ms  te0-0-0-6.ccr21.sfo01.atlas.cogentco.com [154.54.7.173]
  8  327 ms  336 ms  336 ms  te0-2-0-2.ccr21.mci01.atlas.cogentco.com [154.54.6.162]
  9  345 ms  339 ms  338 ms  te0-2-0-5.ccr21.ord01.atlas.cogentco.com [154.54.82.142]
 10  342 ms  329 ms  327 ms  te0-2-0-4.ccr21.atl01.atlas.cogentco.com [154.54.29.101]
 11  352 ms  338 ms  461 ms  38.122.18.211
 12  346 ms  319 ms  319 ms  206.220.172.26
 13  372 ms  348 ms  338 ms  184.170.248.170
 14  365 ms  356 ms  358 ms  209.140.17.38
 15  343 ms  329 ms  342 ms  static-128-18.140.209.nocdirect.com [209.140.18.128]
 16  377 ms  359 ms  377 ms  static-169-18.140.209.nocdirect.com [209.140.18.169]

Trace complete.

From here, I see what you mean by running the tests from my own PC.. Hawkhost SG DC wins! LOL.. And JPC seems running too many hoops/routers??

faustine 08-07-2012 02:50 AM

Pings hot from my PC! * Sweating by the "oven" *

Code:

Pinging sjc.hawkhost.com [50.23.66.3] with 32 bytes of data:
Reply from 50.23.66.3: bytes=32 time=231ms TTL=52
Reply from 50.23.66.3: bytes=32 time=255ms TTL=52
Reply from 50.23.66.3: bytes=32 time=234ms TTL=52
Reply from 50.23.66.3: bytes=32 time=261ms TTL=52

Ping statistics for 50.23.66.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 231ms, Maximum = 261ms, Average = 245ms

Code:

Pinging sng.hawkhost.com [216.12.197.183] with 32 bytes of data:
Reply from 216.12.197.183: bytes=32 time=63ms TTL=55
Reply from 216.12.197.183: bytes=32 time=60ms TTL=55
Reply from 216.12.197.183: bytes=32 time=59ms TTL=55
Reply from 216.12.197.183: bytes=32 time=63ms TTL=55

Ping statistics for 216.12.197.183:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 59ms, Maximum = 63ms, Average = 61ms

Code:

Pinging cp22.stablehost.com [199.96.156.70] with 32 bytes of data:
Reply from 199.96.156.70: bytes=32 time=291ms TTL=50
Reply from 199.96.156.70: bytes=32 time=287ms TTL=50
Reply from 199.96.156.70: bytes=32 time=324ms TTL=50
Reply from 199.96.156.70: bytes=32 time=293ms TTL=50

Ping statistics for 199.96.156.70:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 287ms, Maximum = 324ms, Average = 298ms

Code:

Pinging cybermind.com.sg [209.140.18.169] with 32 bytes of data:
Reply from 209.140.18.169: bytes=32 time=343ms TTL=49
Reply from 209.140.18.169: bytes=32 time=381ms TTL=49
Reply from 209.140.18.169: bytes=32 time=332ms TTL=49
Reply from 209.140.18.169: bytes=32 time=334ms TTL=49

Ping statistics for 209.140.18.169:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 332ms, Maximum = 381ms, Average = 347ms

So from here the Hawkhost SG DC seems so much better?!

kpmedia 08-07-2012 02:55 AM

There's nothing unusual about the number of hops on the JaguarPC route. Start to worry only when it exceeds 30, or if it seems to loop back to itself for no apparent reason.

If anything, the Stablehost speeds look oddly slower than I would have expected. But then again, that can be due to any number of network related issues -- at your end, at their end, or in between.

The Hawkhost SG server does appear a bit slow (on the tracert), given the size of Singapore, and the fact that you're almost on top of it. The networks there must be slower or more congested than I thought. It did ping faster, but it usually does. Run UptimeScout against your site, and see how the site homepage actually loads starting on the second load. I have a feeling it's going to be faster than you think.

faustine 08-07-2012 02:56 AM

From the Multi-location, I'll just insert the SG numbers -- here for simplicity :

SJC - Hawkhost : Singapore, Singapore: Packets lost (80%) 185.9 188.2 190.5 50.23.66.3
SNG - Hawkhost : Singapore, Singapore: Packets lost (60%) 34.6 35.7 36.4 216.12.197.183
CP22 -Stablehost : Singapore, Singapore: Okay 217.2 231.8 243.8 199.96.156.70
JPC -- own : Singapore, Singapore: Okay 281.4 282.3 285.4 209.140.18.169

Seems the SG DC by Hawkhost wins again!

kpmedia 08-07-2012 03:19 AM

I think the weak link with the Los Angeles JaguarPC location is they're using Cogent bandwidth -- or rather the datacenter is (Colo@ in LA). Cogent has long been known as a discount bandwidth supplier, and sometimes their routes are screwy. Increased latency is par for the course with Cogent. It doesn't make a huge difference domestically, for websites, but it may be a factor in access quality from overseas.

Hawkhost is going over nLayer.

Stablehost is going over Highwinds to CWIE.

faustine 08-07-2012 03:24 AM

Wah.... lol... . should have posted all this information ... (researched), before getting JPC for him! Damn!

So now the case is Hawkhost or Stablehost? The Names you posted means nothing to me.. haha

Hawkhost SG -- according to the tracerts and pings, seems ok (I'm testing this over a 3G connection -- usb stick).... But if the Story about Tokyo routing is true.. it should be seen here as well? I saw in their blog -- announcement for The SG DC, someone posted the tracert results there, and NTT Tokyo came up..

I saw a familiar one in Stablehost Tracert:

4 100 ms 79 ms 97 ms anutsi11.starhub.net.sg [203.118.3.227]


That's our Singapore Starhub ISP!

faustine 08-07-2012 03:33 AM

Installed Uptime Scout .. here are my findings :
Cybermind - JPC : 3777ms
SJC - Hawkhost : 725ms
SNG - Hawkhost : 347ms
Stablehost : 875ms

kpmedia 08-07-2012 03:34 AM

Even I don't always think of bandwidth carriers when looking for new hosts. But I've gotten better about it in recent years.

Hawkhost and Stablehost are fine. Had their carriers been an issue, I'd have mentioned it.

Understand that I'm not saying Cogent is "bad" as much as it's just not the best. And in their specific case, the routes and latency is a known issue for most of the past decade. Folks often thought Cogent would grow out of it, as the network matured, but it never happened. You get what you pay for.

JaguarPC in Atlanta -- their main datacenter -- runs over nLayer.

Your UptimeScout JPC reading sucks. 4 seconds... yuck. But is that the first load, or the second and beyond?

faustine 08-07-2012 03:42 AM

That's the first load.. over the last 5 loads (I set to auto run every 10 min) -- range between 3019 to 4383 ms!!!!

And AS I can see, SNG Hawkhost is clearly the winner here : Ranging from 207 to 347ms!
Stable host : 596 to 875ms..
In this regard, SJC Hawkhost is slightly better than Stablehost only...

so the message is clear? -- SNG Hawkhost -- SG!!

** Hmmm, we used to be from Atlanta DC previously, but that sucks as well...
Just curious and run the Uptime Scout with my own shared hosting with Arvixe, and that was even worst... 4752ms!

kpmedia 08-08-2012 11:47 PM

Arvixe is a good-but-not-best host. On our soon-to-be-released 1st/2nd/3rd/4th class scale, they're definite 2nd Class host. In my opinion, the biggest problem is that Arvand (the owner) can be a real ass (unprofessionally rude) to customers on public forums, and he needs to leave customer relations to others within the organization. Outside of that their techs and servers are quite decent. Prices, too.

I think Hawkhost @Singapore is a good option for your needs. :)

faustine 08-08-2012 11:58 PM

OK.

I'm shifting my Arvixe hosting to JPC for the time being till our contract with JPC ends...

These few days, Arvixe keep having internal 500 errors!! Up n down several times...

As for Hawkhost... if they have recurring discount for shared hosting.... now they don't... Also their new Semi dedicated hosting is only available at Texas - Dalias.... So I guess that is out for my friend... Stablehost in Arizona and Hawkhost in Texas had similar response times....

Hmm.... pondering..

kpmedia 08-09-2012 12:12 AM

Well, again, remember that ping/traceroute response times are not necessarily measurements of "speed". ;)

Regarding coupons:
- Current Hawkhost 50% OFF coupon whts50v2 does not appear to be limited to any one location, and can be use for any payment term.
- Current Stablehost 25% OFF coupon US-WHT2012-25 is good for USA shared plans, on any payment plan.

faustine 08-09-2012 08:57 AM

just out of curiousity... I tried entering whts50v2 in hawkhost promotion code box but it doesn't apply for semi dedicated in Texas...

We have till next year Sep to change host.... though....

You're saying pings and tracert doesn't indicate the speed and reliability... so what else will help us determine the good ones from the bad?

kpmedia 08-10-2012 05:22 PM

The content of the site ultimately determines the speed -- latency is an effect, but not the ulterior determining factor. There's too much weight put into latency (and thus ping and traceroute), instead of ascertaining the entire "big picture" of what's going on. And that big picture includes the coding quality of the site, any applicable caching plugins/modules, and things of that nature.

Some hosts overstuff (overload) servers -- NOT to be confused with "overselling" (which is a poor way to express reasonable resource/server management) -- and that can limit the way code functions on a certain site, at a specific host. The only way to truly determine good hosts from bad is to use them, and see how it works. Of course, the ability to judge a host's quality is limited by your own understanding of networking, servers, and site coding. That's why non-affiliate-biased lists of "good hosts" (like the Best Hosts List here at digitalFAQ.com) is so important to folks like yourself, as they've been created by a person/persons with quite a bit of experience and knowledge in these many variables, including how they interplay with one another.

In terms of deciding between Stablehost and Hawkhost -- both are good, so nothing to fear. Neither overload servers.

In terms of deciding the best location, latency can assist in that. It does appear that Hawkhost Singapore would be ideal for your Singapore traffic.

The Hawkhost semi-dedicated coupon is sdlaunch and is good for 30% for life on all semi-dedicated plans. :)

faustine 08-10-2012 06:15 PM

OK.

hmm too bad their semi-dedicated are only available in Texas....

Thanks for your guidance!


All times are GMT -5. The time now is 12:37 AM

Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.