50M Think Broadband Ping Monitor Results (POST YOURS) - Page 225

Kushan · 11-02-2013, 10:51

Looks fine to me.

trikz · 11-02-2013, 11:48

Anyone for a swim?

Kushan · 11-02-2013, 11:50

Also looks fine.

Efour · 11-02-2013, 15:58

Quote:

Originally Posted by Kushan

Just me then! I'll keep an eye on it, it's rock stable now so probably just a simple glitch.

looks fine

alwaysabear · 11-02-2013, 17:10

I went from 4 downstream to 6 and 1 upstream to two earlier today.

blue166 · 11-02-2013, 19:16

Anyone Up for a laugh (I have just created mine).

http://www.thinkbroadband.com/ping/s...d358b7ac1.html

The high utilization is causing me so much grief.

dwarven · 11-02-2013, 21:23

Quote:

Originally Posted by Kushan

Unfortunately, this is where Virgin often lets itself down in a big way. If you can, ring up technical support and ask them directly for information on those F00 numbers. They'll have access to the history and they'll be able to see just how far those tickets go. One thing I would point out, however, is the number for the upstream utilisation is significantly less than the SNR one. SNR issues can take time to fix, but usually no more than a week or two. So if we assume that ticket is relatively recent. The Utilisation ones can take literally years and given the number it is (tickets are assigned sequentially), it has already been open for quite some time.
Virgin has a nasty habbit of just upping the resolution time on those tickets completely arbitrarily so they're never "Behind".

Seems you were right -

Reply on the 27/1/13 :

Quote:

Hi dwarven,

F002308103 has been closed as the SNR has now been raised to an acceptable level and should cause no further issues.

F001996558 is still ongoing. An extra Upstream has been added which has reduced the Upstream Utilisation. The plans are now being put into place to resolve the Downstream utilisation issues.

Reply on 5/2/13 after request for further info :

Quote:

Hi dwarven,

I can see that fault ref: F001996558 has been escalated to our networks department. The estimated fix time on this issue is currently 13/03/2013 ( although this may be subject to change ).

In addition to this fault ref: F002308103 has been escalated for an SNR issue which is also affecting your connection, this is due to be resolved by 06/02/2013.

I'm very sorry for any inconvenience caused by this.

Reply on 8/2/13 after someone else asked about the SNR fix :

Quote:

Hi StumptBloke,

I have checked fault ref: F002308103. I'm afraid works on this issue have been delayed we have a new estimate of 13/02/2013 ( although this may be subject to change ).

I'm very sorry for the delay in resolving this

The dates just keep getting pushed further and further back

Still makes for interesting feedback on their trial Im taking part in

12-02-2013, 00:57

Quote:

Originally Posted by blue166

Anyone Up for a laugh (I have just created mine).

http://www.thinkbroadband.com/ping/s...d358b7ac1.html

The high utilization is causing me so much grief.

That was our situation about six months ago. It's not terminal, although you may feel like it could be. Chin up dude

qasdfdsaq · 12-02-2013, 11:48

Quote:

Originally Posted by Kushan

Also looks fine.

Dunno about you but that looks horrendous to me. Among the worst cases of congestion I've seen this year.

joeron · 12-02-2013, 12:32

Started geting small packet loss, all the time this last week 1 to 4 % and today seems to be geting worse going up to 10%, the high utilisation fix date keeps geting push back it now 06/03/2013, this is in the Bradford area bd17

Could this packet loss im seeing be any thing to do with the work been carryed out or is this a new error?

Sephiroth · 12-02-2013, 12:50

It could be due to upstream noise introduced while work is being carried out.

Qtx · 12-02-2013, 12:55

Quote:

Originally Posted by dwarven

The dates just keep getting pushed further and further back

That is the reason I left virgin. Well the broken broadband was the actual reason, the moving dates which meant the fix date was 12 months away from when the problem started, was the nail in the coffin

---------- Post added at 12:55 ---------- Previous post was at 12:53 ----------

Quote:

Originally Posted by Sephiroth

It could be due to upstream noise introduced while work is being carried out.

If the fix date is a month away, its not likely they are doing work now. So very unlikely.

They have already admitted a problem, maybe its related to the unfixed problem?

Sephiroth · 12-02-2013, 13:05

Quote:

Originally Posted by Qtx

.......

If the fix date is a month away, its not likely they are doing work now. So very unlikely.

They have already admitted a problem, maybe its related to the unfixed problem?

Well, upstream noise anyway.

joeron · 12-02-2013, 13:33

Last time i asked them about the work been carried out was told the "Current plans are to implement an additional upstream, once that is complete, load balancing across all the upstreams"

So ur prolly right with noise on upstream

@ Qtx it is starting to get a pain been going on last 5 months now, tho prio to this problem it all ways been good dated back from the blueyonder days, this is what was keeping me from leaving virgin

Qtx · 12-02-2013, 13:46

Quote:

Originally Posted by joeron

@ Qtx it is starting to get a pain been going on last 5 months now, tho prio to this problem it all ways been good dated back from the blueyonder days, this is what was keeping me from leaving virgin

Never had any issues back in the blueyonder days myself. Noticed steady degradation in service over the last 3 or so years with VM though, to the point where you realise the good old yonder days are gone