50M : Think Broadband Ping Monitor Results (POST YOURS)

[dwarven]

And they still keep pushing back the fix for my problem, last month it was moved from mid feb to mid march, and I got this reply when asking for an update this month :

Hi dwarven,



Issue ref: F001996558 is showing a target fix date for 19/06/2013.



My apologies for the longer than usual amount of time it is taking to rectify this. The original problem was with utilisation on the upstream channel. An additional upstream was implemented in the latter part of last year.

Once that work was completed, after careful monitoring, it was noted that utilisation was affecting the downstream channel.

The current planned upgrade works are to remedy this.



This does mean, however, that for you the date is being altered often. I am sorry about this, if it were at all possible we would get this resolved faster.

Please make sure you request your month-by-month credit, which, whilst not ideal should at least go some way towards making the wait a little less of an ordeal.

Another 3 months now just gets worse and worse

[qasdfdsaq]

Lol.

VM capacity management SNAFU...

[dwarven]

Originally Posted by qasdfdsaq

Lol.

VM capacity management SNAFU...

Indeed you would think capacity would have been considered BEFORE doing the speed upgrades not after, I know naïve.

What really annoys me is I have to phone up to request a credit on my account because of their continual failures.

[Kushan]

Unfortunately, this kind of thing is very typical when dealing with capacity problems.

[Sephiroth]

Originally Posted by dwarven

Indeed you would think capacity would have been considered BEFORE doing the speed upgrades not after, I know naïve.

What really annoys me is I have to phone up to request a credit on my account because of their continual failures.

I hope that VM have added this to their lessons learned file. Release the upstream constraint and the downstream (that depends on upstream) demand rises significantly

[dwarven]

Originally Posted by Sephiroth

I hope that VM have added this to their lessons learned file. Release the upstream constraint and the downstream (that depends on upstream) demand rises significantly

Would hope so but its more likely to end up in the bin

[Qtx]

Originally Posted by dwarven

Another 3 months now just gets worse and worse

The moving fix dates were the reason I left VM. The last one they gave me meant I would have waited a year for the fix in the end.

If they told you at the start that it would take 6 months or whatever to fix, customers would leave them. So the shorter moving resolution dates does retain customers.

The actual resolution date for my VM down/upstream issue still a month away lol

[roughbeast]

Has the mid-evening bump returned?



Rubbish speed tests too.



Pingcraptic!



Here's the tracert:

Tracing route to speedtest4.thinkbroadband.com [80.249.107.197]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms REDDWARF [192.168.1.1]
2 11 ms 8 ms 7 ms 10.14.112.1
3 9 ms 10 ms 7 ms brhm-core-2a-ae3-1179.network.virginmedia.net [2
13.106.229.161]
4 37 ms 40 ms 39 ms brhm-bb-1c-ae17-0.network.virginmedia.net [62.25
3.174.73]
5 41 ms 42 ms 47 ms nrth-bb-1c-et-400-0.network.virginmedia.net [62.
253.174.226]
6 39 ms 39 ms 44 ms nrth-bb-1b-ae11-0.network.virginmedia.net [62.25
3.174.109]
7 41 ms 42 ms 41 ms tele-ic-4-ae0-0.network.virginmedia.net [62.253.
174.18]
8 38 ms 39 ms 41 ms linx-gw1.thn.ncuk.net [195.66.224.240]
9 40 ms 41 ms 42 ms speedtest4.thinkbroadband.com [80.249.107.197]

Trace complete.

OK to the head end. Downhill from then on.

Any similar problems out there today?

PS Ignore the spikes. I have never figured those out!

[thenry]

'ps'.. samknows kit may be?

those humps are not on my tbb or f8lure monitors.

[roughbeast]

Originally Posted by thenry

samknows kit may be?

those humps are not on my tbb or f8lure monitors.

The spikes you mean. I had those before I had SamKnows. They aren't the main problem.

[thenry]

your on shared network capacity. it can be someone else running it which is on the same connection channels as you.

[roughbeast]

Originally Posted by thenry

your on shared network capacity. it can be someone else running it which is on the same connection channels as you.

OK. That makes sense. The spikes don't affect my service particularly. They don't last long enough.

However the elephant in the room, yesterday's mid-evening bump and this evening's definitely do.

[dwarven]

Had the bump return as well yesterday and today :





Makes what is currently a bad service terrible

[Sephiroth]

I think what TH meant to ask is during the humps, what were you doing? P2P; Uploading?

That would amplify on TBB whatever interference you get from others on your segment.

BTW, your traceroute - the first three hops take you past the Head End so I don't really understand your comment. The ping times from hop 4 onward are consistent and not at odds with peak times. I've seen much, much worse. But that consistency indicates that the bottleneck is at hop 4. I've confirmed that with my own tracert to your CMTS (at the local head end).

Tracing route to cove-cmts-12-ge130.network.virginmedia.net
over a maximum of 30 hops:

1 27 ms <1 ms <1 ms 192.168.1.1
2 6 ms 7 ms 7 ms 10.153.156.1
3 8 ms 7 ms 8 ms winn-core-2a-ae7-1196.network.virginmedia.net [6
2.253.123.93]
4 9 ms 8 ms 9 ms brnt-bb-1c-ae2-0.network.virginmedia.net [62.253
.96.169]
5 * 44 ms 13 ms brhm-bb-1c-ae8-0.network.virginmedia.net [62.253
.174.126]
6 39 ms 38 ms 39 ms brhm-core-2a-ae0-0.network.virginmedia.net [62.2
53.174.74]
7 39 ms 36 ms 34 ms cove-cmts-12-ge130.network.virginmedia.net

Trace complete.

Spo that's one for VM to answer.

[craigj2k12]

Only affecting a handful of users, more likely to be a more localised issue than a national routing problem

[img]Download Failed (1)[/img]





[img]Download Failed (1)[/img]