Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 8128 kbps(DOWN-STREAM), 832 kbps(UP-STREAM)
IP profile for your line is - 7150 kbps
Actual IP throughput achieved during the test was - 3360 kbps
danni@Matilda:~$ ping idnet.net -c10
PING idnet.net (212.69.36.10) 56(84) bytes of data.
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=1 ttl=59 time=137 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=2 ttl=59 time=167 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=3 ttl=59 time=141 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=4 ttl=59 time=138 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=5 ttl=59 time=172 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=6 ttl=59 time=173 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=7 ttl=59 time=149 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=8 ttl=59 time=152 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=9 ttl=59 time=178 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=10 ttl=59 time=175 ms
--- idnet.net ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
rtt min/avg/max/mdev = 137.247/158.632/178.383/15.559 ms
Erm, suggestions? My noise margin and stuff are fine. I can see that others are having the ping problems, but the speed is what worries me more.
Same here Danni
Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 8128 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 7150 kbps
Actual IP throughput achieved during the test was - 2559 kbps
If you wish to discuss these results please contact your ISP.
Call IDNet and report the issue
ya not the only one that is more worried about the thoughput
Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 5824 kbps(DOWN-STREAM), 832 kbps(UP-STREAM)
IP profile for your line is - 5000 kbps
Actual IP throughput achieved during the test was - 1722 kbps
*** now here comes the part where someone blames it on BT*****
/me blames it on BT :P
now how did i know you would go and do a thing like that danni :whistle:
Leave me alone :(
Should I contact IDNet?
Quote from: Danni on Jul 01, 2009, 16:36:15
Leave me alone :(
Should I contact IDNet?
The more who do maybe the more they will look and see if its a BT issue or a capacity issue, whichever it is it is best sorted out Danni, thats how I see it.
Okay, emailing them now.
While we're on it, I'm now blaming the flooding and lightening strikes on the Metro system, because I want to blame silly things while I'm getting it sorted :P
Quote from: Danni on Jul 01, 2009, 16:40:17
Okay, emailing them now.
While we're on it, I'm now blaming the flooding and lightening strikes on the Metro system, because I want to blame silly things while I'm getting it sorted :P
You have storms? Its just searing sun down on the south coast :( to hot
aggreed really annoying having speed issues when im not allowed to dirve or go to work
im going to blame it on a capacitor hidden away within somewhere in a Idnet router that isnt even conected to the network and is just producing bad karma
Indeed- the storms have passed over me, but I think that's to blame for Colin's lower sync speed :)
I am so glad I missed college today- would have been stranded in South Shields as I don't cope well with buses and getting two home would have been too much.
could explain my low sync but doesnt explain my throughput
Quote from: Danni on Jul 01, 2009, 16:44:07
Indeed- the storms have passed over me, but I think that's to blame for Colin's lower sync speed :)
I am so glad I missed college today- would have been stranded in South Shields as I don't cope well with buses and getting two home would have been too much.
I can understand that, I never did like buses much Danni, to many people I get claustrophobic, especially in heat
I think anyone with speed issues should contact IDNet directly. :)
Had a response from Simon:
QuoteHi Danni
We're seeing a high volume of traffic right now and are working to re-balance our Centrals.
regards
Simon
I am hoping this means it will be sorted soon :)
yea once the tennis is finnished
you got it sorted yet Danni/Colin.
are us folk up here all on GW5?
seems ok for me
Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 8128 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 7150 kbps
Actual IP throughput achieved during the test was - 6404 kbps
pings are still all over the place
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\colin>ping idnet.net
Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=186ms TTL=59
Reply from 212.69.36.10: bytes=32 time=168ms TTL=59
Reply from 212.69.36.10: bytes=32 time=175ms TTL=59
Reply from 212.69.36.10: bytes=32 time=165ms 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 = 165ms, Maximum = 186ms, Average = 173ms
C:\Documents and Settings\colin>
sadly nope im on dsl 4
at least it isnt affecting my watching of youtube videos
I bet the load balancing on the centrals has gone haywire with extra traffic.Did we ever hear whether gw6 was resolved?
I don't think we did, Steve, but I assume the issue was resolved when users started moving over to ADSL2+, hence relieving the unanticipated strain on gw6.
My Pings appear to be okay (well better than you were getting) :
C:\Documents and Settings\John>ping idnet.net -n 10
Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59
Reply from 212.69.36.10: bytes=32 time=39ms TTL=59
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59
Reply from 212.69.36.10: bytes=32 time=37ms TTL=59
Reply from 212.69.36.10: bytes=32 time=41ms TTL=59
Reply from 212.69.36.10: bytes=32 time=37ms TTL=59
Reply from 212.69.36.10: bytes=32 time=28ms TTL=59
Reply from 212.69.36.10: bytes=32 time=240ms TTL=59
Reply from 212.69.36.10: bytes=32 time=124ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Ping statistics for 212.69.36.10:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 240ms, Average = 65ms
Have you tried them again recently ?
my ping look like they are getting better down to 60ms still not great compaired to the 60ms i normally get but that could just be my line as it seems to be misbehaving
I'm on DSL4 which I believe is part of GW5, I'm pinging 212.69.40.3 at around 24ms
Quote from: Glenn on Jul 01, 2009, 20:17:03
I'm on DSL4 which I believe is part of GW5, I'm pinging 212.69.40.3 at around 24ms
I am pinging idnet.net at 31ms which is about the norm for me now.
Please continue here (http://www.idnetters.co.uk/forums/index.php?topic=14931.0), as IDNet have been referred to the other thread. :)