Speed Down To USA Servers ?

[curly]

Hi All
im having probs with speed got 10 meg and 4 the past 3 weeks d/loading from usa newshosting am only getting 1/2 speed . done a speed test and london getting full speed anything out the country is crap...everything was fine 3 weeks ago can anyone throw some light on this....cheers

[The Jackal]

US links look a little slower than usual.

From home the hop to the states took a whopping 146ms
From the datacentre it took 70ms (I'm sure the average is 30ms)

home
5: pc-62-30-250-54-ha.blueyonder.co.uk (62.30.250.54) 40.579ms
6: 213.228.222.10 (213.228.222.10) asymm 7 186.542ms

dc
3 ae0-81.lon11.ip.tiscali.net (213.200.77.113) 0.749 ms 0.622 ms 0.682 ms
4 so-7-0-0.was10.ip.tiscali.net (213.200.80.110) 75.096 ms so-1-0-0.was10.ip.

BTW whats the hostname or ip of the address you are connecting to ?

[curly]

hi....its unlimited.newshosting.com....how do u get the ip address ?

[The Jackal]

I'm getting severe packet loss within the states nothing u can do now till they fix it

ping unlimited.newshosting.com
PING unlimited.newshosting.com (63.218.45.254) from xxxxxxxx : 56(84) bytes of data.
64 bytes from 63.218.45.254: icmp_seq=1 ttl=59 time=73.6 ms
64 bytes from 63.218.45.254: icmp_seq=2 ttl=59 time=76.8 ms
64 bytes from 63.218.45.254: icmp_seq=3 ttl=58 time=77.2 ms
64 bytes from 63.218.45.254: icmp_seq=4 ttl=59 time=76.2 ms
64 bytes from 63.218.45.254: icmp_seq=5 ttl=59 time=72.8 ms
64 bytes from 63.218.45.254: icmp_seq=6 ttl=59 time=72.5 ms
64 bytes from 63.218.45.254: icmp_seq=7 ttl=59 time=72.7 ms
64 bytes from 63.218.45.254: icmp_seq=8 ttl=59 time=72.5 ms
64 bytes from 63.218.45.254: icmp_seq=9 ttl=58 time=74.1 ms
64 bytes from 63.218.45.254: icmp_seq=12 ttl=58 time=82.5 ms
64 bytes from 63.218.45.254: icmp_seq=15 ttl=59 time=76.7 ms
64 bytes from 63.218.45.254: icmp_seq=16 ttl=58 time=76.2 ms
64 bytes from 63.218.45.254: icmp_seq=16 ttl=58 time=76.2 ms
64 bytes from 63.218.45.254: icmp_seq=17 ttl=59 time=75.4 ms
64 bytes from 63.218.45.254: icmp_seq=18 ttl=58 time=75.7 ms
64 bytes from 63.218.45.254: icmp_seq=19 ttl=59 time=75.5 ms
64 bytes from 63.218.45.254: icmp_seq=20 ttl=59 time=75.3 ms
64 bytes from 63.218.45.254: icmp_seq=21 ttl=59 time=74.8 ms

--- unlimited.newshosting.com ping statistics ---
21 packets transmitted, 17 received, 19% loss, time 20155ms
rtt min/avg/max/mdev = 72.518/75.368/82.505/2.364 ms

[curly]

Thanks.. who needs to fix it ?.....it seems to speed up after midnight at the moment am getting average 450k/sec

[The Jackal]

Thanks.. who needs to fix it ?.....it seems to speed up after midnight at the moment am getting average 450k/sec

This will be fixed by the ISPs who manage those links as far as we are concerned its an invisible operation they'll prolly be working on it as we speak.

[curly]

cheers mate i'll keep an eye on it as u can imagine d/loads r taking considerably longer...i cant fault the telewest service up 2 now but i didnt want 2 rant at them if it's not there fault...thanks

[Druchii]

It happens form time to time, funnily i get better pings to germany and france than i do to London...

[AntiSilence]

Yikes:

Pinging unlimited.newshosting.com [63.218.45.254] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Reply from 63.218.45.254: bytes=32 time=134ms TTL=54

Ping statistics for 63.218.45.254:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 134ms, Maximum = 134ms, Average = 134ms

[Druchii]

Pinging unlimited.newshosting.com [63.218.45.254] with

Reply from 63.218.45.254: bytes=32 time=105ms TTL=46
Reply from 63.218.45.254: bytes=32 time=106ms TTL=46
Reply from 63.218.45.254: bytes=32 time=110ms TTL=46
Reply from 63.218.45.254: bytes=32 time=119ms TTL=46

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

Not bad :)

[AntiSilence]

I'm getting better results now.. 0% packet loss, unlike before.

[Druchii]

Could be fixed then :D