Is there any reported problems today?
I've just been disconnected (reconnected at same sync) and now got very high pings and slow speed.
Nothing I've heard of, Paul, but if you had a resync it would suggest a burst of noise or BT work.
Connection fully down now :(
support say nothing wrong with the line / connection.
Have you checked at the test socket, Paul?
Not yet. Can't get to it at the mo. To much junk infront of it at mo.
I've done a router reset and it still it won't connect. Won't even connect to bt_test@startup_domain like support told me to try.
It's possibly a dead router, of course. Do you have one you could swap?
Picking a spare one up on my way back.
I've left the router of for now and hope that fixes any problems when I get back.
:fingers:
Let us know how it goes, will you?
Just got back in, turned the router on and it connected.
still getting very low speeds and high ping though :(
What do the stats look like? Also, please run a BT speed test as the profile may have taken a hit.
Speed has gone up abit now. Still not right though.
Download speedachieved during the test was - 2842 Kbps
For your connection, the acceptable range of speeds is 600-7150 Kbps.
Additional Information:
Your DSL Connection Rate :5504 Kbps(DOWN-STREAM), 448 Kbps(UP-STREAM)
IP Profile for your line is - 4000 Kbps
I was getting around 3900 Kbps before my troubles.
ADSL Link Downstream Upstream
Connection Speed 5504 kbps 448 kbps
Line Attenuation 39 db 12.5 db
Noise Margin 11 db 26 db
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 123 ms 113 ms 131 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 166 ms 162 ms 145 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 133 ms 134 ms 147 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 145 ms 139 ms 152 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 131 ms 135 ms 144 ms www.idnet.net [212.69.36.10]
Trace complete.
Tracing route to psp83.co.uk [77.92.89.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 129 ms 117 ms 120 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 156 ms 152 ms 470 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 141 ms 149 ms 155 ms lonap1.enta.net [193.203.5.134]
5 149 ms 133 ms 129 ms te5-2.gs1.core.enta.net [87.127.236.42]
6 168 ms 155 ms 138 ms te1-1.interxion.core.enta.net [87.127.236.86]
7 164 ms 159 ms 147 ms 78-33-30-154.static.enta.net [78.33.30.154]
8 149 ms 135 ms 140 ms atlas.safeukdns.net [77.92.89.1]
Trace complete.
Everything seems to be back to normal now.
Speed is backup to around 3900 Kbps and pings back low.
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 14 ms 14 ms 15 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 445 ms 109 ms 162 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 14 ms 14 ms 15 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 15 ms 14 ms 16 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 14 ms 14 ms 15 ms www.idnet.net [212.69.36.10]
Trace complete.
Dunno what the hell caused it though.
My speed issues continue as well. Speed variations have increased markedly over the past month or so. My BT Speedtest donstream is down to 1597 Kbps compared with 6300 Kpbs when I checked on Friday afternoon. My pings are as follows:
G idnet.com (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=114.505 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=143.631 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=160.147 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=131.963 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=127.536 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=139.244 ms
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=149.138 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=183.294 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=131.235 ms
64 bytes from 212.69.36.10: icmp_seq=9 ttl=59 time=105.848 ms
--- idnet.com ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 105.848/138.654/183.294/21.148 ms
I am reluctant to keep on re-booting my router. I sense that IdNet is having some capacity issues. Am I right?
Regards
Spoke to soon, High pings again.
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 152 ms 152 ms 143 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 162 ms 165 ms 154 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 158 ms 147 ms 130 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 148 ms 141 ms 141 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 162 ms 168 ms 164 ms www.idnet.net [212.69.36.10]
Trace complete.
Speed has dropped again aswell :(
I have just spoken to Simon at IdNet and he has admitted that they have had problems and they are trying to rebalance the load. At his suggestion (again), I have re-booted my router. This has resulted in a further drop in my downstream speed to 1107 Kbps.
Ping has started...
PING idnet.com (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=163.423 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=181.034 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=159.294 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=151.614 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=172.027 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=118.353 ms
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=144.371 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=163.431 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=183.523 ms
64 bytes from 212.69.36.10: icmp_seq=9 ttl=59 time=153.754 ms
--- idnet.com ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 118.353/159.082/183.523/18.011 ms
I confess that I am unsure what I should do next.
I rebooted my router, speed regained, pings low, 2 mins later. Pings are now getting higher and speeds getting slower
All over the place today, was gunna make a skype call but think i will use the phone insted!
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 58 ms 56 ms 70 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 24 ms 24 ms 28 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 69 ms 87 ms 302 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 68 ms 58 ms 68 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 111 ms 115 ms 103 ms www.idnet.net [212.69.36.10]
Trace complete.
C:\Users\Paul>tracert www.idnet.net
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 69 ms 73 ms 80 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 90 ms 95 ms 84 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 205 ms 135 ms 147 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 114 ms 102 ms 100 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 105 ms 100 ms 100 ms www.idnet.net [212.69.36.10]
Trace complete.
C:\Users\Paul>tracert www.idnet.net
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 19 ms 14 ms 19 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 28 ms 29 ms 30 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 36 ms 36 ms 40 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 57 ms 67 ms 53 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 41 ms 43 ms 40 ms www.idnet.net [212.69.36.10]
Trace complete.
C:\Users\Paul>tracert www.idnet.net
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 16 ms 16 ms 16 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 24 ms 22 ms 20 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 45 ms 28 ms 26 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 22 ms 19 ms 20 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 43 ms 38 ms 28 ms www.idnet.net [212.69.36.10]
Trace complete.
Looks like no arse kicking on xbox tonight aswell :(
I had a power cut at home this morning :eek4:. Router has synced at around usual speed of 6274, but pings have shot up to 150ms. They have been behaving themeselves at 14-15ms for the past few days (after weeks of volatility). Looks like the power-cut imposed reboot has connected me to one of the congested centrals again :'(
I will have a look again this evening, but it seems likely I will have to go through the rebooting saga again until I find that uncongested central :dunno:
I'm just about to give up on pings,
Mines going from 14ms to over 2000 ms.
I understand there was a capacity issue this morning, but that it's now clear. If people are still having speed or ping issues, and a re-boot doesn't cure it, please contact support so that they can look into it for you.
Back up to 4000 Kbps now without any further re-boot. I just wish that IdNet would put out a proper SB on the main website when have problems. It would save them a lot of hassle.
High pings here:
Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=144ms TTL=59
Reply from 212.69.36.10: bytes=32 time=102ms TTL=59
Reply from 212.69.36.10: bytes=32 time=133ms TTL=59
Reply from 212.69.36.10: bytes=32 time=112ms 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 = 102ms, Maximum = 144ms, Average = 122ms
Just rebooted router, which has made pings slightly worse:
Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=148ms TTL=59
Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=151ms TTL=59
Reply from 212.69.36.10: bytes=32 time=149ms 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 = 129ms, Maximum = 151ms, Average = 144ms
Same here, all the pipes seem congested, throughout hasn't been significantly affected though.
Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=95ms TTL=59
Reply from 212.69.36.10: bytes=32 time=154ms TTL=59
Reply from 212.69.36.10: bytes=32 time=149ms TTL=59
Reply from 212.69.36.10: bytes=32 time=128ms TTL=59
Reply from 212.69.36.10: bytes=32 time=139ms TTL=59
Reply from 212.69.36.10: bytes=32 time=115ms TTL=59
Reply from 212.69.36.10: bytes=32 time=132ms TTL=59
Reply from 212.69.36.10: bytes=32 time=173ms TTL=59
Reply from 212.69.36.10: bytes=32 time=116ms TTL=59
Reply from 212.69.36.10: bytes=32 time=121ms 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 = 95ms, Maximum = 173ms, Average = 132ms
All I can do is repeat my advice to contact support.
QuoteWe are seeing high levels of 20CN traffic today and yet one of the VPs on one of our Centrals is only running at 50% utilisation. We are working to balance the traffic across these VPs.
Does the BT speed tester bypass IDNet's network?
BT Speedtest shows good throughput, but all other speedtest sites show very slow throughput:
BT Speedtest
Download speed achieved during the test was - 5950 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
Thinkbroadband throughput 2276.45 Kbps
speedtest bbmax.co.uk 2819 Kbps
speedtest.net Maidenhead server 3.13Mb/s
AFAIK, it doesn't bypass IDNet's network, but I can't find absolute confirmation of that.
TEST1 will determine whether the performance problem experienced by the EU is caused by traffic on the Internet, high utilization of the target application server or whether there is an actual performance problem in either SPs or BTs network.
TEST2 will determine whether the performance problem experienced by the EU is caused by the SPs network or BTs network. This test is only applicable for SPs with BT Central Classic (LNS or LTS) access.
TEST3 will determine whether the performance problem is caused by either the congestion in the access VP, errors at the DSL/ATM layers within the access, or the EU premises.
What ever that means!! But to get to test 2 and 3 performance has to be pretty appalling if anything above 600 is classed by BT as acceptable.
Which implies that test 1 and 2 are using the IDNet network, I guess.
Just restarted my router and ping results are :
Microsoft Windows [Version 6.1.7100]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
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=130ms TTL=59
Reply from 212.69.36.10: bytes=32 time=122ms TTL=59
Reply from 212.69.36.10: bytes=32 time=152ms TTL=59
Reply from 212.69.36.10: bytes=32 time=175ms 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 = 122ms, Maximum = 175ms, Average = 144ms
C:\Users\Steven>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=130ms TTL=59
Reply from 212.69.36.10: bytes=32 time=178ms TTL=59
Reply from 212.69.36.10: bytes=32 time=153ms TTL=59
Reply from 212.69.36.10: bytes=32 time=136ms 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 = 130ms, Maximum = 178ms, Average = 149ms
C:\Users\Steven>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=108ms TTL=59
Reply from 212.69.36.10: bytes=32 time=112ms TTL=59
Reply from 212.69.36.10: bytes=32 time=151ms TTL=59
Reply from 212.69.36.10: bytes=32 time=157ms 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 = 108ms, Maximum = 157ms, Average = 132ms
C:\Users\Steven>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=178ms TTL=59
Reply from 212.69.36.10: bytes=32 time=157ms TTL=59
Reply from 212.69.36.10: bytes=32 time=175ms TTL=59
Reply from 212.69.36.10: bytes=32 time=153ms 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 = 153ms, Maximum = 178ms, Average = 165ms
C:\Users\Steven>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=164ms TTL=59
Reply from 212.69.36.10: bytes=32 time=163ms TTL=59
Reply from 212.69.36.10: bytes=32 time=149ms TTL=59
Reply from 212.69.36.10: bytes=32 time=157ms 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 = 149ms, Maximum = 164ms, Average = 158ms
The service has been like this for over a month now and it's practically useless, if it carries on for much longer I'm going to have to switch to another ISP. I appreciate that it may be problems caused by BT's inferstructure but my friends who use BT's ISP service are getting totally rock solid 30 pings so I don't accept this as the main cause.
This is getting silly. My downstream is now done to just over 1000Kbps on the BTSpeedtest. There is little point in paying extra for a premium service when congestion is as bad as this. I need to speak to Support again.
Download speedachieved during the test was - 1396 Kbps
For your connection, the acceptable range of speeds is 1200-7150 Kbps.
Additional Information:
Your DSL Connection Rate :8128 Kbps(DOWN-STREAM), 832 Kbps(UP-STREAM)
IP Profile for your line is - 7150 Kbps
Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=193ms TTL=59
Reply from 212.69.36.10: bytes=32 time=166ms TTL=59
Reply from 212.69.36.10: bytes=32 time=178ms TTL=59
Reply from 212.69.36.10: bytes=32 time=147ms TTL=59
(http://www.speedtest.net/result/577143114.png) (http://www.speedtest.net)
think ive been hit
been out/work all day and now i cannot login to any web pages ?
server/system all down then ?
My ping was bad last night and didn't settle down until 1am. Just got in from work and its as bad if not worse again. I have powered down my router for half an hour. When I reconnected my ping was back to normal (about 40ms to IDNet) but half an hour later its a bad as ever (ping in excess of 120ms going up to 150ms plus). I just popped round next door and my friends ping is fine and he is with talk talk (urgh). There is no LLU on my exchange so he is on max, the same as me, but hasnt had any problems with ping. He currently pings 42ms to IDNet.
I can only conclude that the problem is with IDNet yet again. For an ISP that says "Our network has the capacity and very low-latency to ensure your Internet traffic, whether you have Broadband, Leased-line or Ethernet connectivity, is delivered with the highest performance that is technically possible". I am getting to the point where I can only conclude that they are at best misleading customers and at worst plain telling lies about their capacity.
The main reason I joined IDNet was for the promise of low pings as I am a semi professional gamer, I do closed beta testing for 2 game companies one of which paid for me to go to the Nvison 08 GeForce LAN in LA. The level of service from IDNet has been a joke for the last couple of months. This has to be a capacity issue even though IDNet I am sure will deny this.
I, and I am sure many others, will be questioning why the hell they are paying top dollar for a service that the company seems either unwilling or unable to provide. Either IDNet sorts this out quickly or people will simply go to another provider and IDNet will find themselves ranked with supanet and the other poor providers who simply do not provide the service they offer.
I am not asking for the earth, simply an internet connection that allows me to game when I want.
See reply #27 above - there's an issue with imbalance again, which should be taken care of automatically, but has not. :(
Quote from: netn00b on Sep 28, 2009, 19:05:37
been out/work all day and now i cannot login to any web pages ?
server/system all down then ?
Nothing's down as far as I know, try re-booting your router, leaving it powered off for at least a couple of minutes, you may have a stale session.
the router has been turned off all day as we do not leave it on.
i connected, started to access a couple of websites, one of which for an order i really need to place tonite and then suddenly it all went blank and getting IE error pages.
the wife has the same on her pc.
i have rebooted the route 2 times since this and i cannot connect to anything. support are not answering due the time of day so i'm left not knowing what the heck is going on or when i am going to get a service which i need now.
Is your router in sync?
in snyc ?
Is it connecting to the exchange? What router is it?
its a netgear 834g.
got some stable and flashing green lights and one yellow flashing one currently.....which i thought was usually green but the router is the other side of the room next to my wifes pc so i rarely actually look it !
If you've got a yellow, there's a good chance the router is not in sync, log into the router interface via your browser and see if you can see connection speeds etc.
Quote from: Rik on Sep 28, 2009, 19:08:36
See reply #27 above - there's an issue with imbalance again, which should be taken care of automatically, but has not. :(
I am sorry Rik but IDNet never suffered from these problems until recently, if they have problems balancing their network why hasnt this happened before in the couple of years I have been with them (I have just checked with my other neighbour who is with AOL and his pings are fine too), strange other ISPs dont seem to suffer from this balancing issue. It just sounds like a poor excuse time and time again for what has to be a capacity issue.
Quote from: Rik on Sep 28, 2009, 19:23:48
If you've got a yellow, there's a good chance the router is not in sync, log into the router interface via your browser and see if you can see connection speeds etc.
umm ok will try to do that if i can.......not sure i remember how and does it not require a password ?
I can't argue with you, I only know what I've been told. Most of the time, there isn't a capacity issue, but of late there seem to have been some 'hotspots' exacerbated by the failure of load balancing to assign connections more evenly. The capacity issue will be addressed in the next few weeks when BT finally deliver the extra capacity that IDNet have been waiting almost a year for, in the form of IPStream Connect, which will allow them to move customers onto the 21CN network ahead of their exchanges being enabled for WBC (though the additional speeds of ADSL2+ will not be available to customers using this method). The problem with the delay has been that ordering more capacity for the older network has, itself, a significant lead time (3 months or so), is prohibitively expensive and will shortly be redundant. :(
Quote from: netn00b on Sep 28, 2009, 19:26:40
umm ok will try to do that if i can.......not sure i remember how and does it not require a password ?
Yes, it's usually admin/password, unless you've changed it. I'm just going off for the evening, but others will be here to help. If you don't have sync, it's a local issue between you and the exchange, so check your wiring, try a different filter etc. If you do have sync, but not a PPP connection (so no IP address showing), then it could be an authentication problem, the router logs should reveal that.
If you have no service, call the IDNet out of hours service and someone will get back to you.
ok got into it and it says its not connected ?
in the router status section i have :
modem status : connecting
downstream speed : 0 kpbs
upstream speed : 0kbps
whats the idnet out of hours number ?
call IDnets normal number and have a pen ready.
i take it you have checked all the cables to to router etc etc
0800 701 2000 or 01462 248 0092.
To save you some time, because this is what IDNet will ask you to do, have you:
a) Plugged the router into the master socket or, if you have an NTE5 - the type where the bottom part of the faceplate can be removed - plugged it into the test socket which is revealed when you remove that faceplate?
b) Unplugged everything but the router from the phone line?
c) Tried with another router or modem if you have one?
Good luck.
(http://www.speedtest.net/result/577199233.png) (http://www.speedtest.net)
Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=189ms TTL=59
Reply from 212.69.36.10: bytes=32 time=180ms TTL=59
Ping statistics for 212.69.36.10:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 180ms, Maximum = 189ms, Average = 184ms
things are looking up but will hit hold or will my throughput fall off the wagon again
thanks Rik/Colin
i will have a look into it. i'm guessing at this time of night i am unlikely to get anything sorted.
i dont have the new nte5 faceplate. and the main socket as i understand it is in the kitchen, we are on an extension box where the 2 pc's are located.
we dont have anything normally apart from the router plugged in. we dont actually have a normal phoned plugged in more than 1 time in 100 as we always use mobiles.
i dont have another router.modem though to try....
Make the call, whoever's on tonight will do their best to help you.
So when idnet get the extra capacity from IPStream Connect will they be offering compensation to their loyal customers who have had to endure the sub-standard service for the last 3 months?....I think I already know the answer.....
There is hope to anyone still getting high pings....on my third reboot of today I am now at full sync and ping has dropped back to 15ms. I hope it stays like this for a while :fingers:
Quote from: Fox on Sep 28, 2009, 19:54:58
So when idnet get the extra capacity from IPStream Connect will they be offering compensation to their customers who have had to endure the sub-standard service for the last 3 months?....I think I already know the answer.....
As you know, I don't work for them and just try to act as a conduit for information. You'd have to ask them directly, but I think I know the answer too.
We've been struggling with one of our Centrals today that failed briefly this morning. It has since had double the normal number of sessions connected to one VP whist the other has only had 50% of the normal volume of connections running through it. BT will not help with this and so we are going to have to manually drop the connected sessions in order to try to get the balancing correctly again. We'll do this early tomorrow morning to minimise disruption. Apologies for the inconvenience caused.
Simon
Thanks for the update, Simon. :)
When do you think the government will step in to demand BT actually do what they're supposed to be doing?
about the same time we have someone that has a clue about wat they are doing...
oh and my ping times are starting to fall on the floor again
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\jk>ping idnet.net
Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=122ms TTL=59
Reply from 212.69.36.10: bytes=32 time=137ms TTL=59
Reply from 212.69.36.10: bytes=32 time=114ms TTL=59
Reply from 212.69.36.10: bytes=32 time=154ms 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 = 114ms, Maximum = 154ms, Average = 131ms
C:\Documents and Settings\jk>
I am now in a position to offer sympathy to you all, having had my Be LLU connection activated today.
My Idnet line stats on WBC (atten 39db, SNR margin 9db, typical sync of 9000 down and 900 up; full depth interleaving; IP profile of 7150 or 8000) have given me a ropy and inconsistent throughput of...well, very little for the last three weeks, with very regular resyncs.
Suffice to say that my speedtests have often given me a higher upload than download!
My Bethere connection is right now synced at nearly 11000, with throughput of 1.1Mbps. Same kit, same socket, same everything as on Idnet this morning. That's better!
Whether the recent problems have been down to congested Idnet centrals or BT's 'underdimensioning' farce, I'm sorry to have left Idnet after 2.5 years. But it's not been a good experience on WBC since June, and I don't see any improvement on the horizon.
best to you all!
Quote from: Niall on Sep 28, 2009, 20:41:24
When do you think the government will step in to demand BT actually do what they're supposed to be doing?
Never. Too many shares involved. :evil:
Quote from: Simon_idnet on Sep 28, 2009, 20:05:15
We've been struggling with one of our Centrals today that failed briefly this morning. It has since had double the normal number of sessions connected to one VP whist the other has only had 50% of the normal volume of connections running through it. BT will not help with this and so we are going to have to manually drop the connected sessions in order to try to get the balancing correctly again. We'll do this early tomorrow morning to minimise disruption. Apologies for the inconvenience caused.
Simon
That's good to know; I've come home and discovered high pings and slow speeds as well, and it saves a lot of time wasted rebooting routers, troubleshooting connections etc.. if we know there's an external cause. With that in mind, can I gently point out that http://www.idnet.net/support/status.jsp is still doing an impression of the band on the titanic. I've talked about this before; a service status page is absolutely no use if it doesn't reflect the current service status; it's actually counter-productive in that case. Clearly the broadband status should not be "Good Service" with a green light, it should be "Reasonable Service" with an orange light and an explanation, to save potentially thousands of people fiddling around with their routers. Come on guys, set the service status page properly in future.
We have cleared all sessions on that Central and have seen them reconnect with almost perfect balancing now :)
Thanks
Simon
Thanks for the update Simon.
Shame about the page status though :(
I agree, Gary.
Quote from: Simon_idnet on Sep 29, 2009, 04:48:55
We have cleared all sessions on that Central and have seen them reconnect with almost perfect balancing now :)
Thanks
Simon
Cheers Simon,
But high pings are back again :(
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 93 ms 68 ms 109 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 105 ms 91 ms 84 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 113 ms 137 ms 112 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 88 ms 91 ms 109 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 109 ms 109 ms 95 ms www.idnet.net [212.69.36.10]
Trace complete.
Restarted my router and it's same old same old:
Microsoft Windows [Version 6.1.7100]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Steven>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=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=188ms TTL=59
Reply from 212.69.36.10: bytes=32 time=147ms TTL=59
Reply from 212.69.36.10: bytes=32 time=486ms 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 = 30ms, Maximum = 486ms, Average = 212ms
C:\Users\Steven>
Useless!
I've had a word with Simon today, following this morning's 'nuke option', and he is happy that their network is re-balanced and has sufficient capacity. All I can suggest is contacting support.
except for the period of high pings earlier, mines been fine.
Would check now but got alot of traffic going through my home network at the mo that will cause pings to go high.
Massive backups going on!! pain in the arse!!!
If only backups weren't necessary... :)
Quote from: Rik on Sep 29, 2009, 18:21:59
If only backups weren't necessary... :)
I'm getting ready for windows 7.
Got 3 laptops and 3 pc's to upgrade, so thought i would do a fresh backup from all.. Big mistake ;D
Oh and forgot the netbook. cant leave that out now!! :) (not putting win7 on that thou)
My corporate version of Windows 7 is running sweetly.
Quote from: psp83 on Sep 29, 2009, 18:24:40
I'm getting ready for windows 7.
Got 3 laptops and 3 pc's to upgrade, so thought i would do a fresh backup from all.. Big mistake ;D
Paint drying? :)
My RC versions are running fine aswell..
I just havent decided.. full reformat and install or do the lifehacker upgrade way!
It won't have time to dry when installing W7, it only takes around 30 minutes on an average spec laptop.
Quote from: Rik on Sep 29, 2009, 18:29:08
Paint drying? :)
Yeh, think i'm on the 2nd room of paint drying now! :laugh:
Quote from: Glenn on Sep 29, 2009, 18:30:37
It won't have time to dry when installing W7, it only takes around 30 minutes on an average spec laptop.
I have some Ronseal 20 minute woodstain. ;D
Quote from: psp83 on Sep 29, 2009, 18:31:03
Yeh, think i'm on the 2nd room of paint drying now! :laugh:
A feeling with which I can empathise.
Quote from: Rik on Sep 29, 2009, 18:32:05
A feeling with which I can empathise.
Wish i never had the crazy idea!
Just starting to install a new server now, should keep me away from the backups for abit :)
The congestion returned about 30 minutes ago for me:
Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=157ms TTL=59
Reply from 212.69.36.10: bytes=32 time=167ms TTL=59
Reply from 212.69.36.10: bytes=32 time=102ms TTL=59
Reply from 212.69.36.10: bytes=32 time=89ms TTL=59
Reply from 212.69.36.10: bytes=32 time=132ms TTL=59
Reply from 212.69.36.10: bytes=32 time=172ms TTL=59
Reply from 212.69.36.10: bytes=32 time=160ms TTL=59
Reply from 212.69.36.10: bytes=32 time=169ms TTL=59
Reply from 212.69.36.10: bytes=32 time=114ms TTL=59
Reply from 212.69.36.10: bytes=32 time=93ms 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 = 89ms, Maximum = 172ms, Average = 135ms
high pings here aswell :(
reboot not clearing it either :(
ok, this is getting annoying now. never had high pings like this with tiscali :(
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 58 ms 46 ms 47 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 55 ms 44 ms 40 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 52 ms 48 ms 46 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 24 ms 25 ms 23 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 49 ms 64 ms 52 ms www.idnet.net [212.69.36.10]
Trace complete.
C:\Users\Paul>tracert www.idnet.net
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 15 ms 24 ms 14 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 15 ms 16 ms 18 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 14 ms 15 ms 16 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 15 ms 16 ms 14 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 27 ms 25 ms 17 ms www.idnet.net [212.69.36.10]
Trace complete.
C:\Users\Paul>tracert www.idnet.net
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 185 ms 156 ms 123 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 97 ms 86 ms 83 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 96 ms 106 ms 105 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 98 ms 96 ms 91 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 81 ms 90 ms 83 ms www.idnet.net [212.69.36.10]
Trace complete.
my pings have finnaly become stable and throughput has pritty much gone back to normal so im a happy bunny
Pings are back to normal here aswell.
root@saturn:~# ping -c 20 idnet.net
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=14.1 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=2 ttl=59 time=13.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=3 ttl=59 time=13.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=4 ttl=59 time=15.1 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=5 ttl=59 time=14.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=6 ttl=59 time=14.2 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=7 ttl=59 time=14.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=8 ttl=59 time=15.9 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=9 ttl=59 time=13.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=10 ttl=59 time=14.5 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=11 ttl=59 time=12.5 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=12 ttl=59 time=13.2 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=13 ttl=59 time=14.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=14 ttl=59 time=12.9 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=15 ttl=59 time=13.6 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=16 ttl=59 time=14.1 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=17 ttl=59 time=13.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=18 ttl=59 time=13.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=19 ttl=59 time=18.8 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=20 ttl=59 time=14.5 ms
--- idnet.net ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19029ms
rtt min/avg/max/mdev = 12.522/14.269/18.866/1.299 ms
Quote from: psp83 on Sep 29, 2009, 18:30:09
My RC versions are running fine aswell..
I just havent decided.. full reformat and install or do the lifehacker upgrade way!
Clean install. :thumb:
:iagree:
High pings and nasty slow data throughput here. One minute it's fast, the next minute it's like being back on dial-up. :eek4:
Speedtest on speedtester.bt.com gave me 765kbps and speedtester.net a little over 1mbit :'(
I did see a lot of websites taking ages to load over the last couple of days, but okay download speeds. I assumed at the time that it was my router needing a reboot, but it's back to normal now so could have been anything.
Wow, that's a helpful contribution :D
Yet again, another night of high pings. Impossible to play xbox online.
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 107 ms 109 ms 109 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 129 ms 137 ms 136 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 147 ms 149 ms 144 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 111 ms 117 ms 106 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 134 ms 119 ms 103 ms www.idnet.net [212.69.36.10]
Trace complete.
Also, websites are lagging aswell. :(
I hadn't actually noticed, but mine seem to be up too.
Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=175ms TTL=59
Reply from 212.69.36.10: bytes=32 time=136ms TTL=59
Reply from 212.69.36.10: bytes=32 time=140ms TTL=59
Reply from 212.69.36.10: bytes=32 time=157ms 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 = 136ms, Maximum = 175ms, Average = 152ms
Reboot hasn't help either. :(
Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=114ms TTL=59
Reply from 212.69.36.10: bytes=32 time=137ms TTL=59
Reply from 212.69.36.10: bytes=32 time=150ms TTL=59
Reply from 212.69.36.10: bytes=32 time=152ms 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 = 114ms, Maximum = 152ms, Average = 138ms
C:\Documents and Settings\Simon>tracert idnet.com
Tracing route to idnet.com [212.69.36.10]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms home [192.168.1.254]
2 68 ms 61 ms 74 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 124 ms 124 ms 122 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 108 ms 106 ms 102 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 126 ms 120 ms 121 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 128 ms 139 ms 132 ms www.idnet.net [212.69.36.10]
Trace complete.
Tracing route to www.idnet.co.uk [212.69.36.10]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.1
2 24 ms 21 ms 22 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 20 ms 19 ms 20 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 25 ms 22 ms 20 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 21 ms 25 ms 20 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 26 ms 21 ms 22 ms www.idnet.net [212.69.36.10]
Mine seems fine.
High pings tonight. Honestly what's going on? Having high pings in the afternoon was "acceptable" but to have it in the evening since yesterday isn't.
my pings are normal tonight, makes a change.
root@saturn:# ping -c 20 idnet.net
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=13.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=2 ttl=59 time=15.2 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=3 ttl=59 time=14.1 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=4 ttl=59 time=14.5 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=5 ttl=59 time=15.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=6 ttl=59 time=15.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=7 ttl=59 time=16.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=8 ttl=59 time=13.9 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=9 ttl=59 time=14.5 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=10 ttl=59 time=14.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=11 ttl=59 time=14.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=12 ttl=59 time=14.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=13 ttl=59 time=12.8 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=14 ttl=59 time=14.0 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=15 ttl=59 time=14.6 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=16 ttl=59 time=13.8 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=17 ttl=59 time=12.6 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=18 ttl=59 time=13.8 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=19 ttl=59 time=13.8 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=20 ttl=59 time=26.1 ms
--- idnet.net ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19028ms
rtt min/avg/max/mdev = 12.631/14.908/26.196/2.718 ms
High pings here as well..... :shake:
Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=130ms TTL=59
Reply from 212.69.36.10: bytes=32 time=148ms TTL=59
Reply from 212.69.36.10: bytes=32 time=114ms TTL=59
Reply from 212.69.36.10: bytes=32 time=52ms 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 = 52ms, Maximum = 148ms, Average = 111ms
Quote from: Aaron on Oct 01, 2009, 20:47:18
High pings tonight. Honestly what's going on? Having high pings in the afternoon was "acceptable" but to have it in the evening since yesterday isn't.
As I keep saying, people with ping issues
need to contact support. There's nothing we can do here to help, sorry.
And, just to add, they need to contact support during the day, as pings are not seen as a priority 'out of hours'.
Good point, Simon.
It would be better if you made a sticky on the forum explaining the congestion issue, the more frequently it is occurring, the more people are noticing its effects.
I'd prefer it to come from IDNet. ;)
Pings are fine but my connection has just dropped twice within 5mins, Sync speed still the same though ???
Was it sync or ppp you lost? I'm guessing sync as you mentioned it which is local to your line from the exchange to the house. It may have BT doing some work.
Quote from: psp83 on Oct 02, 2009, 23:03:50
Pings are fine but my connection has just dropped twice within 5mins, Sync speed still the same though ???
There
is a sticky for loss of service just so we can count these cases.
Richard
Good point, Richard.
My speeds are quite good right now, not the best they've been, but a very reasonable 7Mbit/sec (average from testing on a couple of different sites, and leaving out the highest and lowest scores), but the pings are still all over the shop. One minute they're 25~30ms next they're 180ms+. :dunno:
Xbox Live is still painful to play on right now. I still haven't managed to get my Halo ODST fix because of the problems :(
You're on WBC, aren't you?
I am, yep. Jumped on the ADSL2+ the moment it was available at my exchange, and somewhat regret having done it now. Went from a rock solid ADSL Max 8Mbit with uptimes of 14 days or more to a glitchy ADSL2+ that re-syncs 4 or 5 times a week and at anywhere between 9 and 12MBit.
Guess that's the price you pay for early adoption?
(Just like the £49.99 I used to pay for 512K on BTOpenWorld. Those were the days.)
To some extent, I think that ADSL2+ is always going to suffer from these problems due to it using frequencies that were not used on Max.
Quote from: MattBeale on Oct 03, 2009, 13:19:54
I am, yep. Jumped on the ADSL2+ the moment it was available at my exchange, and somewhat regret having done it now. Went from a rock solid ADSL Max 8Mbit with uptimes of 14 days or more to a glitchy ADSL2+ that re-syncs 4 or 5 times a week and at anywhere between 9 and 12MBit.
You can ask support to increase the stability of the line, they have specific tools for the job with WBC. For me, WBC has got steadily better, but some areas of the country are still experiencing BT congestion.
Let me guess, increasing stability means turning down the sync speed?
That's the equation I'm afraid.
Quote from: Rik on Oct 02, 2009, 08:52:34
As I keep saying, people with ping issues need to contact support. There's nothing we can do here to help, sorry.
I not spending time taking ping test and going through the hoops when they won't do anything anyway and just reply with Ping uses ICMP, which has low priority, la la la. I just like to see if I'm the only one with a problem or not and people posting pings lets me know this. The status page is a joke so thats no help.
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 3 ms 3 ms 3 ms 192.168.1.1
2 40 ms * 122 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 105 ms 94 ms 76 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 57 ms 62 ms 59 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 75 ms * 118 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 98 ms 101 ms 104 ms www.idnet.net [212.69.36.10]
Trace complete.
The problem is, if you don't contac support how can they try and work towards a solution?
If there is ever a wide spread problem with pings, the forum has numerous members posting. At the moment, it is only a handful of members which makes tracking the problem very difficult or means it is down to an individual's line and exchange.
Not exactly working towards a solution if all I'll get told is ICMP is treated as low priority. Whats the point in me even bothering to send them it if it's that useless. The problems is know already is it not? The load balancing keeps messing up.
Latency was high for me at one point this evening, but as has been said many times before, manually reconnect your router's ISP connection (or just reset the router) to 'load balance' yourself on to a less congested pipe. Using a ping graph type program before and after is a handy way to see if you've fixed the issue.
Unfortunately, unless you move to a different provider, you'll just have to get used to this problem periodically re-occurring until all of Idnet's 20CN customers are switched over to use their 21CN hostlink. This will hopefully happen in the next 1-2 months.
It may be the load balancing (in which case the reboot will normally work) or it may be something else.
Hopefully the host link will be in and tested sooner rater than later!
If:
1. You're currently paying for one of Idnet's ADSL Max products (i.e. Home PAYG, Home Lite, Home Max or Home Supermax).
2. The "Virtual paths" of the telephone exchange your phone line is connected to aren't listed as yellow/red here (http://usertools.plus.net/exchanges/).
3. No-one/nothing else (checked for malware etc) is also using the connection.
4. You've verified your latency is actually higher than normal, via a ping graph program like Ping Plotter (http://www.pingplotter.com) or by typing "ping www.idnet.net -n 100" at the Command Prompt.
Then most likely the BT Central you're currently routed through is congested. The best course of action to resolve the situation is to manually try and move yourself to another pipe as described in post #120.
I'd agree with everything you say, but with one caveat, the Plusnet checker doesn't seem to be kept current any more. :(
"Record last updated: 18 Sep 09" it says for my exchange, I know it's not exactly up to the minute in terms of accuracy, but it's all we have from BT Openreach/Wholesale!
It is, but the situation changes faster than the information, unfortunately.
Tonight is the worse night so far,
High pings and websites loading really slow.
Quote from: psp83 on Oct 05, 2009, 22:29:46
Tonight is the worse night so far,
High pings and websites loading really slow.
Same here, I've emailed IDnet this time as posting it here is pointless these days.
http://www.aaronstevens.co.uk/Ping-milliseconds-2009Oct05-2240.jpg
It was the same for me too.
Quote from: dujas on Oct 05, 2009, 00:53:21
Latency was high for me at one point this evening, but as has been said many times before, manually reconnect your router's ISP connection (or just reset the router) to 'load balance' yourself on to a less congested pipe. Using a ping graph type program before and after is a handy way to see if you've fixed the issue.
Unfortunately, unless you move to a different provider, you'll just have to get used to this problem periodically re-occurring until all of Idnet's 20CN customers are switched over to use their 21CN hostlink. This will hopefully happen in the next 1-2 months.
Post removed
Quote from: Aaron on Oct 05, 2009, 23:43:53
Same here, I've emailed IDnet this time as posting it here is pointless these days.
The forum is
not an official support channel, we do our best to fill in outside support hours, but on speed issues we can do little. Forum staff spend a lot of time on the phone to IDNet each week, following up issues for members and trying to obtain resolution, but we are volunteers and do not have the time to deal with every issue reported. IAC, speed issues require data for them to be investigated, so there's little point in us taking up such cases.
Rik and the admin team do an excellent job (well beyond the call of duty) in helping members out and as Rik says they can only advise on steps to take, which will at some stage will require assistance from IDNET support.
It is with regret that I have to say farewell to IDNET as an ISP. The rocky past few weeks on MAX with latency, frequent reboots of the router and consequent drop in profile have taken their toll and it is so unfortunate that BT are no doubt the cause of many of these issues. I obtained my MAC yesterday and am migrating to BE Unlimited to sample the delights of LLU! :fingers:
IDNET would still be my first choice for a BT based (non LLU) product and their support is excellent - just a pity that BT have let them down :'(.
Don't be a stranger, Wags, do let us know how you get on. :)
Quote from: Rik on Oct 07, 2009, 09:06:08
Don't be a stranger, Wags, do let us know how you get on. :)
Will do Rik! :thumb:
I agree with you, though. IDNet and other small ISPs have been royally screwed by BT in the past year, and yet the have no way of getting compensation. I am optimistic, though, that things are improving and will have improved dramatically in the next month or so.
Quote from: Rik on Oct 07, 2009, 09:12:44
I agree with you, though. IDNet and other small ISPs have been royally screwed by BT in the past year, and yet the have no way of getting compensation. I am optimistic, though, that things are improving and will have improved dramatically in the next month or so.
Hmmm. You can see why Zen were in no hurry to hop on board the WBC bandwagon.....
At least iDNet's customers have got something out of it in the form of increased allowances.
Hope all goes well on BE, Wags. :)
Surprise surprise high pings again tonight.
If I want to leave do I just request a MAC and make sure I'm switched before my next bill date of 25th Oct or do I have to give some notice?
I think, if you call or email support, a MAC will be issued almost immediately.
Quote from: Sebby on Oct 07, 2009, 22:01:26
Hope all goes well on BE, Wags. :)
Thanks Sebby. I will let you know after the switch-over on 15th October :fingers:
Quote from: juiceuk on Oct 07, 2009, 23:06:28
If I want to leave do I just request a MAC and make sure I'm switched before my next bill date of 25th Oct or do I have to give some notice?
I asked for mine by email and gave a short reason why and I was emailed my MAC within an hour. Now I have a date for BE's service, I guess I now need to email IDNET and tell them to cancel the service on that date.
No need - this happens automatically on the date of transfer. You can just sit back and relax. :)
A brief up date for you....
Migrated to BE today and connected straight away at 10.7 meg . My first SpeedTest gives a download of 9.02 meg, so very chuffed indeed. Ping (interleaved) is 21ms! (can't wait to see what it's like when I switch to fastpath)!! :thumb:
http://www.speedtest.net/result/593103847.png
Fantastic! :thumb:
Good stuff, Wags. ;D
:thumb: