High pings again

Started by glen, Jul 20, 2009, 10:34:43

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Baz


psp83

Well i've given it a good test tonight, Pings stayed around 13-14ms.

Hope it stays that way!

Glenn

Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

Things have now steadied out for me, and it doesn't get much better than this!

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=10ms TTL=59
Reply from 212.69.36.10: bytes=32 time=10ms TTL=59

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

Throughput is the maximum possible for my profile as well. :thumb:

Steve

The ping to ping variability seems to be much less at present
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

It certainly does. It's what I'd call rock solid at present.

psp83

Same here :

PING 212.69.36.10 (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=60 time=10.0 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=60 time=10.0 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=60 time=10.0 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=60 time=10.0 ms

--- 212.69.36.10 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 10.0/10.0/10.0 ms

Aaron

Rebooted router now, went from .55 to .99 on IP and getting a ping of 23-25, pretty nice for an interleaved line! It used to be 27-30ms :thumb:
IDNet Home Pro ADSL2+ 4Mbps | Billion BiPAC 7800N

wecpcs

Quote from: Sebby on Nov 02, 2009, 22:32:09
Things have now steadied out for me, and it doesn't get much better than this!

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59
Reply from 212.69.36.10: bytes=32 time=10ms TTL=59
Reply from 212.69.36.10: bytes=32 time=10ms TTL=59

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

Throughput is the maximum possible for my profile as well. :thumb:

Mine is very similar now that I have had interleaving turned off and on the new Hostlink. I also now have my max sync of 8128 back, just waiting for my profile now to catch up currently on 6500 (always used to be 7150).

C:\Users\Colin>ping www.idnet.net

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=11ms TTL=59

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

Simon

Nice to see some happy bunnies at last!  :thumb:
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

cavillas

I changed as well  ;D and I have interleaving on.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59

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

------
Alf :)

Ray

This is much better.  :thumb:

[attachment deleted by admin]
Ray
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

zappaDPJ

You should change the thread title to be honest. 'Very low pings again' would be more apt  :laugh:
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Fox

My pings are the best I have seen for a long time

C:\Users\Fox>ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59

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


but..............my bandwidth sucks, I got less than half a meg on the DSL Zone speed test and 0.7 meg on ThinkBroadband. Ran BT speedtester  and

Download speedachieved during the test was - 2732 Kbps
For your connection, the acceptable range of speeds is 600-7150 Kbps.
Additional Information:
Your DSL Connection Rate :8128 Kbps(DOWN-STREAM), 448 Kbps(UP-STREAM)
IP Profile for your line is - 7150 Kbps

Whats going on? I normally get 6-7 meg  :bawl:
True power doesn't lie with the people who cast the votes, it lies with the people who count them



Glenn

Fox, call support and let them know, there maybe something that they can do straight away to fix the issue
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

I am sure speedtest.net got silly since I changed to the hostlink, It thinks my preferred server is in Dublin, how strange.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

It's the Guinness, Steve.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

Performance is now fantastic; solid 10ms pings and and maximum throughput at any time of the day. This is the IDNet I remember. :)

Baz

ok explain how some people get good pings and others bad.mine havent changed much since switching to the new hostlink but i see that some people have great improvements

Glenn

Mine haven't change either Baz, but I was starting at a low base, 22/23ms
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

Pity I don't have a stable line to benefit from the ping.
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

wecpcs

Quote from: Sebby on Nov 03, 2009, 18:56:35
Performance is now fantastic; solid 10ms pings and and maximum throughput at any time of the day. This is the IDNet I remember. :)

I wish mine was. My pings are now fantastic, but my download speeds have deteriorated rapidly since this mornings excellent speeds of about 6.3Mb when my fast mode was enabled, but now from around 4:30pm they are all over the place from about 2-4Mb, totally unstable. Not very happy, this IS NOT the Idnet I remember, when until up to a few weeks ago I used to get 6-7+ 24/7.

Colin

psp83

Quote from: Baz on Nov 03, 2009, 20:08:05
ok explain how some people get good pings and others bad.mine havent changed much since switching to the new hostlink but i see that some people have great improvements

I always had low pings (around 14ms) until recent problems. Mines only dropped about 2ms since the new hostlink.

Baz

not complaining just wondering why.

Simon

Quote from: wecpcs on Nov 03, 2009, 20:31:27
I wish mine was. My pings are now fantastic, but my download speeds have deteriorated rapidly since this mornings excellent speeds of about 6.3Mb when my fast mode was enabled, but now from around 4:30pm they are all over the place from about 2-4Mb, totally unstable. Not very happy, this IS NOT the Idnet I remember, when until up to a few weeks ago I used to get 6-7+ 24/7.

Colin

:argh:  Just when we thought things were getting better! 
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.