Please post any problems or comments in this thread. Thanks. :)
(The announcement is here. (http://www.idnetters.co.uk/forums/index.php?topic=5368.msg93755#msg93755))
Is this going to improve things? I can't imagine things could get any better... ;D
was going to ask the same.. will we notice anything or is it just to future proof things?
I don't think that anyone will notice any difference but you probably would in a few months' time if we did nothing now.
Cheers
Simon
Ah, forward planning - :karmic:
Quote from: Simon on Jan 11, 2008, 21:21:06
Ah, forward planning
It's one of the things we like about IDNet, they don't wait until they have the problem to get it fixed, but rather prevent the problem in the first place!
Indeed!
I am having a few problems to certain website like IMDB and AVforums, but maybe its something my end?
I can't get to the BBC, ThinkBroadband, Digital Spy, PC Pals, but I can get to Nationwide, DigiGuide, Sky Sports. I've just queried whether that's what Simon means by anomalies.
Quote from: Rik on Jan 12, 2008, 10:28:39
I can't get to the BBC, ThinkBroadband, Digital Spy, PC Pals, but I can get to Nationwide, DigiGuide, Sky Sports. I've just queried whether that's what Simon means by anomalies.
Hi
None of those work for me either.
I've just noticed we've never welcomed you properly to the forum, very remiss of us. Have a karma. :) :welc: :karmic:
Thanks Rik :)
I love IDNET, best ISP I have ever had. I dont mind a little down time on certain sites for maintenance, its not the end of the world.
Well I'm not happy. I've just been kicked off and reconnected at a synch rate of 6688.. I was at 8096. I do hope this isn't going to be permanent.
That's nothing to do with the maintenance work, Ann, they are working 'internally', so it will have had no effect on your connection to the exchange. It could be BT work, or a bad burst of noise.
Quote from: tigermad on Jan 12, 2008, 10:34:17
I dont mind a little down time on certain sites for maintenance, its not the end of the world.
Even better, it's not so much maintenance as upgrade. ;)
I'm not getting the BBC either or liverpoolfc.tv. Skysports tempremental.
That's all i've tried so far.
Mike
google.co.uk and tfl are very intermittent
Quote from: Ann on Jan 12, 2008, 10:41:21
Well I'm not happy. I've just been kicked off and reconnected at a synch rate of 6688.. I was at 8096. I do hope this isn't going to be permanent.
I've just been kicked off and had to reconnect too. I am finding many sites inaccessible. I believe it's down to IDNet.
Michael
Quote from: Rik on Jan 12, 2008, 10:42:40
That's nothing to do with the maintenance work, Ann, they are working 'internally', so it will have had no effect on your connection to the exchange. It could be BT work, or a bad burst of noise.
Just lost my DSL connection as well, about 3/4 minutes.
Would it not possible to e-mail customers where planned maintenance is being carried out? It would avoid the 'is the router, the ISP or BT' question that immediately comes to mind when internet access is lost. ???
That seems a few too many to be a coincidence, In, yet the work that's being done shouldn't cause a re-sync for anyone. I'll see if I can get any more info.
Quote from: michaelh on Jan 12, 2008, 10:46:54
I've just been kicked off and had to reconnect too. I am finding many sites inaccessible. I believe it's down to IDNet.
Michael
Me too :(
Quote from: Ardua on Jan 12, 2008, 10:48:52
Would it not possible to e-mail customers where planned maintenance is being carried out? It would avoid the 'is the router, the ISP or BT' question that immediately comes to mind when internet access is lost. ???
Notices were placed here and on ThinkBroadband yesterday, however there's nothing on the IDNet website which is, perhaps, an oversight.
I'll mention the email suggestion.
I can't get to quite a few websites or Purple Cloud's email servers.
Just had a look out of my window, no Openreach vans at my " local " ;D exchange.
Me three!
Not too impressed with this. Posting an "announcement" on a forum that I didn't visit until today, the day before an outage is not very professional.
Not to mention carrying out an upgrade on a Saturday morning !
:-[
Oh I'm glad someone wrote about purplecloud. My email stopped coming in from them just before I was disconnected. You don't realise how much the ISP influences until it breaks. But if my synch rate doesn't recover I shall be very upset.
I lost my connection also for about a few mins - I restarted the router, and it seemed to restart - whether that was coincidence or not.....
Quote from: Rik on Jan 12, 2008, 10:52:33
Notices were placed here and on ThinkBroadband yesterday, however there's nothing on the IDNet website which is, perhaps, an oversight.
Shouldn't this work be reflected somehow on the Status page?
I've already mentioned it, Noreen. ;)
I just checked my router logs and I didn't lose sync at all, but it does look like I lost the connection to IDNet at some point over night.
Any idea when, Sebby? The work didn't start till 7, so it may have been BT at work (I'm expecting a rash of stale sessions on Monday morning. :()
Hm, seem to have lost lots of chunks of the net too...
To clarify : I have google! So I can read news, and I managed to secure a nifty new album to listen to, but most of the net appears inaccessible beyond N hops (usually 4 or 5) due to routing fun.
Oh well...
Lots of sites unreachable here too (BBC, Pistonheads, Cahoot, etc) and POP3 email collection also not working.
Don't like to criticise IDNet as their service is normally spot on but if these issues are related to the upgrade then I have to agree that Saturday morning was a bloody stupid time to carry it out.
Edit: I see service staus shows no problems. This clearly isn't the case...
Quote from: Rik on Jan 12, 2008, 11:06:11
Any idea when, Sebby? The work didn't start till 7, so it may have been BT at work (I'm expecting a rash of stale sessions on Monday morning. :()
Just so that I'm prepared, would you explain what a stale session is, Rik?
This is a bit disappointing, to be honest it's the only bad experience of IDNet that I know of so I'm not too worried, but an e-mail to inform us of any maintenance should have been sent around. I just had to google "weather" and click on about 15 links until I could get one to work! Wikipedia doesn't work, nor does BBC, thinkbroadband, Setanta, plus all kinds of links I'm researching about alternatives to Windows updates. This kind of maintenance with the potential impact it has had, should be carried out at the lowest usage time possible, which I suspect is not Saturday morning/afternoon.....?
Stale session : When the net thinks you're connected but your router really doesn't agree. Needs to be reset from somewhere else other than the router (can't remember if it's BT or IDNet you need to pester), worst case scenario is to notify Simon or one of Simon's minions and the problem should get solved pretty fast. Do the usual of rebooting the router (leave it down for a minimum of 15 mins beforehand) to get rid of the possibility of an untimed PPP session still being up on the local exchange.
Looks like everything's back up and running again :) ;D
Quote from: minimoog on Jan 12, 2008, 11:17:21
Looks like everything's back up and running again :) ;D
Looks it, may expect some blips over the next hour whilst things are still tweaked but eh... *shrug*
I've just had word from Tim. IDNet send their apologies, the work has proved more disruptive than they envisaged and, ironically, he's been unable to access the network status page to update it.
They are pushing ahead to complete the work asap.
Quote from: Nova on Jan 12, 2008, 11:15:45
Do the usual of rebooting the router (leave it down for a minimum of 15 mins beforehand) to get rid of the possibility of an untimed PPP session still being up on the local exchange.
Or log in to the BT test domain and then revert to the normal IDNet login - at least that's the theory. :)
Quote from: Rik on Jan 12, 2008, 11:19:08
he's been unable to access the network status page to update it.
:laugh:
Quote from: Rik on Jan 12, 2008, 11:06:11
Any idea when, Sebby? The work didn't start till 7, so it may have been BT at work (I'm expecting a rash of stale sessions on Monday morning. :()
No idea, Rik; this is one thing I find a bit annoying about the 2Wire; some of the reporting is definitely wrong. If I look at
ISP Connection Establishment it's showing 215:02:38, which is madness as the router has only been connected for 2 and a half days!
Is there another way I can tell on the 2Wire?
Quote from: Nova on Jan 12, 2008, 11:15:45
Stale session : When the net thinks you're connected but your router really doesn't agree. Needs to be reset from somewhere else other than the router (can't remember if it's BT or IDNet you need to pester), worst case scenario is to notify Simon or one of Simon's minions and the problem should get solved pretty fast. Do the usual of rebooting the router (leave it down for a minimum of 15 mins beforehand) to get rid of the possibility of an untimed PPP session still being up on the local exchange.
.........and I don't really understand that either. ;D
Quote from: Rik on Jan 12, 2008, 11:20:06
Or log in to the BT test domain and then revert to the normal IDNet login - at least that's the theory. :)
That requires effort ;)
15 mins gives you time to make a cuppa!
Quote from: Noreen on Jan 12, 2008, 11:25:25
.........and I don't really understand that either. ;D
Basically a "Stale session" is when one bit of equipment (usually the local exchange) considers you connected. But your router says that you are not, and continually tries to log in, of course because the guys at the other end believe you ARE logged in, they refuse these log in attempts and you're stuck.
To remove any possibility of a stuck (not stale) session, turn off your router for 15 mins and make a coffee, listen to some music, relax etc. If it's still not agreeing after say 30 mins of this kind of treatment, contact IDNet.
Not been here for ages as everything has been pretty much perfect. Went to check some stuff today and no internet, checked router and found i'd been reconnected 25m ago and only now connecting to sites other than google.
Not a big issue but it would be better to have an email notifaction of planned works as i bet the majority of customers don't check here or thinkbroadband much or at all.
Quote from: spiral on Jan 12, 2008, 11:31:27
Not a big issue but it would be better to have an email notifaction of planned works as i bet the majority of customers don't check here or thinkbroadband much or at all.
They probably didn't anticipate any impact on customers, though this goes to show that any maintenance work can have unfavourable consequences. ;)
OK, I think that we are pretty much in agreement that any future maintenance work should be notified in advance and a message displayed on the web site, oh and preferably not on a Saturday during the day time, just in case there are any unforeseen side effects. ;)
But that aside, it was done well. ;)
I can't believe all the negative comments about Idnet posted this morning. It was made clear that BT gave them very little warning and they were told to expect a 1 minute loss of service. They then informed us at once, what more can they do. Now everybody that has lost sync this morning is blaming it on Idnet. For God's sake get off their backs and remember this is the best ISP on the planet and we can be gratefull for a very good service all the year round.
As for doing this on a Saturday morning at a time when most people are in bed, Oh what a thing to do, Much better to do it in the week at about 12.00 noon when everybody was in work and it would have only hit the unemployed, retired and business premises. :o
Agreed. What I've said is only factual, such as when I disconnected. There are no complaints here. :)
Den, I think the work that you're talking about is that scheduled for Monday.
No complaints here, just a blip of a few minutes and everything ok. Comapere that to some other ISP's with downtimes in the hours.
Quote from: Noreen on Jan 12, 2008, 11:48:22
Den, I think the work that you're talking about is that scheduled for Monday.
It is, Noreen.
Today's work should, according to Cisco, have been a simple hot plug, but it didn't work out that way. :(
Quote from: Den on Jan 12, 2008, 11:43:48
I can't believe all the negative comments about Idnet posted this morning. It was made clear that BT gave them very little warning and they were told to expect a 1 minute loss of service. They then informed us at once, what more can they do.
AFAIK the BT maintenance is yet to come. ;) That said, I've had no noticeable issues yet, so I'm not complaining.
I agree Noreen, it seems that on this occasion Den has not fully understood the facts of the issue.
It certainly didn't happen at 07.00 hours. ;D
Also they did not notify all of " us " they only notified forum users.
I am not having a go at IDNet, I am one of their biggest fans, however, if things could have been done better, it is best to say so, it is called " constructive critisism ". ;)
All critics should die. >:D >:D >:D :leer: :leer:
Quote from: cavillas on Jan 12, 2008, 12:00:10
All critics should die. >:D >:D >:D :leer: :leer:
You are just evil Alf.. ;D :evilb: :evilb: :evilb: :tongue:
Quote from: Inactive on Jan 12, 2008, 11:54:41I am not having a go at IDNet, I am one of their biggest fans, however, if things could have been done better, it is best to say so, it is called " constructive critisism ". ;)
Exactly. The Status page is my main niggle and this subject has cropped up before. I really can't see the point of a Status page that doesn't reflect the status, surely it's the first place that non-forum members would look when they have a problem, yet while we were all discussing here the problems (admittedly short-lived) caused by the maintenance work the Status page still stated that everything was fine. I realise that as Rik has said that IDNet couldn't access it later.
And I have lost synch speed. I turned the router off and left it off while I did some maintenance.. defragging and so on.. reconnect and still a low synch speed. I know it's only internet but I honestly feel so miserable. Why did they do this to me?
I really don't think your problem is related to IDNet, Ann. Synch speed is a local issue, ie between you and the exchange. Work being done at Letchworth or Telehouse should have no impact on that at all.
It's very coincidental.
I did have a blip this morning, around 11:10am, and couldn't access some sites, but it all seems to be up and running again now.
I do, however, feel that IDNet should have sent out an email to all customers, informing them of the planned maintenance, as clearly, not everyone reads the forums.
Quote from: Ann on Jan 12, 2008, 12:19:38
It's very coincidental.
I accept that, but sync speed is all about the connection between you and the exchange, it's unrelated to who your ISP is. (Throughput is a different issue, of course.) What are your line stats showing?
Quote from: Simon on Jan 12, 2008, 12:20:33
I do, however, feel that IDNet should have sent out an email to all customers, informing them of the planned maintenance, as clearly, not everyone reads the forums.
I agree Simon, it would seem the sensible thing to do.
So can we all now expect an email with reference to the upcoming planned BT work. ?? ;)
My connection to differnet sites seems to be snappier and faster now. Did they do this work just for 'lil old me. ;D
Quote from: cavillas on Jan 12, 2008, 12:25:30
My connection to differnet sites seems to be snappier and faster now. Did they do this work just for 'lil old me. ;D
Do you know what Alf, I thought it was my imagination, but that seems to be the case here as well. ;)
It should be the case. Many of the routers are now going 10x faster. :)
Although it would have been nicer under better circumstances, :welc: to any new members of the forum this morning. Things seem to be up and running normally again, but your comments have been noted, and will be passed on to IDNet. Welcome karma points have been issued to all! :)
Hi all
Apologies for the disruption this morning. We really didn't expect there to be any. Next time we will expect the worst, choose another day for the work, send an email to everyone in advance, and make sure the status page reflects the worst in advance in case we're unable to access it! Right, Weekend..take 2!
Apologies again
Tim
Thanks Tim! (http://si6776.www.idnet.com/smileys/thumb.gif)
Brilliant Tim, that is what we all wanted to hear,
Cheers ;)
Just an FYI, the status page did give advanced warning of the work, and the current state of play, but only when logged in via the customer account page. Tim's looking into why that didn't update the main status page.
[attachment deleted by admin]
Hey
Had random connectivity this morning, due to the routing. Bounced router, lost all comm's, rebuilt router, then rang out of hours support, got a call back in 15 mins or so, advising of maintenance, (can't beat that). As others have said email would have been good, but beyond that, under an hour of no internet is not really an issue ;) even though as usual it was important at the time, or was it ...
keep up the good work guys
Thank you Tim, Rik and everyone else concerned. :thnks:
Quote from: Rik on Jan 12, 2008, 12:21:10
I accept that, but sync speed is all about the connection between you and the exchange, it's unrelated to who your ISP is. (Throughput is a different issue, of course.) What are your line stats showing?
If it's not directly IDNet's fault then it is indirectly. I had been up for almost a month and it was them who disconnected me and allowed the lower synch to take place. Maybe it was lurking there waiting to jump but I can blame IDNet for allowing it to happen. >:(
IDNet didn't disconnect you, Ann, at least not from the exchange. Did you do a manual reboot of the router?
Never mind. I'll live.
Quote from: Sebby on Jan 12, 2008, 11:24:19
Is there another way I can tell on the 2Wire?
Sorry, Sebby, missed this in the rush. How about the stats page, that has something about ISP connection establishment.
http://192.168.1.254/xslt?PAGE=J04&THISPAGE=J17&NEXTPAGE=J04
LCP down @ 1135 this morning for 6 long minutes !!!!! ::) ::) Most unacceptable situation .... now considering a move back to f2s after over 2years of faultless service by IDNet. I mean to say, this down period could happen again over the next few years couldn't it?? ;D ;D ;D
Got my mouthwash ready Rik!!!! :laugh:
:rofl2: :karmic:
Well done to Simon and Tim etc. They did acknowledge the problems and dealt with them quickly and efficiently. It was, after all, for the longer term benefit of IDNET users. They should now book themselves a weekend off, I think they need it being just after Christmas. ;D
I'm suffering from very high pings... 150ms minimum on the Steam Server browser, and pinging bbc.co.uk.
It was fine last night (averaging 25ms).
I've restarted my router (Speedtouch 585v6) twice, but it doesn't help.
Is there anything else I can try?
Not really. I'm also seeing extended ping times, I'll let support know.
thanks for the quick reply Rik. It'll keep me off online gaming, but it's working fine otherwise (I'm listening to streaming radio off BBC)
edit: pings coming down to 100ms now...
Getting high pings here aswell..
Pings on wednesday 9th
Tracing route to www.jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms home [192.168.1.254]
2 17ms 15 ms 15 ms telehouse-gw2.idnet.net [212.69.63.55]
3 18 ms 17 ms 15 ms g3-35-501.cr05.hx2.bb.pipex.net [193.203.5.14]
4 16 ms 17 ms 15 ms v3953.cr05.tn5.bb.pipex.net [62.72.137.29]
5 18 ms 15 ms 15 ms g1-1-6.ar01.tn5.bb.pipex.net [62.72.140.142]
6 17 ms 19 ms 17 ms ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.241.14]
7 19 ms 17 ms 17 ms secure.jolt.co.uk [82.133.85.65]
Trace complete.
Pings today
Tracing route to www.jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms home [192.168.1.254]
2 113 ms 108 ms 114 ms telehouse-gw2.idnet.net [212.69.63.55]
3 125 ms 118 ms 100 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243]
4 102 ms 100 ms 100 ms g3-35-501.cr05.hx2.bb.pipex.net [193.203.5.14]
5 104 ms 108 ms 108 ms v3953.cr05.tn5.bb.pipex.net [62.72.137.29]
6 151 ms 135 ms 102 ms g1-1-6.ar01.tn5.bb.pipex.net [62.72.140.142]
7 106 ms 108 ms 102 ms ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.241.14]
8 111 ms 114 ms 124 ms secure.jolt.co.uk [82.133.85.65]
Trace complete.
Thanks, Paul, duly passed on. :)
No prob..
Just can't play CoD4 or UT3 now :(
Feels like i'm back gaming with Tiscali lol..
Just joking, aint that bad.
I shall now go wash my mouth out for swearing :laugh:
fixed! :)
ping bbc.co.uk
Pinging bbc.co.uk [212.58.224.131] with 32 bytes of data:
Reply from 212.58.224.131: bytes=32 time=20ms TTL=122
Reply from 212.58.224.131: bytes=32 time=22ms TTL=122
Reply from 212.58.224.131: bytes=32 time=21ms TTL=122
Reply from 212.58.224.131: bytes=32 time=23ms TTL=122
Ping statistics for 212.58.224.131:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 23ms, Average = 21ms
Better, at an average of 45ms, but still not back to normal. :'(
mine is better but still high in some places.. plus theres an extra hop now than before.
#3 is the extra one in my trace route above.
TBH, I have no idea whether there's an extra hop, but here's what I'm seeing:
ping www.bbc.co.uk -n 10
Pinging www.bbc.net.uk [212.58.253.75] with 32 bytes of data:
Reply from 212.58.253.75: bytes=32 time=24ms TTL=248
Reply from 212.58.253.75: bytes=32 time=27ms TTL=248
Reply from 212.58.253.75: bytes=32 time=25ms TTL=248
Reply from 212.58.253.75: bytes=32 time=26ms TTL=248
Reply from 212.58.253.75: bytes=32 time=25ms TTL=248
Reply from 212.58.253.75: bytes=32 time=23ms TTL=248
Reply from 212.58.253.75: bytes=32 time=25ms TTL=248
Reply from 212.58.253.75: bytes=32 time=30ms TTL=248
Reply from 212.58.253.75: bytes=32 time=24ms TTL=248
Reply from 212.58.253.75: bytes=32 time=25ms TTL=248
Ping statistics for 212.58.253.75:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 30ms, Average = 25ms
tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.253.75]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms home [192.168.1.254]
2 24 ms 41 ms 23 ms telehouse-gw2.idnet.net [212.69.63.55]
3 29 ms 29 ms 23 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
4 26 ms 25 ms 25 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 25 ms 23 ms 27 ms 212.58.238.133
6 27 ms 25 ms 25 ms fe0-0.rt0-frontpost.prodgw.bbc.co.uk [212.58.239
.222]
7 25 ms 25 ms 25 ms www6.cwwtf.bbc.co.uk [212.58.253.75]
Trace complete.
ping www.idnet.net -n 10
Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=38ms TTL=59
Reply from 212.69.36.10: bytes=32 time=28ms TTL=59
Reply from 212.69.36.10: bytes=32 time=42ms TTL=59
Reply from 212.69.36.10: bytes=32 time=29ms TTL=59
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=28ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=55ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms 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 = 27ms, Maximum = 55ms, Average = 35ms
That extra step could well be a new router, I guess.
I believe the third hop is new. I've always noticed that pings between IDNet devices are fairly high, though never really looked into why.
Simon has said in the past that they give low priority to pings.
Rik, do you know if the new hop at #3 (telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243]) is here to stay or just because of today work?
pings have gone bad again.... and here's my trace route
tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.251.203]
over a maximum of 30 hops:
1 1 ms 99 ms 99 ms speedtouch.lan [192.168.1.254]
2 93 ms 87 ms 79 ms telehouse-gw2.idnet.net [212.69.63.55]
3 96 ms 86 ms 112 ms telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
4 71 ms 61 ms 50 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 82 ms 78 ms 62 ms 212.58.238.149
6 80 ms 73 ms 81 ms 212.58.239.62
7 71 ms 69 ms 75 ms www3.telhc.bbc.co.uk [212.58.251.203]
Trace complete.
Quote from: Rik on Jan 12, 2008, 16:32:18
Simon has said in the past that they give low priority to pings.
I wonder if a traceroute from a UNIX/Linux machine would be different then, as they use UDP datagrams instead of ICMP echo requests.
Quote from: RostokMcSpoons on Jan 12, 2008, 16:36:32
pings have gone bad again.... and here's my trace route
I'm seeing the odd rogue reading, eg 355ms. :(
Quote from: Adam on Jan 12, 2008, 16:37:13
I wonder if a traceroute from a UNIX/Linux machine would be different then, as they use UDP datagrams instead of ICMP echo requests.
Can you try it?
IDnet still working on routing problems? Noticing some sites are sluggish now and pings are high again. Google for one is loading slow
Quote from: Ann on Jan 12, 2008, 10:41:21
Well I'm not happy. I've just been kicked off and reconnected at a synch rate of 6688.. I was at 8096. I do hope this isn't going to be permanent.
I seem to have gone from a sync of 8128 to 7616 today aswell, could be because I just changed to the 2700hgv though :-\.
Quote from: psp83 on Jan 12, 2008, 16:41:35
IDnet still working on routing problems? Noticing some sites are sluggish now and pings are high again. Google for one is loading slow
I don't know, Paul. I've got an email in to support, so I'm waiting to hear back.
Quote from: Rik on Jan 12, 2008, 16:38:10
Can you try it?
From a wireless device, the pings are high but lowish latency between the devices.
traceroute to www.bbc.co.uk (212.58.224.125), 30 hops max, 40 byte packets
1 home (192.168.1.254) 37.955 ms 39.268 ms 39.533 ms
2 telehouse-gw2.idnet.net (212.69.63.55) 155.577 ms 158.728 ms 158.997 ms
3 telehouse-gw3-gi0-1-400.idnet.net (212.69.63.243) 151.377 ms 151.580 ms 152.023 ms
4 rt-lonap-b.thdo.bbc.co.uk (193.203.5.91) 153.162 ms 153.532 ms 154.932 ms
5 212.58.238.133 (212.58.238.133) 163.846 ms 164.089 ms 164.290 ms
6 www25.thdo.bbc.co.uk (212.58.224.125) 165.013 ms 169.587 ms 188.103 ms
Which, presumably, supports the low priority theory?
Traceroute from a Linux box
[ted@localhost ~]$ su
Password:
[root@localhost ted]# traceroute
Version 1.4a12
Usage: traceroute [-dFInrvx] [-g gateway] [-i iface] [-f first_ttl]
[-m max_ttl] [ -p port] [-q nqueries] [-s src_addr] [-t tos]
[-w waittime] [-z pausemsecs] host [packetlen]
[root@localhost ted]# traceroute 82.133.85.65
traceroute to 82.133.85.65 (82.133.85.65), 30 hops max, 38 byte packets
1 home (192.168.1.254) 1.551 ms 1.421 ms 1.382 ms
2 telehouse-gw2-msdp.idnet.net (212.69.63.51) 45.648 ms 64.861 ms 49.279 ms
3 telehouse-gw3-gi0-1-400.idnet.net (212.69.63.243) 47.666 ms 48.797 ms 47. 256 ms
4 g3-35-501.cr05.hx2.bb.pipex.net (193.203.5.14) 49.158 ms 78.251 ms 51.642 ms
5 v3952.cr05.tn5.bb.pipex.net (62.72.137.9) 48.485 ms v3953.cr05.tn5.bb.pipex .net (62.72.137.29) 53.863 ms 48.982 ms
6 g1-1-6.ar01.tn5.bb.pipex.net (62.72.140.142) 47.301 ms 50.509 ms 47.326 m s
7 ge-0-0-0-3801.jolt-gw.cust.pipex.net (212.241.241.14) 47.135 ms 46.942 ms 51.091 ms
8 secure.jolt.co.uk (82.133.85.65) 48.993 ms 48.792 ms 49.376 ms
[root@localhost ted]#
Who let Pipex in?? :)
Quote from: Rik on Jan 12, 2008, 16:53:22
Which, presumably, supports the low priority theory?
Yes, that'd be correct. Though I see no real reason why ICMP Echo should have a lower priority.
Cisco devices give ICMP echo-reply packets that are aimed directly to their interfaces (as happens in traceroute but not ping (to a destination i.e. *through* the cisco device)) a low priority.
From my DSL line at home I'm seeing normal ping times but I'll keep an eye on it.
Simon
simons-mac-pro:~ simon$ ping 82.133.85.65
PING 82.133.85.65 (82.133.85.65): 56 data bytes
64 bytes from 82.133.85.65: icmp_seq=0 ttl=56 time=11.729 ms
64 bytes from 82.133.85.65: icmp_seq=1 ttl=56 time=12.294 ms
64 bytes from 82.133.85.65: icmp_seq=2 ttl=56 time=12.856 ms
64 bytes from 82.133.85.65: icmp_seq=3 ttl=56 time=12.175 ms
64 bytes from 82.133.85.65: icmp_seq=4 ttl=56 time=13.752 ms
64 bytes from 82.133.85.65: icmp_seq=5 ttl=56 time=12.324 ms
64 bytes from 82.133.85.65: icmp_seq=6 ttl=56 time=12.647 ms
64 bytes from 82.133.85.65: icmp_seq=7 ttl=56 time=12.203 ms
^C
--- 82.133.85.65 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max/stddev = 11.729/12.498/13.752/0.568 ms
simons-mac-pro:~ simon$ ping www.bbc.co.uk
PING www.bbc.net.uk (212.58.253.74): 56 data bytes
64 bytes from 212.58.253.74: icmp_seq=0 ttl=248 time=12.460 ms
64 bytes from 212.58.253.74: icmp_seq=1 ttl=248 time=12.777 ms
64 bytes from 212.58.253.74: icmp_seq=2 ttl=248 time=12.584 ms
64 bytes from 212.58.253.74: icmp_seq=3 ttl=248 time=12.904 ms
64 bytes from 212.58.253.74: icmp_seq=4 ttl=248 time=13.215 ms
64 bytes from 212.58.253.74: icmp_seq=5 ttl=248 time=12.545 ms
64 bytes from 212.58.253.74: icmp_seq=6 ttl=248 time=13.106 ms
64 bytes from 212.58.253.74: icmp_seq=7 ttl=248 time=12.673 ms
^C
--- www.bbc.net.uk ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max/stddev = 12.460/12.783/13.215/0.255 ms
simons-mac-pro:~ simon$
Hi You all, OK so I jumped in this morning thinking the fuss was all about the planed BT jobby. But my comments were still valid, I have never seen so many people slagging off Idnet and I was quite shocked. Things can go wrong and we all know that Idnet will sort it out as quick as they can and this once again proved the case. In this situation they obviously did not expect it to go wrong and did not feel a need to inform us, so what, the situation was soon in hand and they learned from their mistake. ;D Is it just me but I seem to be accessing page quicker than normal. :thup:
Quote from: Simon_idnet on Jan 12, 2008, 17:17:34
Cisco devices give ICMP echo-reply packets that are aimed directly to their interfaces (as happens in traceroute but not ping (to a destination i.e. *through* the cisco device)) a low priority.
Can I have your line please, Simon. :)
I'm now seeing times that are consistent at ~25ms to the BBC, a bit slower than normal, but I don't often test pings - especially on a Saturday afternoon.
To IDNet, though, is markedly slower than usual:
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=37ms TTL=59
Reply from 212.69.36.10: bytes=32 time=41ms TTL=59
Reply from 212.69.36.10: bytes=32 time=45ms TTL=59
Reply from 212.69.36.10: bytes=32 time=44ms 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 = 37ms, Maximum = 45ms, Average = 41ms
Quote from: Den on Jan 12, 2008, 17:19:21
Is it just me but I seem to be accessing page quicker than normal. :thup:
A number of people have reported a 'nippier' service, Den, though some of us do seem to be seeing slightly extended ping times.
As to your earlier comments, I agree that some people seemed to react very strongly to this morning's problems. Perhaps it's a sign that we now regard a 'net connection in the same way as any other utility, eg if we turn on the lights, we expect them to work - if we open the tap, we expect water to flow. People 'need' the net nowadays as never before.
Quote from: Simon_idnet on Jan 12, 2008, 17:17:34
Cisco devices give ICMP echo-reply packets that are aimed directly to their interfaces (as happens in traceroute but not ping (to a destination i.e. *through* the cisco device)) a low priority.
That makes sense. :) It isn't really an issue as UNIX/Linux uses UDP packets unless specified, just somewhat confusing when comparing it to a Windows traceroute. :P
something been going on today then ? :back:
:lol:
It has, Philip, it has. ;)
Quote from: Rik on Jan 12, 2008, 17:30:51
:lol:
It has, Philip, it has. ;)
being serious, we've not noticed any problems in Penzance, Meg has been on her lappy most of the morning and she usually lets me know if there's a problem. :mad:
Hope everything is OK for everyone now. :pray:
Quote from: Ann on Jan 12, 2008, 12:19:38
It's very coincidental.
Sync is not related to the ISP, Ann.
Quote from: The Doctor on Jan 12, 2008, 17:38:10
Meg has been on her lappy most of the morning and she usually lets me know if there's a problem. :mad:
Only
usually?? :)
Quote from: Sebby on Jan 12, 2008, 17:38:31
Sync is not related to the ISP, Ann.
No but as I said before... oh never mind.
Quote from: Rik on Jan 12, 2008, 13:34:07
Sorry, Sebby, missed this in the rush. How about the stats page, that has something about ISP connection establishment.
http://192.168.1.254/xslt?PAGE=J04&THISPAGE=J17&NEXTPAGE=J04
Thanks, Rik. In that case, it looks like I didn't lose the connection to IDNet after all. :)
ping times are back to normal. saying that.. every trace route i've done to my normal IP's/websites has an added 2ms to there time than it did last week.
eg, Jolt.co.uk, usual ping 15ms, Todays is 17ms.
but can't moan, wont notice that in games :P
will try again at usual gaming times.
Quote from: Ann on Jan 12, 2008, 17:40:22
No but as I said before... oh never mind.
I appreciate what you're saying - had you not been disconnected from the exchange, you wouldn't have sync'd lower. Obviouslu between the time you last sync'd (did you say around a month ago?) and now, more noise is around. Subsequently, your router has had to sync a bit lower to achieve the same target SNRM.
I understand how infuriating it can be, but any ISP - not just IDNet - do not control the connection between you and the exchange. Had you been disconnected from IDNet, your sync wouldn't have dropped, so this is a BT issue and not related to IDNet's maintenance.
All seems fine to me but we've been unable to ping any of our routers from 11am that are on idnet. Every other service seems fine.
Thanks
Theo
Quote from: theop on Jan 12, 2008, 19:59:13
All seems fine to me but we've been unable to ping any of our routers from 11am that are on idnet. Every other service seems fine.
Thanks
Theo
Welcome to the forum, Theo. :) I believe most of the issues have been resolved, though from the sound of it you have a custom setup. It may be worth contacting IDNet regarding your problem as I'm sure they'd be more than willing to get it resolved ASAP.
When I ping www.bbc.co.uk I get destination host unreachable but I can surf the BBC site no problem.
I just pinged www.jolt.co.uk and pings seem faster if anything as does IDNet:
Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=18ms TTL=56
Reply from 82.133.85.65: bytes=32 time=18ms TTL=56
Reply from 82.133.85.65: bytes=32 time=19ms TTL=56
Reply from 82.133.85.65: bytes=32 time=19ms TTL=56
Ping statistics for 82.133.85.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 19ms, Average = 18ms
Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=16ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms 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 = 16ms, Maximum = 21ms, Average = 18ms
They do seem to have calmed down now, so hopefully the problems have been sorted. :)
Hi Theo, and welcome to the forum - have a welcome karma!
Welcome Theo, have a welcome Karma.. :welc: :karmic:
Quote from: theop on Jan 12, 2008, 19:59:13
All seems fine to me but we've been unable to ping any of our routers from 11am that are on idnet. Every other service seems fine.
Hi Theo, welcome to IDNetters. :)
Have you contacted IDNet? If your problems are continuing, I think you need to let them know asap.
I'm still getting this if I ping www.bbc.co.uk:
Pinging www.bbc.net.uk [212.58.251.203] with 32 bytes of data:
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Ping statistics for 212.58.251.203:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
However surfing the BBC's site is working fine and pinging other sites also works fine, so it's not causing me any problems, just thought I would post incase it indicates some other problem that IDNet might need to know about. Also even though I typed ping www.bbc.co.uk it tried to ping www.bbc.net.uk ???
That's odd, Phil. I've just got this:
ping www.bbc.co.uk
Pinging www.bbc.net.uk [212.58.253.71] with 32 bytes of data:
Reply from 212.58.253.71: bytes=32 time=26ms TTL=249
Reply from 212.58.253.71: bytes=32 time=26ms TTL=249
Reply from 212.58.253.71: bytes=32 time=23ms TTL=249
Reply from 212.58.253.71: bytes=32 time=24ms TTL=249
Ping statistics for 212.58.253.71:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 26ms, Average = 24ms
It might be 2-3ms slower than usual, but otherwise it's fine. It always does the 'net' switch, btw - at least for me.
Anyone else seeing problems?
No problems here, fine.
My ping is 36ms to the bbc Rik, but no issue with things being unreachable
No. can ping everything and it all seems much snappier and faster. They did it for me. :)
I wouldn't know what a " ping " was if one hit me in the face Rik, but surfing is fine. ;)
If one did hit you in the face, In, you might know what it was afterwards?? ;D
Quote from: Inactive on Jan 13, 2008, 10:47:40
I wouldn't know what a " ping " was if one hit me in the face Rik, but surfing is fine. ;)
Ditto. ;D
Quote from: Noreen on Jan 13, 2008, 10:54:31
Ditto. ;D
Nice to know that I ain't alone Noreen.. :ty: :good:
Shall I tell you?
Tell us all PLEASE Rik ::)
Quote from: Rik on Jan 13, 2008, 10:59:41
Shall I tell you?
Go on then, you know you can't resist.. ;D
OK... A ping is a useful diagnostic for a connection. For example, if you are having trouble with your connection, a simple diagnostic would be to ping the router - this would quickly establish whether the computer and router are talking. From there, a ping to the BBC or other 'known good' site, can establish whether your connection is talking to the web at large.
In addition to establishing whether the connection is working, a ping tells you how fast the remote site is responding (latency). This figure is critical for gamers, they need low latency so that they can respond in a timely manner (before someone zaps them, iow :)).
To run a ping test, hit Start > Run > CMD <press Enter>
that will bring up a DOS-like window.
In that, type ping www.bbc.co.uk or ping <router address>.
The results look like the post above, and can be copied by right-clicking on the title bar of the window, selecting edit, then select all, press <Enter> to copy, paste in the normal way.
Thanks Rik, I am a little wiser now. ;)
Quote from: Inactive on Jan 13, 2008, 11:14:42
Thanks Rik, I am a little wiser now. ;)
Me too although I can'r see me ever using it. ;D
As I say, Noreen, it's a useful diagnostic if you have a problem. Beyond that, I find little use for pings - I just get on and use the service. :)
Pinging www.bbc.net.uk [212.58.253.74] with 32 bytes of data:
Reply from 212.58.253.74: bytes=32 time=31ms TTL=248
Reply from 212.58.253.74: bytes=32 time=30ms TTL=248
Reply from 212.58.253.74: bytes=32 time=31ms TTL=248
Reply from 212.58.253.74: bytes=32 time=35ms TTL=248
Ping statistics for 212.58.253.74:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 35ms, Average = 31ms
How far are you from London, Simon? About 60 miles or a bit less?
From the outskirts of London, about 35 miles, Rik.
Mmm. Maybe the routing is via Letchworth then, I thought it was to Telehouse...
Now you've lost me. Is mine good or bad then?
purplecloud has gone again.. it's not IDNet again is it?
Quote from: Simon on Jan 13, 2008, 11:42:44
Now you've lost me. Is mine good or bad then?
AFAIK, pings increase with distance (a bit like radar signals). So, someone in Scotland, say, will have longer ping times than someone in London (to a London site). Similarly, US sites will be slower than UK ones. I thought all IDNet routing ran through Telehouse, in London, therefore I would expect pings to decrease or increase with user distance from London.
Of course, we haven't discussed whether you have interleaving on. :)
Quote from: Ann on Jan 13, 2008, 11:43:16
purplecloud has gone again.. it's not IDNet again is it?
I wouldn't have thought so, Ann, 1&1 is fine.
Not my weekend really is it.. LOL.
But as for the ping situation, I have interleaving on or at least it was when last I checked (it's not easy to check and I'll have to remember how).. but my ping to the bbc was 28ms which seems quicker than I'd expect. I'm in Canterbury however many miles away from London that is.
A 28ms ping with interleaving on sounds fine, Ann. Are you experiencing difficulties with any other sites, or is it just PC?
I don't think so but it's hard to tell. PC going down on a Sunday is not good news.. I feel for them. Everything's gone, email, web, the lot.
It's certainly dead from here, Ann. :(
OK, just for interest I had a go. ;D
Pinging www.bbc.net.uk [212.58.253.72] with 32 bytes of data:
Reply from 212.58.253.72: bytes=32 time=22ms TTL=249
Reply from 212.58.253.72: bytes=32 time=21ms TTL=249
Reply from 212.58.253.72: bytes=32 time=21ms TTL=249
Reply from 212.58.253.72: bytes=32 time=21ms TTL=249
Ping statistics for 212.58.253.72:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 22ms, Average = 21ms
Do you have interleaving on, do you know, Noreen? The figures suggest you do.
How do I tell if I have interleaving on, and if I turn it off, will my pings get faster?
The router will usually show it, somewhere in its line stats, either by a direct reference (fast path=off), or by the error logs, where FECs indicate that interleaving is on.
You can't change it yourself, IDNet have to persuade BT to do it, but because it's used are part of the stabilisation process, it's not always easy to achieve.
Quote from: Rik on Jan 13, 2008, 12:04:56
Do you have interleaving on, do you know, Noreen? The figures suggest you do.
Sorry Rik, I've no idea. Where would I find it on my Netgear? Are those results good or bad?
Quote from: Ann on Jan 13, 2008, 11:43:16
purplecloud has gone again.. it's not IDNet again is it?
No, all other sites work. Purplecloud's own separate status page (http://"http://www.purplestatus.net/status/)shows everything down atm.
Thanks, Colin, at least we can't blame IDNet for this one then. :)
Quote from: Noreen on Jan 13, 2008, 12:10:58
Sorry Rik, I've no idea. Where would I find it on my Netgear? Are those results good or bad?
To get the results in a Netgear, Noreen, enter this in the browser address bar:
http://192.168.0.1/setup.cgi?todo=debug
which should result in a screen which just says 'Debug enable'.
(That's assuming that you haven't changed the router's IP address from the default).
Then exit from the web interface and open a command-line window. Type:
telnet 192.168.0.1
You should get a BusyBox welcome message to confirm that your telnet connection is established.
Now type:
cat proc/avalanche/avsar_modem_stats <ENTER>
You'll get a list of the error count. The numbers will be in either the fast path section or the interleaving one, iirc.
Your pings are about what I'd expect for an interleaved connection.
Quote from: Ann on Jan 13, 2008, 11:43:16
purplecloud has gone again.. it's not IDNet again is it?
Me too, Purple cloud has gone again, can't get to there website either:
http://www.purplecloud.com/home/
Quote from: Phil123 on Jan 13, 2008, 10:39:15
I'm still getting this if I ping www.bbc.co.uk:
Pinging www.bbc.net.uk [212.58.251.203] with 32 bytes of data:
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Ping statistics for 212.58.251.203:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
However surfing the BBC's site is working fine and pinging other sites also works fine, so it's not causing me any problems, just thought I would post incase it indicates some other problem that IDNet might need to know about. Also even though I typed ping www.bbc.co.uk it tried to ping www.bbc.net.uk ???
Just realised why I can't ping bbc.co.uk I had Pear Guardian on and this was blocking the BBC, all working fine now:
Pinging www.bbc.net.uk [212.58.253.75] with 32 bytes of data:
Reply from 212.58.253.75: bytes=32 time=18ms TTL=249
Reply from 212.58.253.75: bytes=32 time=23ms TTL=249
Reply from 212.58.253.75: bytes=32 time=18ms TTL=249
Reply from 212.58.253.75: bytes=32 time=18ms TTL=249
Ping statistics for 212.58.253.75:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 23ms, Average = 19ms
Phew. :)
Purplecloud now seems to be up again.
Double phew. ;D
I've got no problems as such here, although pings to BBC are higher. I used to get on average 31ms, and now I'm getting 41ms. It's no issue for me though as I'm not a gamer. :)
Are you comparing like for like, Sebby, ie have you checked your ping times on a Sunday before?
Yep. I used to get 31ms day or night and regardless of the day.
I've just tried again and it seems to have settled down, averaging 32ms.
I'm seeing 24ms, which is about 3ms higher than normal - but I'm not sure what normal really is as I only ever run a ping when there's a problem. ;)
Ping times have increased since yesterdays work..
I'm noticing upto 5ms increase on some sites.
Pinging www.bbc.net.uk [212.58.251.202] with 32 bytes of data:
Reply from 212.58.251.202: bytes=32 time=17ms TTL=249
Reply from 212.58.251.202: bytes=32 time=16ms TTL=249
Reply from 212.58.251.202: bytes=32 time=18ms TTL=249
Reply from 212.58.251.202: bytes=32 time=19ms TTL=249
Ping statistics for 212.58.251.202:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 19ms, Average = 17ms
Average used to be 15ms.
I know pings are fairly important for game players but to the rest of us it seems to make no difference to web browsing, emailing downloading etc. So is there too much importance being placed on ping times at the moment, as we already know that pings are given a low priority by IDNET.
Pings aren't given a low priority by IDNet, Alf, though they are by Cisco routers. I don't mean to split hairs, but the difference is critical to gamers.
For the rest of us, I agree, it makes no difference and I usually only check mine when prompted to by a post here. :)
Quote from: Lance on Jan 11, 2008, 22:48:41
It's one of the things we like about IDNet, they don't wait until they have the problem to get it fixed, but rather prevent the problem in the first place!
TO be fair that's what all ISPs do, until they're bought by Pipex :D
my pc shows that is connected at circa 6600k, the bt speedtest is showing a through put of 6336 k with a IP line profile of 7000k.................yet i aint had a download come down at over 350 kpbs all day, it normally downloads at rate of 660 kpbs - 800 kpbs..........is this connected to the maintenance in any way :( ???
I did not lose connection at my router during the 1st maintenance work carried out on saturday btw.
James
All of those figures look wrong, James, ie you shouldn't have a profile higher than your sync speed. It's almost as if the profile has changed, but not updated on the speed test. Can you try another test and see if it's still contradictory?
The upgrade yesterday should have improved speed if anything, not lowered it, and no-one else has reported an issue like yours, so I think we need to do some digging. If you can post the results of the BT test, together with your line stats from the router, maybe something will become evident.
ok rik, carried out 00.14
Test1 comprises of Best Effort Test: -provides background information.
IP profile for your line is - 7000 kbps
DSL connection rate: 448 kbps(UP-STREAM) 8000 kbps(DOWN-STREAM)
Actual IP throughput achieved during the test was - 5329 kbps
the 5329 kbps is way down
___________________________________________________________
Date 14/01/08 00:15:48
Speed Down 6449.69 Kbps ( 6.3 Mbps )
Speed Up 371.84 Kbps ( 0.4 Mbps )
Port 8095
Server speedtest1.adslguide.org.uk
I had this speedtest show speed down at 3.2 Mpbs about 23.00 hrs on sunday rik !!
_________________________________________________________________
from dsl zone uk
6687 Kbps
which is around 835.91 KB/s
including overheads
I had this give me 4500 Kpbs earlier too
________________________________________________________________
router stats
DSL Status
Connection Status Connected
Upstream Rate (Kbps) 448
Downstream Rate (Kbps) 8000
US Margin 26
DS Margin 10
Modulation MMODE
LOS Errors 0
DS Line Attenuation 21
US Line Attenuation 21
Path Mode Interleaved
DSL Statistics
______________________________________________________________
I carried out a download from microsoft downloads and it came down at 801 kpbs ( very good !! )though ive not had speed like that all day. what do you make of it rik, my bt speedtest through put is normally 6400 kpbs.
james
It's possible you have exchange congestion, James. Have you checked (http://usertools.plus.net/exchanges/)?
TBH, I don't put a lot of store by speed tests, except the BT one, as they fake the download by a variety of techniques, so they are, at best, an indicator. That's further complicated by the fact that the result will be dependent on the server load and the network status between you and the server, ie the bits outwith IDNet.
Your d/l from MS suggests that your inherent speed is OK, so at the moment I'm leaning towards congestion outside the IDNet network.
Virtual paths: Green
There are currently no known capacity problems on your exchange. There may still be an exchange problem, however BT are not currently reporting that they are aware of it. Please contact Support if you are having speed problems, who can advise further.
Record last updated: 31 Dec 07
just completed a 90mb download, took 2 min 7 secs at an average of 732 kpbs, it seems my system has received a good boot in the hole back into life.
strange ???
james
It could be that BT have been working at the exchange, they seem to do this at weekends... Or it could just be that the wind was from the wrong direction. ;) Keep an eye on things, see how it goes.
ta for looking at it for me rik :angel:
james
NP. :)
Quote from: Dont mention Talk Talk !! on Jan 14, 2008, 00:45:03
ta for looking at it for me rik :angel:
james
I bet you didn't get this kind of one to one service at gone midnight at Talk Talk... ;)
Whoops did I mention.....TT. ;D
Justr read this. My router log reported a couple of lost synchs for saturday. Didnt seem to cause any other problems.
update
09.00 am monday morning and didnt i just get a bleedin stale session ::)
phoned the boys at ID and was told to shut down the router for 15 mins ........i switched it off for 30 and bingo, back to 8000 / 448 ...............phew ;D
james
You did notice we headlined the board with stale session advice yesterday evening, didn't you, James. :)
Quote from: Rik on Jan 14, 2008, 09:35:45
You did notice we headlined the board with stale session advice yesterday evening, didn't you, James. :)
anybody else report getting any stale sessions ?
james
None that I've seen.
I had a cheese sarnie that was a bit hard around the edges, does that count? ;D
Seriously, no .. nothing at all here.
Quote from: Inactive on Jan 14, 2008, 00:56:06
I bet you didn't get this kind of one to one service at gone midnight at Talk Talk... ;)
Whoops did I mention.....TT. ;D
Had I have had this situation when with at Shyte Shyte it probably would have gone along these lines:
Me: I must ring up to see whats wrong here
Waiting for ages for phone to be picked up
TT: erm....yaaaaaawn......hello
Me: Ive got a .............
TT: Ill put you on hold ......yaaawn ......(phrrrrrrrt in background )
" call out the instigators.....theres something ......"
40 mins later
" we gotta bring it together now .........."
TT: Hello , how can we help you ?
Me : Ive got something wrong here..........
Line goes dead.
Not the same quality of service I think you might notice ;D :laugh: ;D and thats not exaggerated.
James
Sounds like a call to Sky. ::)
No problems here, perhaps Wales is exempt ;D
Wales is many things, Den. ;)
Quote from: Den on Jan 14, 2008, 09:47:31
No problems here, perhaps Wales is exempt ;D
mark webster winning that darts epic last night must have brought the welsh boys a bit o luck.
was that a match or what !!!!!!!!!!!!!!!!!!!!!! those 2 guys were dart throwing machines, Id be lucky to hit the board.
James
Talktalk when i was with them cut my line off like once a day. You call them after being offline for a day+ and you get redirected, re-explain, taken to india, re-explain, change pc config, disconnect, ring up, re-explain, redirected (all the while 80p a min) and they think its your pc all the while keeping you on for almost an hour of redialling etc. until finally "OH BT test says theres a fault on your line...we shall fix it shortly...
/Kill Talk_talk.cfg
Please :laugh:
Quote from: Dont mention Talk Talk !! on Jan 14, 2008, 09:38:55anybody else report getting any stale sessions ?
Nope. I switched everything off at midnight, switched on first thing this morning. It took one tweak via the DMT tool and I had the same sync as yesterday. Easy peasy.
Quote from: Rik on Jan 14, 2008, 09:46:36
Sounds like a call to Sky. ::)
Don't let a certain Think Broadband member hear you say that. :laugh:
;D
I speak very quietly over there...
I say nothing. It's a waste of energy. ;D
You have a point... ::)