Major Problems?

[ou7shined]

Identical Packet loss here, Aberdeen. 

[wecpcs]

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

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

Colin

[cavillas]

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

[T_M_D]

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]

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]

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

[Desaan]

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]

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]

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]

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]

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]

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]

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

[Rik]

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]

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]

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]

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]

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

[Glenn]

Use a funnel - congestion?

[Lance]

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

Only for their cups of tea, Rik. 

[Rik]

 

[beeurd]

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]

  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]

Hi and welcome to the forum, beeurd.

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

[Ray]

    beeurd.