Major Problems?

Desaan · Apr 22, 2011, 03:15:37

Since midnight, despite not being disconnected or re synced I'm getting nothing to load and when it does it takes about 10mins to load one page.
This has been happening FAR too much lately!

Tracing route to idnet.com [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.0.1
2 34 ms 31 ms 31 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 29 ms 30 ms * telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 30 ms * * redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 30 ms * 30 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 * * * Request timed out.
7 * * 29 ms 212.69.36.10

Trace complete.

C:\Users\Gary>tracert idnet.com
Unable to resolve target system name idnet.com.

C:\Users\Gary>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 192.168.0.1
2 35 ms 419 ms 30 ms 212.69.63.51
3 30 ms 30 ms 30 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 * * 168 ms 212.69.63.5
5 * * 30 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 * * * Request timed out.
7 30 ms * 30 ms 212.69.36.10

Trace complete.

Desaan · Apr 22, 2011, 03:21:07

aaaaaaaaaaaaand just as I post it seems to have woken up!

aaaaaaaaaaaaand it's gone again!

/givesup

zappaDPJ · Apr 22, 2011, 03:39:16

I've had the same issue, it started shortly after midnight. The symptom is packet loss but I've no idea what the cause is. For reference I'm in the North London area.

beeurd · Apr 22, 2011, 03:59:35

I appear to be having the same issue here in north Worcestershire.

Router appears to be connected fine at a 6.2Mbps, but the only websites I have found that I have access are BBC, Google, IDnet and this forum. Bit frustrating.

Athena · Apr 22, 2011, 04:20:26

Been having random DNS resolver issues, connection issues, you name it, started about two hours ago.

Lately there's been no end of issues and it's starting to wear on my patience. I know it's BT and all but surely the ISP's should start making noise about the shoddy service they're getting.

Desaan · Apr 22, 2011, 04:31:03

I'm in Liverpool for reference. Currently seeing between 25%-100% packet loss, this is some 4 and a half hours after it started. Brilliant.

Paxtonite · Apr 22, 2011, 04:44:05

I'm in Essex, and same problem here. Also getting a bit peeved with this continual problem.

Gary · Apr 22, 2011, 07:35:34

Same happened here at 1am I could not access any sites at all, I'm in West Sussex, totally fed up with what seems to be almost a weekly event now

Steve · Apr 22, 2011, 07:53:18

The packet loss seemed to correct itself around 05:00. No idea what the cause was.

Lance · Apr 22, 2011, 09:20:32

Although it's typical BT maintenance timing.

jameshurrell · Apr 22, 2011, 09:45:59

4 lines here monitored on TBB BQM graphs - three are IDNet, 1 is BT Retail. The three IDNet lines showed the packet loss, the BT retail one did not. Two of the lines (1 x BT and 1 x IDnet) are on the same exchange and go to the same building - so from that I guess it's easy to conclude that the problem seemed to be within the IDNet network somewhere.

Ardua · Apr 22, 2011, 09:46:50

Would this be the same as a "Timeout PPP Negotiation Failed'? It happened twice last night at 02.28 and again at 03.09 in the Worcestershire area? Fortunately, there has been no reduction in my connection speeds.

TheDuke · Apr 22, 2011, 09:50:14

I to had the same issue around that time, ignore the 100% packet loss for about an hour, the router was off.
Rochford Exchange in Essex

Was asleep during those hours so didn't really effect me.

dlorde · Apr 22, 2011, 09:58:15

Similar problem here in north east Kent, from midnight to 5am.

Bill · Apr 22, 2011, 10:35:40

I won't bother with the BQM trace, but the same out here in Oxfordshire.

JB · Apr 22, 2011, 10:37:07

Same again, in Cheshire.

Niall · Apr 22, 2011, 10:53:55

Last night I noticed my I couldn't connect to some pages and others were VERY slow to load. This was at 8:15. I was actually bored, sitting on the wall outside waiting for a taxi, so I rebooted the router from my phone (I felt like such a geek

) but it didn't seem to solve the issue. Everything seemed okay when I came back from town around midnight. Also, I noticed that a couple of wi-fi spots in town were having problems too. During the night, whilst being all bored and nerdy, I found two unsecured wi-fi connections in addition to the few free pub wi-fis around and they were having similar issues. Although that's not the best way to compare as I have no idea who these people were using as providers.

To be honest it smells of BT doing unscheduled/unnotified work again.

Oh, I'm in Wrexham.

esh · Apr 22, 2011, 12:44:45

My plot is absolutely clean, zero packet loss. gw5, Northampton way.

AzShane · Apr 22, 2011, 13:31:39

Same Packetloss showing here, Leicester

.Griff. · Apr 22, 2011, 13:44:26

Same here - Walsall

Technical Ben · Apr 22, 2011, 16:39:44

No problems here. Perfect speed and ping. On ASDL Vanilla.

AzShane · Apr 22, 2011, 16:48:12

Possible its limited to 21CN? or what ever the ASDL2+ thing is called

gyruss · Apr 22, 2011, 16:56:18

Don't think its limited, i had a total loss of internet this morning, and this last week my net has noticeably been dropping connections etc.

I gave up in the end this morning, the BT Wholesale message was rather boring to look at.

i'm on the up to 8mb service, router is in the hall, and no changes to my pc or cabling. All twisted pair. Shame really, i had quite a good winter and early months of this year with no issue, then all of a sudden it starts playing up. I'm simply not buying yet another router again this time, i threw £180 at it last time and there really IS a point where this should be fixed between the ISP and BT.. after all, they are the providers here.

Aaron · Apr 22, 2011, 19:28:24

Had problems browsing as well during the same time periods of midnight to 3am

jameshurrell · Apr 22, 2011, 19:44:14

Quote from: AzShane on Apr 22, 2011, 16:48:12
Possible its limited to 21CN? or what ever the ASDL2+ thing is called

No unfortunately not - of my three IDnet lines (yes I'm greedy

), two are bog standard ADSL up to 8MB, the other is 21CN ADSL2+... all had the problem...

ou7shined · Apr 22, 2011, 22:33:35

Identical Packet loss here, Aberdeen.

wecpcs · Apr 22, 2011, 23:14:04

Quote from: Technical Ben on Apr 22, 2011, 16:39:44
No problems here. Perfect speed and ping. On ASDL Vanilla.

No problems here all day either, also on ADSL Vanilla.

Colin

cavillas · Apr 23, 2011, 09:48:50

Check this SITE and see if it is afecting your connection. Everything has been ok at Walton on the Naze

T_M_D · Apr 26, 2011, 08:25:36

Quote from: Desaan on Apr 22, 2011, 03:15:37
Since midnight, despite not being disconnected or re synced I'm getting nothing to load and when it does it takes about 10mins to load one page.
This has been happening FAR too much lately!

Tracing route to idnet.com [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.0.1
2 34 ms 31 ms 31 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 29 ms 30 ms * telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 30 ms * * redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 30 ms * 30 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 * * * Request timed out.
7 * * 29 ms 212.69.36.10

Trace complete.

C:\Users\Gary>tracert idnet.com
Unable to resolve target system name idnet.com.

C:\Users\Gary>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 192.168.0.1
2 35 ms 419 ms 30 ms 212.69.63.51
3 30 ms 30 ms 30 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 * * 168 ms 212.69.63.5
5 * * 30 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 * * * Request timed out.
7 30 ms * 30 ms 212.69.36.10

Trace complete.

Hi Desaan, I have just read your post - sorry, I have been so taken up by my post over the weekend that I have not had time (or internet access) to look at other posts, but I also encountered packet losses of 25-50% using Tracert and ping from cmd.

I am wondering if my problem is the same as yours - I would be interested to know how things were for you after Friday as you stopped posting after then. Did you suffere further service loss over the weekend and Monday, are you still having issues?

Desaan · Apr 26, 2011, 17:56:27

Still having major issues, packet loss all over the place and a generally poor connection. Think it maybe about time to belatedly give IDNET the heave ho. This has been going on for far too long, it happened as recently as 10mins ago whereby I had 10 mins of insane packet loss but no loss of connection.

Steve · Apr 26, 2011, 17:58:33

Have you managed to speak support if not I encourage you to do so.

Desaan · Apr 26, 2011, 18:05:10

Quote from: Steve on Apr 26, 2011, 17:58:33
Have you managed to speak support if not I encourage you to do so.

To be honest Steve its pretty apparent from reading the boards that the issue is fairly wide spread and in no way limited to geography or client side issues with hardware etc. I doubt the support team could do anything for anyone with this issue as it very much appears to be some sort of internal/external infrastructure problem. I've been with IDNET for 5 years now but there comes a time when even I say enough is enough, for the price I'm paying (£25 a month) I'm not getting the quality of service of times gone by.

Hell, if it wasn't for the these forums I'd be just another blind sheep waving money around!

Rik · Apr 26, 2011, 18:07:07

We can shut down if that will help.

I would advise talking to support, though, the more people tell them, the better the chance of a solution.

Lance · Apr 26, 2011, 18:08:37

Over the last half hour I've had a maximum 5% packet loss according to my BQM graph - but during this I've been working over a IPSEC VPN connection, whilst the other half has been uploading various pictures and stuff. I've certainly not noticed any significant packet loss causing an impact on my connection.

Steve · Apr 26, 2011, 18:12:48

I agree with Rik unless people let support now, they may not be potentially aware or how widespread a problem may be. I for one except on Friday night (when it was almost universal from the reports of forum members) have no packet loss.

Desaan · Apr 26, 2011, 18:22:00

I've sent them an email, last attempt at blind faith

Another recent tracert/ping test done 5mins ago, no background d/l's going on and all router stats normal. Again notice the timeout causing the packet loss.

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

C:\Users\Gary>ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=29ms TTL=59
Request timed out.
Reply from 212.69.36.10: bytes=32 time=29ms TTL=59
Reply from 212.69.36.10: bytes=32 time=28ms TTL=59

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

C:\Users\Gary>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 192.168.0.1
2 138 ms 162 ms 29 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 32 ms 30 ms 28 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 29 ms 32 ms 30 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 31 ms 30 ms 30 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 29 ms 30 ms 29 ms www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\Gary>

Rik · Apr 26, 2011, 18:26:11

This won't be much consolation, Gary, but it may help to indicate the evasive nature of the problem:

ping www.idnet.com

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

Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms 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 = 13ms, Maximum = 14ms, Average = 13ms

tracert www.idnet.com

Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.1.254
2 55 ms 11 ms 11 ms 212.69.63.51
3 14 ms 13 ms 11 ms 212.69.63.245
4 14 ms 13 ms 11 ms 212.69.63.5
5 11 ms 11 ms 13 ms 212.69.63.225
6 14 ms 13 ms 13 ms 212.69.36.10

Trace complete.

Desaan · Apr 26, 2011, 18:28:12

You clearly have traffic priority with that insanely low ping and/or live inside the server!

Rik · Apr 26, 2011, 18:33:04

Bog standard ADSL2+ I promise. The business line, which is ADSL (if 2+ fails, ADSL tends to stay up) shaves a couple of milliseconds off the ping but otherwise looks the same.

My gut feeling has been for some time that BT built the network with insufficient capacity and, depending where you live, from time to time there will be spells of poor performance. Certainly, when 2+ launched, there were signs of BT moving capacity around, by re-routing, because they didn't have the backhaul to cope with the services they had sold. Sadly, proving that from outside the company is next to impossible (and I did have a stand up row with Ian Livingstone at the time!).

Bill · Apr 26, 2011, 18:43:40

Quote from: Rik on Apr 26, 2011, 18:33:04
My gut feeling has been for some time that BT built the network with insufficient capacity and, depending where you live, from time to time there will be spells of poor performance.

The problem with that Rik, is that BT claim to have added sufficient capacity to allow them remove the cap on Infinity, and the take-up of Infinity has also been much lower than they hoped.

So, assuming that's true, their should be plenty of capacity around...

I'm seeing more than normal packet loss too (though it's not high), see BQM link in sig.

Rik · Apr 26, 2011, 18:45:05

I know, Bill, and as I said, it's a gut instinct (at least in part), but it's hard to explain the variations any other way.

Steve · Apr 26, 2011, 18:49:06

Maybe a stupid and erroneous analogy, if you look at capacity, if you fill an empty pint milk bottle from another pint bottle and pour it fast you spill some -FTTC, pour it slowly no problem adslmax.

Rik · Apr 26, 2011, 18:51:39

I have this vision of BT engineers stationed at the exchanges with milk bottles now.

Glenn · Apr 26, 2011, 18:52:06

Use a funnel - congestion?

Lance · Apr 26, 2011, 18:52:33

Quote from: Rik on Apr 26, 2011, 18:51:39
I have this vision of BT engineers stationed at the exchanges with milk bottles now.

Only for their cups of tea, Rik.

Rik · Apr 26, 2011, 18:57:39

beeurd · Apr 27, 2011, 02:25:01

Got a reply from IDnet support today...

Basically just says that there had been no reported network issues at that time, and if I'm still having trouble to send more info over if it's still happening.
Bit of a disappointing response, considering. ¬_¬

Glenn · Apr 27, 2011, 08:34:17

Beeurd

If you can post your router stats and a BT speedtest, if you can get one, the guys here maybe able to offer somemore help.

Rik · Apr 27, 2011, 09:24:05

Hi and welcome to the forum, beeurd.

As Glenn says, give us some more info and we'll try to help.

Ray · Apr 27, 2011, 10:31:52

beeurd.

Simon · Apr 27, 2011, 10:40:25

Technical Ben · Apr 27, 2011, 16:21:40

Quote from: Steve on Apr 26, 2011, 18:49:06
Maybe a stupid and erroneous analogy, if you look at capacity, if you fill an empty pint milk bottle from another pint bottle and pour it fast you spill some -FTTC, pour it slowly no problem adslmax.

Or try racing down the M25 in your Lamborghini = problem when you meet a traffic jam!
Asdl = driving slowly, FTTC = driving fast. Not that there are any dangers with broadband, just traffic jams when the slow meets the fast.

gyruss · Apr 27, 2011, 19:21:09

As my connection is down to 1400 downsteam, and 300'ish up, did similar pings and tracert anyway. Tried with both idnet and opendns.

C:\>ping www.idnet.com

Pinging www.idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=42ms TTL=59
Reply from 212.69.36.10: bytes=32 time=125ms TTL=59
Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=87ms 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 = 42ms, Maximum = 129ms, Average = 95ms

C:\>tracert www.idnet.com

Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 42 ms 42 ms 41 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 41 ms 42 ms 50 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 184 ms 186 ms 254 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 96 ms 146 ms 65 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 107 ms 44 ms 42 ms www.idnet.net [212.69.36.10]

Trace complete.

cavillas · Apr 27, 2011, 19:33:54

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

C:\Windows\system32>tracert www.idnet.com

Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms READYSHARE [192.168.0.1]
2 25 ms 24 ms 23 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 25 ms 23 ms 24 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 24 ms 24 ms 23 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 24 ms 25 ms 24 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 26 ms 24 ms 24 ms www.idnet.net [212.69.36.10]

Trace complete.

C:\Windows\system32>tracert www.idnet.com

Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms READYSHARE [192.168.0.1]
2 26 ms 23 ms 23 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 22 ms 24 ms 24 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 24 ms 25 ms 23 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 24 ms 24 ms 24 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 24 ms 24 ms 24 ms www.idnet.net [212.69.36.10]

Trace complete.

On ordiniary adsl and from Frinton on sea excange and over 2.8 mles away.

.Griff. · Apr 27, 2011, 19:42:45

C:\>tracert www.idnet.com

Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 18 ms 18 ms 18 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 18 ms 18 ms 18 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 37 ms 275 ms 26 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 19 ms 21 ms 19 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 24 ms 19 ms 19 ms www.idnet.net [212.69.36.10]

Trace complete.

gyruss · Apr 27, 2011, 19:43:41

spikes at the redbus gw2? or is this normal?

Steve · Apr 27, 2011, 19:51:17

I expect will have low priority there. Was anything running on your first set?

gyruss · Apr 27, 2011, 19:56:49

nope. and pc had been on for 5 mins, so no background services doing their connect traffic.

Steve · Apr 27, 2011, 22:55:32

Your router stats looked OK in October has your downstream sync reduced a lot? If not are you not suffering from congestion at your local Exchange/VP

gyruss · Apr 28, 2011, 09:47:29

I'll have to check my routers stats tonight when i get home.

My stats in october were ok.. i enjoyed a 6mb connection throughout the whole of the rest of winter, and the first months of this year.. then we get this sunny weather in the last week or so and bam, suddenly i'm losing sync.. and getting slow speeds again (see my signature graphic for evidence).

I've got routerstats lite on my pc at home so i'll run that later, and i'll do a 17070 quiet line test next time it drops out too.

Netgear Router is still in the hall and connected to the filtered faceplate that bt assisted with last year.

No changes to any cabling, or pc's inside the house, and the hall is not a hot room either.