Forums Web Site News Network survey

Viewing 24 posts - 26 through 49 (of 49 total)
  • Author
    Posts
  • #1228522
    MadPsy
    Participant

    BT probably use Level3 so would go something like… UK – NYC – Chicago – Denver – Seattle

    #1228523
    MadPsy
    Participant

    Final thought of the night… ๐Ÿ™‚ If you want a /really/ nice network then find someone who provides anycast and a nice CDN. Then you end up with one IP routed to the closest point to the end user. An example being the IP 8.8.8.8 which isn’t fixed to one geographical location, it routes to various places depending where the user is, very nice.

    #1228496
    Techno Viking
    Participant

    I’ve looked at those, we can’t afford them… ๐Ÿ™‚

    #1228497
    Techno Viking
    Participant

    @madscientist 395893 wrote:

    When you’re talking distances like this, especially for streaming etc then jitter rather than latency is the biggest problem, although it’s usually only protocols like SIP for VoIP etc that are affected.

    Almost all transit from the UK to the US will go via NYC, so the closer you get to NYC the better, when you jump to Dallas expect at least +30-40ms on latency.

    Washington is an option…

    #1228498
    Techno Viking
    Participant

    In fact I’ve been wrong, washington is reporting the better times of course which makes proper sense. Doo’h!

    #1228514
    siwhite
    Participant

    @General Lighting 395793 wrote:

    as at 2010-08-21 12:50 uk local time the first of the 3 servers is inaccessible

    67.228.118.51 ping statistics —
    3 packets transmitted, 0 received, 100% packet loss, time 1999ms

    with regard to the other two

    — 67.228.118.21 ping statistics —
    4 packets transmitted, 4 received, 0% packet loss, time 3002ms
    rtt min/avg/max/mdev = 172.845/173.754/174.573/0.614 ms, pipe 2

    — 208.43.118.51 ping statistics —
    4 packets transmitted, 4 received, 0% packet loss, time 3003ms
    rtt min/avg/max/mdev = 104.773/105.320/105.944/0.476 ms, pipe 2

    @Dr Bunsen 395800 wrote:

    Interesting can you try the failed one again?

    @General Lighting 395802 wrote:

    no luck – 67.228.118.51 is inaccessible from both my home IP address and logging in remotely to my office PC (7 miles away)

    It’s 66.228.118.51 for the first one ๐Ÿ˜‰

    Anyway, here’s my results:

    — 66.228.118.51 ping statistics —
    10 packets transmitted, 10 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 125.421/127.022/131.200/1.496 ms

    — 67.228.118.21 ping statistics —
    10 packets transmitted, 10 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 168.513/168.959/169.364/0.300 ms

    — 208.43.118.51 ping statistics —
    10 packets transmitted, 10 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 100.733/102.156/104.850/1.303 ms

    #1228526
    pixel_pirate
    Participant

    from South Africa:

    — 66.228.118.51 ping statistics —
    22 packets transmitted, 21 packets received, 4.5% packet loss
    round-trip min/avg/max/stddev = 309.494/317.713/332.764/7.221 ms
    Brett-Arthurs-MacBook:~ brettarthur$

    — 67.228.118.21 ping statistics —
    36 packets transmitted, 36 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 383.575/393.535/415.536/7.459 ms
    Brett-Arthurs-MacBook:~ brettarthur$

    — 208.43.118.51 ping statistics —
    37 packets transmitted, 36 packets received, 2.7% packet loss
    round-trip min/avg/max/stddev = 275.039/284.063/309.065/6.931 ms
    Brett-Arthurs-MacBook:~ brettarthur$

    #1228509
    noname
    Participant

    Ping statistics for 66.228.118.51:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% los
    Approximate round trip times in milli-seconds:
    Minimum = 168ms, Maximum = 169ms, Average = 168ms

    Ping statistics for 67.228.118.21:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss
    Approximate round trip times in milli-seconds:
    Minimum = 199ms, Maximum = 200ms, Average = 199ms

    Ping statistics for 208.43.118.51:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% los
    Approximate round trip times in milli-seconds:
    Minimum = 122ms, Maximum = 123ms, Average = 122ms

    ๐Ÿ™‚

    #1228524
    MadPsy
    Participant

    @Dr Bunsen 395901 wrote:

    In fact I’ve been wrong, washington is reporting the better times of course which makes proper sense. Doo’h!

    Aren’t most users in the UK? Just wondering why you’re hosting in the US?

    #1228499
    Techno Viking
    Participant

    Because the level of service isn’t available at a price we’re able to afford that I’m aware of in the Uk or europe…

    #1228525
    MadPsy
    Participant

    What kind of level of service are you after? i.e what’s the spec of machine etc you’re looking for…

    #1228500
    Techno Viking
    Participant

    I’ll let you know by pm… ๐Ÿ™‚

    #1228529
    buddmeister
    Participant

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.
    C:UsersBuddmeister>ping 66.228.118.51
    Pinging 66.228.118.51 with 32 bytes of data:
    Reply from 66.228.118.51: bytes=32 time=148ms TTL=244
    Reply from 66.228.118.51: bytes=32 time=148ms TTL=244
    Reply from 66.228.118.51: bytes=32 time=148ms TTL=244
    Reply from 66.228.118.51: bytes=32 time=148ms TTL=244
    Ping statistics for 66.228.118.51:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 148ms, Maximum = 148ms, Average = 148ms

    C:UsersBuddmeister>ping 67.228.118.21
    Pinging 67.228.118.21 with 32 bytes of data:
    Reply from 67.228.118.21: bytes=32 time=203ms TTL=48
    Reply from 67.228.118.21: bytes=32 time=203ms TTL=48
    Reply from 67.228.118.21: bytes=32 time=202ms TTL=48
    Reply from 67.228.118.21: bytes=32 time=202ms TTL=48
    Ping statistics for 67.228.118.21:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 202ms, Maximum = 203ms, Average = 202ms

    C:UsersBuddmeister>ping 208.43.118.51
    Pinging 208.43.118.51 with 32 bytes of data:
    Reply from 208.43.118.51: bytes=32 time=106ms TTL=56
    Reply from 208.43.118.51: bytes=32 time=105ms TTL=56
    Reply from 208.43.118.51: bytes=32 time=104ms TTL=56
    Reply from 208.43.118.51: bytes=32 time=105ms TTL=56
    Ping statistics for 208.43.118.51:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 104ms, Maximum = 106ms, Average = 105ms

    I am in the midlands UK
    with a 6750kbps downstream 1240kbps upstream. Hope u find out what you need. Seems fine to me. Do you need any traceroutes doing too?

    #1228527
    dottee
    Participant

    Pinging 66.228.118.51 with 32 bytes of data:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 279ms, Maximum = 292ms, Average = 287ms

    Pinging 67.228.118.21 with 32 bytes of data:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 256ms, Maximum = 302ms, Average = 281ms

    Pinging 208.43.118.51 with 32 bytes of data:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 329ms, Maximum = 358ms, Average = 339ms

    #1228501
    Techno Viking
    Participant

    @dottee 396118 wrote:

    Pinging 66.228.118.51 with 32 bytes of data:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 279ms, Maximum = 292ms, Average = 287ms

    Pinging 67.228.118.21 with 32 bytes of data:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 256ms, Maximum = 302ms, Average = 281ms

    Pinging 208.43.118.51 with 32 bytes of data:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 329ms, Maximum = 358ms, Average = 339ms

    Where is this from?

    #1228531
    Graetar
    Participant

    From Prague, Czech Republic:

    Pinging 66.228.118.51 with 32 bytes of data:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    Pinging 67.228.118.21 with 32 bytes of data:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    Pinging 208.43.118.51 with 32 bytes of data:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss).

    Sorry, no luck, even if I try to repeat the pinging… :frown:

    #1228485
    Anonymous

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

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

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

    #1228502
    Techno Viking
    Participant

    @Graetar 396125 wrote:

    From Prague, Czech Republic:

    Pinging 66.228.118.51 with 32 bytes of data:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    Pinging 67.228.118.21 with 32 bytes of data:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    Pinging 208.43.118.51 with 32 bytes of data:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss).

    Sorry, no luck, even if I try to repeat the pinging… :frown:

    Do you have a firewall running?

    #1228528
    Barksdale
    Participant

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

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

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

    #1228518
    DaftFader
    Participant

    @Dr Bunsen 396133 wrote:

    Do you have a firewall running?

    Also you must be connected to the internet at time of pinging (just encase lol)

    #1228486
    Anonymous

    Pinging Party Vibe is the Meeting Place for Party People [74.86.126.163] with 32 bytes of data:

    Reply from 74.86.126.163: bytes=32 time=76ms TTL=52
    Reply from 74.86.126.163: bytes=32 time=84ms TTL=52
    Reply from 74.86.126.163: bytes=32 time=104ms TTL=52
    Reply from 74.86.126.163: bytes=32 time=74ms TTL=52

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

    #1228503
    Techno Viking
    Participant

    You can ping our new host here: 173.193.228.66. Should be up and running properly tomorrow, it’s all in place except for DNS and the radio… ๐Ÿ™‚

    Reply from 173.193.228.66: bytes=32 time=249ms TTL=54
    Reply from 173.193.228.66: bytes=32 time=233ms TTL=54
    Reply from 173.193.228.66: bytes=32 time=234ms TTL=54
    Reply from 173.193.228.66: bytes=32 time=234ms TTL=54

    #1228487
    Anonymous

    ping statistics for 66.228.118.51
    packets sent 4, received 4, lost 0
    approximate round trip in milli-seconds
    minimum 183ms, maximun 1172ms, average 430ms

    ping statistics for 67.228.118.21
    packets sent 4, received 4 lost 0
    approximate round trip in milli-seconds
    minimum 173ms, maximum 176ms, average 174ms

    ping statistics for 208.43.118.51
    packets sent 4, received 4, lost 0
    approximate round trip in milli-seconds
    minimum 182ms, maximum 187ms, average 183ms

    #1228532
    Graetar
    Participant

    @Dr Bunsen 396133 wrote:

    Do you have a firewall running?

    Yeap, that could be the case. Should I switch it off? Btw, Nmap is able to ping it somehow, Iโ€™m not able to get the trip times, however.

    @DaftFader 396364 wrote:

    Also you must be connected to the internet at time of pinging (just encase lol)

    How could I forget such a thing? ๐Ÿ˜€

Viewing 24 posts - 26 through 49 (of 49 total)
  • You must be logged in to reply to this topic.

Forums Web Site News Network survey