TERRIBLE PING ISSUES/PACKET LOSS AND SLOW INTERNET SPEED IN GENERAL. THROTTLING?

[insomniad]

http://www.pingtest.net/result/63573529.png

i dont understand how it can suddenly get so bad, it was fine 5 mins before

[insomniad]

http://www.pingtest.net/result/63573624.png

then this a few minutes later

[Jop]

The traceroutes show that on the first hop (your UBR) the pings are high and erratic, so it is likely to be an oversubscribed UBR.

Expect VM to tell you this is not the case for a month or two, before turning around and saying it is now at the limits they can pass it on to the network team.  Expect a long, bumpy and frustrating ride!

[insomniad]

lol cheers mate appreciate your input.  when i called them a while back it was apparently passed on to the network team.  hopefu;;y someone will see your message and agree its been like this pretty much all year so its nothing new

[Jen_A]

Hi insomniad,

Our Network Team have accepted the high utilisation issue that was escalated to them.

The fault reference for this is F001956722. They are currently awaiting a date for a Cat C resegmentation.

Please bump this post in a week or so, quoting the reference number, and we'll check for an update for you.

My apologies for the poor connection you have been experiencing, and whilst the resegmentation work will in all honesty not be a speedy fix, when the work is completed you will most definitely notice the difference.

[Jop]

While Cat C resegmentation may sound flashy and nice, the reality is that this is going to take ages to get done, possibly 3 or 4 months.

From a post by another forum staff:

Standard resegmentation takes place in the network headend in order to alleviate congestion on the network segment.

Where standard resegmentation is not able to resolve the issue a Cat C resegmentation is often needed. The Cat C resegmentation work is more in depth and time consuming. This type of work requires extra work to be carried out in the field and includes adding cabinets and fibres amongst other things.

[insomniad]

Hi Jen,

Thats great i'm glad to hear something has been done and that it has been escalated.

I completely understand that these things take time, as long as the problem gets 100% sorted i am fine with that.  It has got better lately compared to what it was but i can still see things aren't right

I will bump the post just over a weeks time then.

thanks for your help and the apology

Adam

[insomniad]

i spoke too soon, its going bad again

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

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=17ms TTL=241
Reply from 212.58.241.131: bytes=32 time=17ms TTL=241
Request timed out.
Reply from 212.58.241.131: bytes=32 time=157ms TTL=241

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

C:\Users\Adz>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:

  1     8 ms    75 ms     *     10.66.196.1
  2    16 ms    87 ms    91 ms  king-geam-1a-ge29.network.virginmedia.net [80.1.
61.242]
  3     8 ms     9 ms     7 ms  perr-geam-1a-tenge73.network.virginmedia.net [62
.30.247.69]
  4    13 ms   158 ms    39 ms  perr-core-2a-ae2-0.network.virginmedia.net [62.2
55.149.133]
  5     *      110 ms     *     manc-bb-1c-ae5-0.network.virginmedia.net [62.255
.149.65]
  6   120 ms    49 ms   177 ms  manc-bb-1d-ae2-0.network.virginmedia.net [62.253
.174.93]
  7    12 ms    13 ms    11 ms  manc-bb-1a-ae11-0.network.virginmedia.net [213.1
05.159.85]
  8    79 ms    20 ms     *     glfd-bb-1b-ae1-0.network.virginmedia.net [213.10
5.175.146]
  9    17 ms    38 ms    46 ms  glfd-tmr-1-ae5-0.network.virginmedia.net [213.10
5.159.46]
 10    56 ms    18 ms     *     tcl5-ic-1-as0-0.network.virginmedia.net [62.253.
185.78]
 11    16 ms    80 ms    17 ms  212.58.239.249
 12     *        *        *     Request timed out.
 13   106 ms     *       93 ms  ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
 14    17 ms    72 ms   190 ms  132.185.255.134
 15   101 ms     *      196 ms  212.58.241.131

Trace complete.

[insomniad]

http://www.pingtest.net/result/63739709.png

http://www.pingtest.net/result/63740015.png

http://www.pingtest.net/result/63740110.png

http://www.pingtest.net/result/63740185.png

[biggiev]

---

Jop wrote:

While Cat C resegmentation may sound flashy and nice, the reality is that this is going to take ages to get done, possibly 3 or 4 months.

From a post by another forum staff:

Standard resegmentation takes place in the network headend in order to alleviate congestion on the network segment.

Where standard resegmentation is not able to resolve the issue a Cat C resegmentation is often needed. The Cat C resegmentation work is more in depth and time consuming. This type of work requires extra work to be carried out in the field and includes adding cabinets and fibres amongst other things.

---

Which also means planning permission is required from the local council. If your local council is anything like mine. I wouldnt expect your net to be realistically fixed for the next 18 months. That number was quoted to me by their own cs staff when i arranged for my contract to be cancelled. In the interim, i'd continually ask for an interuption in service refund. 5-15 pounds is the norm. Have them pay your bill.

I'd also like to add that the cs staff was member was so shocked they were actually advising me who to leave for. So, they are just as mugged off as what their customer base is. This TIVO service is only going to make the situation worse.