Is there any known problems today ?
My connection seems slow even though speed test comes back good.
Pings are also higher than normal. I normally get around 15ms, today is spiking all over the place.
I've seen nothing here, Paul, pings are normal.
Ok, I'll give it an hour to see if it corrects itself, if not I'll phone support.
No problems here, in fact my ping is remarkably low just now.
(http://www.speedtest.net/result/773407850.png) (http://www.speedtest.net)
Looks like a phone call to support. Pings are getting worse.
Target Name: www.idnet.net
IP: 212.69.36.10
Date/Time: 4/6/2010 4:11:39 PM to 4/6/2010 4:13:54 PM
1 0ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.0.1]
2 107 ms 114 ms 107 ms 113 ms 101 ms 126 ms 109 ms 59 ms 67 ms 120 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 104 ms 111 ms 113 ms 114 ms 100 ms 125 ms 114 ms 54 ms 62 ms 184 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 108 ms 118 ms 112 ms 113 ms 105 ms 123 ms 113 ms 54 ms 64 ms 127 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 105 ms 118 ms 110 ms 111 ms 99 ms 117 ms 113 ms 62 ms 68 ms 133 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 104 ms 119 ms 109 ms 110 ms 99 ms 121 ms 112 ms 58 ms 68 ms 129 ms www.idnet.net [212.69.36.10]
Ping statistics for www.idnet.net
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 58ms, Maximum = 129ms, Average = 102ms
Have you seen the status announcement, Paul:
You may notice a delay in response to some queries sent to support@idnet.com
Please be advised; BT Wholesale and BT Openreach testing systems are currently off line due to major system failures. Further to this, their contact centres have also been taken off line.
As such, we are unable to perform diagnostic tests or raise faults for broadband and telephone services at this time.
Any support related queries will be dealt with as soon as the systems are back on line and relevant diagnostic checks have been carried out.
No problems here, Paul.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=16ms TTL=59
Reply from 212.69.36.10: bytes=32 time=16ms TTL=59
Reply from 212.69.36.10: bytes=32 time=17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms 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 = 22ms, Average = 17ms
My friend is on IDnet and on the same exchange and he's not getting any problems either. I've disconnected everything from my router and disabled wireless.
This PC is the only one connected (theres no background stuff running) and still getting high pings :(
Have you re-booted the router, Paul?
Quote from: Rik on Apr 06, 2010, 16:29:31
Have you re-booted the router, Paul?
No, Dont really want to either, with my current noise margin I'll be syncing way lower and I need the speed at the mo to download/upload stuff to FTP.
Something is wrong somewhere as its up and down. One moment its fine at 16 - 20 ms and the next its really high for a period of time.
Well, give support a call, but they'll be fairly limited in what they can suggest today.
Gave support a call, They say I shouldn't be seeing ping issues with speed results coming back fine. Doesn't really help me but oh well..
Will send an email with the requested pings.
I'm getting 10% packet lose now aswell!
Congested VP?
Dunno, Was fine yesterday, but been cr*p all day today.
Plus that would cause speed to drop aswell wouldnt it?
You would think, but I found that pings were improved by moving to a SuperMax product while speeds did not change, so it's not an absolute correlation.
Anyways, its in supports hands now.
I've done normal pings and pings in safe mode with networking enabled and emailed them the results.
I'm off to bed now to get rid of this migraine! :(
My sympathies, I know what they are like. :(
Quote from: Rik on Apr 06, 2010, 17:05:56
My sympathies, I know what they are like. :(
Can't sleep with neighbours dogs barking all the time :(
But pings seems to be getting better now.
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 192.168.0.1
2 19 ms 18 ms 19 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 103 ms 258 ms 67 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 25 ms 19 ms 19 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 23 ms 29 ms 26 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 20 ms 21 ms 20 ms www.idnet.net [212.69.36.10]
Trace complete.
Odd...
;D :pat:
Perhaps support gave something a kick? :dunno:
From what they say, they can't atm...
Ok, Just my line having a mood swing today then!
PMS? :evil:
Makes me wonder!
Might have to start buying it flowers and chocs so it plays nice :eek4:
;D
Whisper sweet nothings into the network card...
Aslongs I dont have to do anything else!! :evil: :eek4:
:lol:
;D
Not tonight...
I use to have problems with the PC or modem overheating. In this weather that's defiantly not the problem! :laugh:
Pings fine here on exchange (01326). But, d/l speed testers show as sub 3000 instead of my normal 14 to 18000. wth is going on??
Nothing showing on status pages AAISP,Plusnet or IDNet but the wholesale and Openreach systems were down earlier today.
Quote from: sobranie on Apr 06, 2010, 21:01:03
Pings fine here on exchange (01326). But, d/l speed testers show as sub 3000 instead of my normal 14 to 18000. wth is going on??
My line is also been having problems all day. This morning browsing seemed very slow and when I was accessing my on-line banking it kept stating my session had been disconnected. When I did a speed test with speedtest.net on the Maidenhead server my pings where normal but the needle refused to move at all on the download. After a router reboot no change so I did a complete router restart and I was getting about 3Mb instead of my normal 6-7Mb and my upload speed was 33% slower that usual. Tonight after yet another router restart my speeds are varying from 3Mb to my normal 6+, pings are fine but my upload speed is still a lot slower. As my exchange (01795) was on BT's list of affected sites recently, I can only assume the problem is still ongoing.
Colin
Edit
Even posting this message it took over 30secs to upload.
Not that it's any help, but no delays here this evening.
Quote from: Simon on Apr 06, 2010, 22:28:27
Not that it's any help, but no delays here this evening.
After the previous router restart, I decided to restart the PC as well and now everything seems normal regarding download/upload speeds and ping, but browsing still seems a lot slower than usual.
Colin
Back to normal now and a little improved too.
Download speedachieved during the test was - 18400 Kbps
For your connection, the acceptable range of speedsis 1000-99999 Kbps.
Additional Information:
Your DSL Connection Rate :19535 Kbps(DOWN-STREAM), 1183 Kbps(UP-STREAM)
IP Profile for your line is - 17000 Kbps
The throughput of Best Efforts (BE) classes achieved during the test is - 16.82:22.88:60.3 (SBE:NBE:PBE)
Quote from: sobranie on Apr 07, 2010, 01:31:05
Back to normal now and a little improved too.
Download speedachieved during the test was - 18400 Kbps
For your connection, the acceptable range of speedsis 1000-99999 Kbps.
Additional Information:
Your DSL Connection Rate :19535 Kbps(DOWN-STREAM), 1183 Kbps(UP-STREAM)
IP Profile for your line is - 17000 Kbps
The throughput of Best Efforts (BE) classes achieved during the test is - 16.82:22.88:60.3 (SBE:NBE:PBE)
Mine is back to normal as well, but I wonder exactly what the problem was, BT I expect.
Colin
My pings are lower today, Its not a moan but pings are still higher, I normally get 15ms but since whatever happened yesterday they have stayed around 21ms.
Something must have changed on my line. I wonder if interleaving has been enabled, support did put a block on it being enabled when I was on adsl1.
Typical. Spoke to soon.
Ping test from the routers diagnostics page (to bypas windows)
PING 212.69.36.10 (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=60 time=45.0 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=60 time=55.0 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=60 time=45.0 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=60 time=20.0 ms
--- 212.69.36.10 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 20.0/41.2/55.0 ms
Pings are creaping up again.
Over the last 10 mins.
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 192.168.0.1
2 20 ms 19 ms 19 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 19 ms 19 ms 19 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 19 ms 18 ms 19 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 20 ms 20 ms 21 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 20 ms 20 ms 19 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 192.168.0.1
2 25 ms 25 ms 26 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 28 ms 29 ms 28 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 43 ms 51 ms 58 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 41 ms 45 ms 45 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 36 ms 35 ms 35 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 192.168.0.1
2 19 ms 19 ms 19 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 25 ms 25 ms 26 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 49 ms 49 ms 46 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 44 ms 47 ms 46 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 57 ms 54 ms 53 ms www.idnet.net [212.69.36.10]
Trace complete.
C:\Users\Paul>tracert www.psp83.co.uk
Tracing route to psp83.co.uk [77.92.89.1]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.1
2 60 ms 64 ms 80 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 50 ms 41 ms 40 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 54 ms 53 ms 51 ms linx.uk2net.com [195.66.224.19]
5 43 ms 42 ms 50 ms dc5-1.uk2.net [83.170.70.134]
6 51 ms 54 ms 62 ms atlas.safeukdns.net [77.92.89.1]
Trace complete.
C:\Users\Paul>tracert www.psp83.co.uk
Tracing route to psp83.co.uk [77.92.89.1]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.1
2 19 ms 18 ms 18 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 19 ms 18 ms 19 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 19 ms 18 ms 19 ms linx.uk2net.com [195.66.224.19]
5 21 ms 18 ms 20 ms dc5-1.uk2.net [83.170.70.134]
6 21 ms 19 ms 18 ms atlas.safeukdns.net [77.92.89.1]
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 192.168.0.1
2 79 ms 81 ms 74 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 88 ms 90 ms 95 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 84 ms 76 ms 75 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 46 ms 50 ms 56 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 80 ms 80 ms 73 ms www.idnet.net [212.69.36.10]
Trace complete.
As you can see, one moment its fine the next its not.
Check with support, I know what I think, Paul, but they'll be able to tell you for sure.
Congestion? Surely that would show in the evening and not day ?
Not always, Paul, it's the school holidays...
Do you know if the BT computer problems has been fixed yet? No point phoning support until it is.
I haven't heard, Paul.
"For the last 2 days all 21CN-BS BRASs have been showing increased peak and minimum latency between the hours of 9am - 5pm."
So say the broadband gods of AAISP.
I put it down to the school holiday effect :(
So did I, Lance, we see this so often.
I hereby move to ban school holidays.
I'll second the motion. :)
Quote from: esh on Apr 07, 2010, 12:34:22
"For the last 2 days all 21CN-BS BRASs have been showing increased peak and minimum latency between the hours of 9am - 5pm."
So say the broadband gods of AAISP.
Thats what I'm seeing. Last night it cleared in the evening but back again today. I bet it clears up tonight again.
Well thats weird.
I've noticed that since being on ADSL2, When support check your line / run diagnostics it now disconnects me. Never happened on ADSL1.
Can't wait for the holidays to be over, Pings getting higher and higher!
I've never had that happen, Paul, except on one occasion when they warned me it would.
Happened both times support has checked my line now, Doesn't worry me thou, everytime they do it I sync higher! ;D
I must get them to test my line more often. ;D
lol..
Just a little frustrated with support at the mo :(
Why?
Quote from: Rik on Apr 07, 2010, 15:20:30
Why?
It just seems like they don't want to look into it or care. Thats twice now it feels like they've just pushed it to the side.
QuoteThe ping results carried out using the Windows command prompt with the PC booted into safe mode are perfectly fine and show no problems although are an improvement over the initial pings when not booted into safe mode. The connection is currently on fast path so has not been interleaved. it may be worth testing the connection using a different router and PC on the connection to determine if any improvement is seen.
As I replied to the email, I dont think those pings are acceptable, esp for voice comms and online games and with todays pings being over 120ms.
Also said I've tried with Vista, Win 7, XP and Linux, Plus this is my 4th router in 3yrs since being with IDnet and since I've joined I've always had a ping around 15ms (except when BT delayed the pipe upgrade for IDnet)
And that it can't be the router if my pings went back to normal last night after 6pm.
It's difficult for them too look into. Ping times are no part of the BT spec for the service, so it's virtually impossible to raise a fault on it. They seem to be suggesting the possibilities for any local issues, so that you can try them if you want to. The fact that pings improved after 6pm tallies with my theory that it's exchange congestion during the school holidays, we see it at Christmas as well. The fact that safe mode improved things, as I read it, says that there's some background process affecting the machine.
I'll see if I can find out anything more for you.
Today I've been doing all my ping tests directly from the router so windows is not there to causes any problems, everytime I've done it, pings have been into the hundred+ range, I also do it from XP on my netbook over wireless and from this main pc (ethernet) from command prompt so I get an average, I know operating systems always adds a few ms ontop, I allow for 10ms to be added.
I think its congestion aswell, as its getting later my pings are dropping slowly. Its just frustrating. I was meant to have a voice chat with a firm in india today about some work but can't because of it breaking up / not connecting.
From this earlier :
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 192.168.0.1
2 124 ms 117 ms 119 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 113 ms 113 ms 121 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 136 ms 132 ms 124 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 131 ms 125 ms 117 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 121 ms 122 ms 130 ms www.idnet.net [212.69.36.10]
Trace complete.
To now :
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 192.168.0.1
2 35 ms 35 ms 36 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 37 ms 37 ms 40 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 27 ms 22 ms 21 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 21 ms 21 ms 22 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 22 ms 18 ms 20 ms www.idnet.net [212.69.36.10]
Trace complete.
Have you tried doing a speedtest when the pings are high?
Yeh, speed test always come back fine, between 4.5mb - 5.3mb on a 5500 profile.
Which would argue against congestion. As there are no widespread reports of ping issues, that leaves is with a local problem, your pings are consistently around the same level at every hop of the tracert.
And its weird AAISP has posted something on there status page saying about increased ping times between 9am - 5pm for the past 2 days, exactly when my problems started.
My mate is on ADSL1 on the same exchange and he has no problems which makes me believe the AAISP post is correct or something along them lines.
I'll ask...
And to prove my point even more..
Directly from the router :
PING 212.69.36.10 (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=60 time=15.0 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=60 time=15.0 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=60 time=15.0 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=60 time=15.0 ms
--- 212.69.36.10 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 15.0/15.0/15.0 ms
From this pc :
C:\Users\Paul>tracert www.idnet.net
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms 192.168.0.1
2 26 ms 19 ms 19 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 19 ms 19 ms 19 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 20 ms 19 ms 18 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 20 ms 19 ms 19 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 19 ms 20 ms 20 ms www.idnet.net [212.69.36.10]
Trace complete.
Its getting towards the evening and pings starting to get low again.
Quote from: psp83 on Apr 07, 2010, 16:06:33
And its weird AAISP has posted something on there status page saying about increased ping times between 9am - 5pm for the past 2 days, exactly when my problems started.
It goes on too say it's only affecting 1.88% of users, Paul, which seems contradictory. My pings remain at 13-15ms, so clearly it's not as simple as AAISP report. BT have not advised IDNet of any issues, so IDNet are checking and will let me know.
Cheers. I put in the email to support about the AAISP post anyways. Its weird that my problems started the same time they noticed an issue with 21cn lines and was fine before.
And as my pings show above.. they get better as the evening gets here.
BT deny all knowledge of the AAISP claim. There are, however, a series of emergency planned engineering works, starting tonight in north and east London, to increase capacity on 21CN. This should not be affecting you however, particularly given the speeds you are seeing. Typically, if affacted (and I have been in the past), speeds will drop to 5-600k.
Typical BT though, Deny everything!
Just got an email from Simon, Looks like I will have to dig through the loft to find my other netgear out.
It does...
Quote from: Rik on Apr 07, 2010, 15:59:09
Which would argue against congestion. As there are no widespread reports of ping issues, that leaves is with a local problem, your pings are consistently around the same level at every hop of the tracert.
I got some days with high bandwidth, but low pings (latency) when I was on O2. That was down to congestion on the virtual path (if that's the correct name). My exchange gets no congestion, but O2 did not have the bandwidth.
Other than that, have you done traces throughout the day? Could it be possible the connection is going over more "hops" when the ping is high?
[edit] Oh, could it be maintenance in the day? Like someone digging the road up?
Well whatever BT is doing tonight my connection is really cr*p at the mo.
Websites taking ages to load.
(http://www.speedtest.net/result/775103004.png) (http://www.speedtest.net)
Just hope its better when I get up.
(http://www.speedtest.net/result/775111539.png) (http://www.speedtest.net)
:eek4:
Time for bed I think.
Your results don't quite make sense, Paul, slower speeds and lower pings are the opposite of what I'd expect to see with congestion.
Nice and steady 12ms +/- 0.5ms from where I am at, not that that's any surprise or consolation.
The only relation I can think of Rik, is that ping times obviously decrease with packet size. Though it would be far too strange to see *that* changing. It just sounds like a terrible misconfiguration somewhere along the line I'd guess...
It still 'feels' like a congested VP to me, esh...
Perhaps the load balancing is wonky. That would be indirectly related to congestion.
There's no load balancing as such, now that everyone is on the hostlink.
Ah, yes... well I guess we're just back to congestion now :( I've only had it really bad once and luckily a router reset made it all go away.
You see, people should run fancy plotting software like mine and make a gigantic graph with ludicrously arbitrary numerical schemes and then try and make sense of it all. It's the way forward! :angel:
;D
I struggle to make sense of life. ;)
Quote from: Rik on Apr 08, 2010, 08:40:10
Your results don't quite make sense, Paul, slower speeds and lower pings are the opposite of what I'd expect to see with congestion.
Welcome to the world of my line! ;D
I've just put my old router in, My trusted Netgear DG834G.
Pings are up and down but gunna give it 30 mins to settle in and warm up since its been in the cold loft for months.
One thing I have noticed, I get better stats from this one.
ADSL Link Downstream Upstream
Connection Speed 7048 kbps 1024 kbps
Line Attenuation 39 db 11.5 db
Noise Margin 15 db 5 db
500k increase on downstream,
200k increase on upstream,
downstream line attenuation has dropped from 42 to 39.
So maybe the new router started to dislike my line?
Well pings have seem to settle..
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 80 ms 75 ms 72 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 83 ms 84 ms 81 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 76 ms 77 ms 80 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 78 ms 83 ms 82 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 63 ms 66 ms 64 ms www.idnet.net [212.69.36.10]
Trace complete.
(http://www.speedtest.net/result/775621515.png) (http://www.speedtest.net)
:(
:grrr:
So are things better or not, Paul?
No, Still high pings with this 2nd router.
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 96 ms 94 ms 97 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 84 ms 86 ms 89 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 111 ms 110 ms 118 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 110 ms 109 ms 100 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 101 ms 105 ms 106 ms www.idnet.net [212.69.36.10]
Trace complete.
PING 212.69.36.10 (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=60 time=130.0 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=60 time=100.0 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=60 time=120.0 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=60 time=100.0 ms
--- 212.69.36.10 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 100.0/112.5/130.0 ms
Getting the same thing from support each time I phone, Just at the stage of giving up.
The same thing being? How are you pinging, manually or via software like ping plotter?
Pings are not guaranteed, nothing they can do etc.
I do ping tests from command prompt and from the diagnostic page on the router.
This one is done by command prompt ran as admin.
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 96 ms 94 ms 97 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 84 ms 86 ms 89 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 111 ms 110 ms 118 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 110 ms 109 ms 100 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 101 ms 105 ms 106 ms www.idnet.net [212.69.36.10]
Trace complete.
This one is done from the diagnostics page on the router
PING 212.69.36.10 (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=60 time=130.0 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=60 time=100.0 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=60 time=120.0 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=60 time=100.0 ms
--- 212.69.36.10 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 100.0/112.5/130.0 ms
Well, they are right, I said before that pings are not considered in BT's service spec. About the only thing I can suggest is to move to a business package if you're not already on one...
And my arguement with support is, how can I have great low pings of 15ms for 3yrs then suddenly one night everything changes without a reason. Something must be wrong somewhere. I've done all the test support has asked me to do.
Quote from: Rik on Apr 08, 2010, 15:14:12
Well, they are right, I said before that pings are not considered in BT's service spec. About the only thing I can suggest is to move to a business package if you're not already on one...
Sorry but I'm not paying more money for less of a service. If I do move, it'll be to another ISP that charges less if I cant get the low pings.
I can understand that. If you have LLU available, that should escape the issues of BT's inadequacies.
I'm gunna wait until AAISP stop reporting a problem and see if it clears my problem up aswell.
QuoteDetails
Yesterday 11:58:18
For the last 2 days all 21CN-BS BRASs have been showing increased peak and minimum latency between the hours of 9am - 5pm.
BT have been advised and are investigating
Update
Yesterday 14:55:10
BT have raised an incident, and BTO are investigating.
Update
Yesterday 16:50:06
Upgrade is required to fix the problem.
BT are working on it.
Update
Today 10:29:13
Still awaiting update on the required upgrade.
Update
Today 15:00:08
Upgrade is still under planning.
If it doesn't show no improvement on the 20th, when the kids are back at school then I will be looking for a new ISP.
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 25 ms 17 ms 18 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 17 ms 17 ms 16 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 20 ms 20 ms 17 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 17 ms 18 ms 17 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 18 ms 17 ms 17 ms www.idnet.net [212.69.36.10]
Trace complete.
First set of pings to come back under 20ms in the afternoon for a few days :eek4:
It's sunny, the kids are outside?
This big kid was just now ;D
Quote from: Rik on Apr 08, 2010, 16:17:51
It's sunny, the kids are outside?
Its been sunny with blue skys all week here. Perhaps thats the cause ;)
Quote from: psp83 on Apr 08, 2010, 16:21:26
Its been sunny with blue skys all week here. Perhaps thats the cause ;)
I must move. :)
Sounds good, if too much like hard work for me. ;)
Rik, you don't want to move here. If you want to die with boredom then do so, if not, stay well away ;D
Hoping to get away from this town soon once I get my business backup and running 100% again.
And on a good note, Simon just replied to my rather frustrated email I sent today (I've apologised for it now)
QuoteIt would appear that your Exchange has reached its current capacity. We'll see if we can find out from BT when they expect to have upgraded the capacity in your exchange.
I guess BT never put in enough capacity when they enabled our exchange.
They never do, Paul, they put in enough for today, then accept 100 orders tomorrow.
QuoteYour Exchange is reported as under-capacity and yet your symptoms are classic of congestion there.
So guess its going to be a waiting game, Hope it is congestion and BT upgrade soon.
i'm starting to be put off switching over now :(
If you are happy with your speeds, service and allowed bandwidth now Baz, I wouldn't.
I only really did it for the extra upload.
Quote from: psp83 on Apr 08, 2010, 16:56:10
So guess its going to be a waiting game, Hope it is congestion and BT upgrade soon.
This is the problem ISPs face. All the signs of congestion are there, but BT deny any issue. Then, miraculously, one day the problem disappears... :shake:
A case of BT not wanting to admit (when have they?) or they still dont know there own stuff yet!
If we recall before the hostlink appeared the classic sign of congestion was high and varied pings combined with variable throughput. I think we have evidence that BT21CN is over subscribed and if your own VP is at capacity,then when the exchange is busy you are going to struggle. You can alleviate the exchange congestion by paying for exchange priority but is it worth the extra cost. I don't think there is a lot of logic why suddenly the exchange VP becomes congested, mine appeared overnight and has got a lot better recently since BT increased the exchange capacity.
I feel it's an unwillingness to admit, Paul. We've seen it so often, the problem appears, ISPs start to raise it, BT deny the issue, suddenly the problem goes away. From what I've heard, they have still been juggling the capacity on WBC recently, moving it from one place to another as complaints rise. I've certainly seen that on my own line, with speeds of <600k on a 3.5M profile.
Quote from: psp83 on Apr 08, 2010, 16:58:50
If you are happy with your speeds, service and allowed bandwidth now Baz, I wouldn't.
I only really did it for the extra upload.
i am seriously thinking about NOT switching,applied two weeks ago and was told a date,as you may remember,and BT said there was not enough capacity in the exchange.could this be a sign i'm starting to think
It's an indication of the problem we are talking about, Baz. BT will happily accept orders for capacity they simply don't have.
Quote from: Rik on Apr 08, 2010, 17:01:53
This is the problem ISPs face. All the signs of congestion are there, but BT deny any issue. Then, miraculously, one day the problem disappears... :shake:
Sorry I ever doubted you Rik! But after BT denying Exchange congestion, Virtual path congestion was the only other thing I could think of that would do this. (Other than the local pigeons sleeping on the line from 4pm onwards. :laugh:)
Oh, it seems to be the rule of thumb when it comes down to capacity. O2 and Sky should be forced to sell their home access [bt reselling] services
VP and backhaul are the two issues that seem to occur most commonly, Ben. Luckily, BT haven't found a way to connect two lines to the same MSAN port or we'd see issues there too. :sigh:
Give them time ;)
;D
I thought that as I posted...
Quote from: Rik on Apr 08, 2010, 17:52:30
VP and backhaul are the two issues that seem to occur most commonly, Ben. Luckily, BT haven't found a way to connect two lines to the same MSAN port or we'd see issues there too. :sigh:
Except for the times the engineer sees a free hole in the board and just plugs in the cable and hopes for the best?
;D
I think I know of an occasion where that actually happened.
Pings have been more stable today.
C:\Users\Paul>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=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 23ms, Average = 20ms
Theres been a few times its been high but came down quick.
It's Friday. ;)
Just thought I would update this post.
Pings have been fine since my last post.
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 14 ms 13 ms 13 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 13 ms 13 ms 14 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 14 ms 14 ms 14 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 14 ms 14 ms 14 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 14 ms 14 ms 13 ms www.idnet.net [212.69.36.10]
Trace complete.
PING 212.69.36.10 (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=60 time=10.0 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=60 time=10.0 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=60 time=10.0 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=60 time=10.0 ms
--- 212.69.36.10 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 10.0/10.0/10.0 ms
That's good, Paul, thanks. :thumb: