Re: MAJOR NETWORK ISSUE (17 Jan 2012)
 

Well the were more posts on this subject on that forum than the were on this forum, does that not tell you something.

Re: MAJOR NETWORK ISSUE (17 Jan 2012)
 

Yes we do. but it's business sensitive ;)

Re: MAJOR NETWORK ISSUE (17 Jan 2012)
 

Why would it be commercially sensitive? I can accept that you may be under an NDA, but to say what failed is commercially sensitive is just ludicrous. Unless ofc it'd be an admission that VM had failed to pay their LINX peerage fees (joke).

Either way, it still doesn't appear to be properly fixed. Since the outage, I'm having pretty bad lagspikes fairly regularly, like one every 2 hours, lasting about 5 minutes each, rendering services unusable during the lagspike.

Re: MAJOR NETWORK ISSUE (17 Jan 2012)
 

Unless it is posted on the community forum we could not post it on a public forum as it would be classed as commercially sensitive information and could lose us our jobs, not worth it especially as we are awaiting our payout.

Re: MAJOR NETWORK ISSUE (17 Jan 2012)
 

I'm guessing that means it wasn't some sort of switch failure then...is the 'business sensitive' information good or bad news?

Re: MAJOR NETWORK ISSUE (17 Jan 2012)
 

As it was not published we cannot go into any detail.

Re: MAJOR NETWORK ISSUE (17 Jan 2012)
 

I can imagine what's sensitive. The opposition would seize on any information that might lead them to conclude and expose insuffient resilience on VM's part.

As many techies will know, you can algorithmically re-route when there is a node failure; this put pressure on other nodes but is in any case standard everywhere these days.

Plus you can put in physical resilience so that another device takes over with the same IP address in case of failure of a key device. I suspect that didn't happen. If there is a site failure then, of course, this measure is not effective).

The trick is to do proper reliability analysis, identify the potential critical items and design the risk out accordingly. Just so you know, this is one of the day job things I do.

Re: MAJOR NETWORK ISSUE (17 Jan 2012)
 

Ok here

https://www.cableforum.co.uk/images/...2012/01/42.png

Re: MAJOR NETWORK ISSUE (17 Jan 2012)
 

Yes, most sensible departments, including mine, do a combination of all 3 of the above. Although that said, I've seen our whole network taken down more often by human error and critical software bugs than actual hardware failure.

I see no excuse for this level of failure in any major ISP, particularly not one of the largest in the UK. And especially not lingering effects several days on as some people seem to be reporting...

Re: MAJOR NETWORK ISSUE (17 Jan 2012)
 

I wasnt aware we were in a posting count competition.

Re: MAJOR NETWORK ISSUE (17 Jan 2012)
 

It was, I'm talking about the exact details.

Re: MAJOR NETWORK ISSUE (17 Jan 2012)
 

I'm still getting drops, happening all day, unusual because my service is normally excellent, I wonder if they're still having issues of some kind, I don't see many people posting about drops in connection so maybe it's just me!

Re: MAJOR NETWORK ISSUE (17 Jan 2012)
 

I was commenting on a particular issue that had the community forum inundated with posts in every section all about the same issue, hence they added a yellow banner to the first page to little effect as no one actually read it.

Nothing to do with any competition rather a simple statement of fact.

Re: MAJOR NETWORK ISSUE (17 Jan 2012)
 

Give Support a call on 151. There are no ongoing issues AFAIK., although the major outage may have masked some more local issues.

Re: MAJOR NETWORK ISSUE (17 Jan 2012)
 

Like I said when I tried it I couldn't get through. So it doesn't how many posted or what was put on a banner once the site was over whelmed.

The information was here though.