Results 1 to 22 of 22
  1. #1
    Join Date
    Mar 2002
    Location
    England
    Posts
    2,014

    Please can some people from around the world test the speed of my site?

    www.sdsym.com

    I'm on Nocster [ www.nocster.net ] and it seems to be running a bit slow recently, like response times seem to be a bit slow, I don't know how to test it out.

    I'd appreciate it if people find out some details/test it from around the world, thanks

  2. #2
    Join Date
    Jul 2002
    Posts
    57
    from europe:
    Reply from 64.191.3.99: bytes=32 time=1016ms TTL=239
    Reply from 64.191.3.99: bytes=32 time=1154ms TTL=239
    Reply from 64.191.3.99: bytes=32 time=1029ms TTL=239
    Reply from 64.191.3.99: bytes=32 time=961ms TTL=239

    Approximate round trip times in milli-seconds:
    Minimum = 961ms, Maximum = 1154ms, Average = 1040ms

  3. #3
    from Asia

    Pinging 64.191.3.99 with 32 bytes of data:

    Reply from 64.191.3.99: bytes=32 time=270ms TTL=242
    Reply from 64.191.3.99: bytes=32 time=271ms TTL=242
    Reply from 64.191.3.99: bytes=32 time=270ms TTL=242
    Reply from 64.191.3.99: bytes=32 time=271ms TTL=242

    Ping statistics for 64.191.3.99:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 270ms, Maximum = 271ms, Average = 270ms
    RyanMandrake

  4. #4
    Join Date
    Jul 2002
    Posts
    180
    Europe:

    Pinging sdsym.com [64.191.3.99] with 32 bytes of data:

    Reply from 64.191.3.99: bytes=32 time=95ms TTL=238
    Reply from 64.191.3.99: bytes=32 time=99ms TTL=238
    Reply from 64.191.3.99: bytes=32 time=94ms TTL=238
    Reply from 64.191.3.99: bytes=32 time=94ms TTL=238

    Ping statistics for 64.191.3.99:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 94ms, Maximum = 99ms, Average = 95ms

  5. #5
    From Dallas, TX:

    Reply from 64.191.3.99: bytes=32 time=50ms TTL=246
    Reply from 64.191.3.99: bytes=32 time=60ms TTL=246
    Reply from 64.191.3.99: bytes=32 time=50ms TTL=246
    Reply from 64.191.3.99: bytes=32 time=50ms TTL=246

    From Edinburgh, UK:

    PING sdsym.com (64.191.3.99) from x.x.x.x : 56(84) bytes of data.
    64 bytes from 64.191.3.99: icmp_seq=0 ttl=238 time=112.812 msec
    64 bytes from 64.191.3.99: icmp_seq=1 ttl=238 time=114.815 msec
    64 bytes from 64.191.3.99: icmp_seq=2 ttl=238 time=113.781 msec
    64 bytes from 64.191.3.99: icmp_seq=3 ttl=238 time=151.912 msec

  6. #6
    Join Date
    Sep 2000
    Location
    New Jersey, U.S.A.
    Posts
    354
    09/06/02 14:54:41 ping sdsym.com
    Ping sdsym.com (64.191.3.99) ...
    1 Addr:64.191.3.99, RTT: 71ms, TTL: 249
    2 Addr:64.191.3.99, RTT: 71ms, TTL: 249
    3 Addr:64.191.3.99, RTT: 72ms, TTL: 249
    4 Addr:64.191.3.99, RTT: 74ms, TTL: 249
    5 Addr:64.191.3.99, RTT: 71ms, TTL: 249
    6 Addr:64.191.3.99, RTT: 72ms, TTL: 249
    7 Addr:64.191.3.99, RTT: 71ms, TTL: 249
    8 Addr:64.191.3.99, RTT: 72ms, TTL: 249
    9 Addr:64.191.3.99, RTT: 70ms, TTL: 249
    10 Addr:64.191.3.99, RTT: 71ms, TTL: 249


    1 65.173.80.1 48ms 47ms 47ms TTL: 0 (user1.XXXX.nj.sprint-hsd.net ok)
    2 207.14.188.2 47ms 48ms 49ms TTL: 0 (user2.XXXX.nj.sprint-hsd.net ok)
    3 144.228.181.41 56ms 52ms 53ms TTL: 0 (sl-gw16-pen-10-0.sprintlink.net ok)
    4 144.232.5.93 53ms 52ms 52ms TTL: 0 (sl-bb25-pen-0-0.sprintlink.net ok)
    5 144.232.5.6 52ms 52ms 52ms TTL: 0 (sl-gw1-pen-10-0.sprintlink.net ok)
    6 144.228.171.178 70ms 68ms 70ms TTL: 0 (sl-hostnoc-1-0.sprintlink.net ok)
    7 64.191.3.99 74ms 71ms 71ms TTL:249 (sdsym.com ok)
    Last edited by RotoHost; 09-06-2002 at 02:38 PM.
    Jim
    RotoHOST.com
    webhosting solutions for e-Business

  7. #7
    Join Date
    Sep 2001
    Location
    Clifton Park, NY
    Posts
    925
    Im getting about 75% packet loss to it right now.

    -Brendan

  8. #8
    64 bytes from 64.191.3.99: icmp_seq=0 ttl=241 time=130.999 msec
    64 bytes from 64.191.3.99: icmp_seq=1 ttl=241 time=131.643 msec
    64 bytes from 64.191.3.99: icmp_seq=2 ttl=241 time=132.889 msec

    --- sdsym.com ping statistics ---
    15 packets transmitted, 4 packets received, 73% packet loss
    round-trip min/avg/max/mdev = 129.960/131.372/132.889/1.150 ms


    very bad.,....

  9. #9
    Join Date
    Mar 2002
    Location
    England
    Posts
    2,014
    So are all the stats bad? I guess it would make sense for the slow loading times?
    <?php include_once('signature'); ?>

  10. #10
    Join Date
    Mar 2002
    Location
    England
    Posts
    2,014
    Bump, I'm getting these slow loading times again !

    What should I say to my host when I Email them?
    <?php include_once('signature'); ?>

  11. #11
    Ask for Traceroutes - not for Pings. Show your host the traceroutes, they can see the problem that way. Chances are its in one of their upstream providers and you will get a response like this:

    "Thanks for your message. We are aware of the problem and are fixing it."

    And hopefully, if you are lucky:
    "We expect the problem to fixed within xx hours."
    Last edited by refcom; 09-11-2002 at 03:56 PM.
    Travis Doherty
    Web Hosting Services
    http://www.referable.com/

  12. #12
    BTW - Here is my Traceroute and some pings for reference:

    (Hop 1 and 2 deleted so I don't promote myself.)
    3 ge6-0-core1.nyc1.globix.net (209.10.1.129) 1.054 ms 1.085 ms 1.093 ms
    4 ge4-0-peer3.nyc1.globix.net (209.10.12.114) 1.098 ms 1.124 ms 4.435 ms
    5 POS2-2.GW12.NYC4.ALTER.NET (157.130.22.237) 1.435 ms 6.996 ms 8.438 ms
    6 505.at-6-1-0.XR4.NYC4.ALTER.NET (152.63.22.78) 1.053 ms 1.414 ms 1.265 ms
    7 0.so-4-0-0.TL1.NYC9.ALTER.NET (152.63.0.173) 2.339 ms 3.259 ms 1.444 ms
    8 0.so-6-0-0.TL1.DCA8.ALTER.NET (152.63.3.198) 5.054 ms 7.612 ms 6.939 ms
    9 0.so-5-0-0.XL1.DCA8.ALTER.NET (152.63.25.38) 6.380 ms 7.711 ms 6.330 ms
    10 289.at-6-1-0.XR1.TCO1.ALTER.NET (152.63.39.246) 9.786 ms 7.810 ms 8.112 ms
    11 193.ATM5-0.GW8.PHL1.ALTER.NET (152.63.39.201) 9.653 ms 12.863 ms 11.722 ms
    12 * * *
    13 64.191.3.99 (64.191.3.99) 14.198 ms 5.686 ms 14.068 ms

    --- sdsym.com ping statistics ---
    43 packets transmitted, 43 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 9.711/14.685/51.930/6.229 ms

    That's not bad if you ask me - but I could be taking a different route than you are to the servers.
    Travis Doherty
    Web Hosting Services
    http://www.referable.com/

  13. #13
    Join Date
    Mar 2002
    Location
    England
    Posts
    2,014
    Well my site's currently down, I emailed my host...
    <?php include_once('signature'); ?>

  14. #14
    Join Date
    May 2002
    Location
    South Dakota
    Posts
    59
    looks okay
    Last edited by RichTek; 09-11-2002 at 04:31 PM.
    Rich D.
    EBS

  15. #15
    Join Date
    Nov 2001
    Posts
    852
    Loads good for me

  16. #16
    Join Date
    Feb 2002
    Posts
    3,727
    From Singapore:

    Pinging sdsym.com [64.191.3.99] with 32 bytes of data:

    Reply from 64.191.3.99: bytes=32 time=392ms TTL=234
    Reply from 64.191.3.99: bytes=32 time=391ms TTL=234
    Reply from 64.191.3.99: bytes=32 time=391ms TTL=234
    Reply from 64.191.3.99: bytes=32 time=391ms TTL=234

    Ping statistics for 64.191.3.99:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 391ms, Maximum = 392ms, Average = 391ms
    Have you Floble'd today?

  17. #17
    Pinging sdsym.com [64.191.3.99] with 32 bytes of data:

    Reply from 64.191.3.99: bytes=32 time=46ms TTL=240
    Reply from 64.191.3.99: bytes=32 time=31ms TTL=240
    Reply from 64.191.3.99: bytes=32 time=31ms TTL=240
    Reply from 64.191.3.99: bytes=32 time=32ms TTL=240
    Reply from 64.191.3.99: bytes=32 time=32ms TTL=240
    Reply from 64.191.3.99: bytes=32 time=32ms TTL=240


    Ping Statistic :
    Packet Sent = 6
    Packet Received = 6
    Lost = 0 <0% loss>

    Approximate round trip times
    in milli-seconds :
    Minimum = 31
    Maximum = 46
    Average = 34
    www.rackfive.com
    Aquired by Data Provider LLC.

  18. #18
    N9ne:

    Do yourself a favour and set yourself up with some monitoring services. I won't list any here, they are easy enough to find online. You should be able to find a decent free one that checks every few hours and reports downtime.

    Make sure you find one that checks from multiple locations.

    This will help you to establish trust in your hosting company, you will know that when things do go wrong they will fix them. If you can't start to trust them based on watching their average downtime frequency and the average window length, use the same process to monitor other hosts and decide which one you would like to transfer too (and of course your normal process of checking support, etc..)
    Travis Doherty
    Web Hosting Services
    http://www.referable.com/

  19. #19
    Join Date
    Sep 2002
    Location
    perl -le '$_=`man perlfaq1`;print/"(j.*)"/'
    Posts
    280
    AlterNet hasn't exactly been "OK" in the past 2 years. If Nocster is relying solely on their AlterNet cage, I feel sorry for them.

    100mbps from CommuniTech, MO, U.S.:
    12 64.191.3.99 (64.191.3.99) 45.144 ms 44.738 ms 44.797 ms

    100mbps from Cogent, TX, U.S.:
    15 64.191.3.99 (64.191.3.99) 50.875 ms 50.516 ms 50.128 ms

    I expected Cogent to do better.
    Richard Ward
    1 NET LANE, LLC.
    http://www.1NL.net
    The low cost data center.

  20. #20
    Join Date
    Jun 2002
    Location
    The Netherlands
    Posts
    393
    From the Netherlands - Amsterdam:

    Pinging 64.191.3.99 with 32 bytes of data:

    Reply from 64.191.3.99: bytes=32 time=95ms TTL=241
    Reply from 64.191.3.99: bytes=32 time=96ms TTL=241
    Reply from 64.191.3.99: bytes=32 time=96ms TTL=241
    Reply from 64.191.3.99: bytes=32 time=107ms TTL=241

    Ping statistics for 64.191.3.99:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 95ms, Maximum = 107ms, Average = 98ms

    Looks good to me
    Alexander

  21. #21
    Join Date
    Apr 2002
    Location
    England, UK
    Posts
    734
    From the UK

    Pinging sdsym.com [64.191.3.99] with 32 bytes of data:

    Reply from 64.191.3.99: bytes=32 time=107ms TTL=242
    Reply from 64.191.3.99: bytes=32 time=107ms TTL=242
    Reply from 64.191.3.99: bytes=32 time=108ms TTL=242
    Reply from 64.191.3.99: bytes=32 time=109ms TTL=242

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

  22. #22
    Join Date
    Aug 2002
    Location
    Canada
    Posts
    83
    You can use www.traceroute.org for selfserve pings from around the world.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •