NHN’s mishap for 5 hrs. 40mins. of downtime was blamed on network equipment failure and their inability to immediately troubleshoot and dissect the exact cause led to prolonged downtime.

The latest website incident with downtime was found to be with network equipment failure (Foundry Networks manufactured Bigiron MG8 backbone switch). NHN operates dual system that handles both KT IDC and remote location simultaneously. The network failure with switching equipment for KT IDC was not discovered in timely manner that led connection failures to the website.

IBM Korea is currently providing IT outsourcing services to NHN Corp. and reported the initial findings of the failed network switching equipment to the NHN.

However, an affiliate from IBM Korea acknowledged, “The initial assessment of the findings was reported to NHN but final analysis for the root cause has not been accessed yet.”

Foundry Networks regional manager Soo-Hong Jun said, “We knew there was a problem with Foundry Networks’ equipment but there isn’t a conclusive evidence that it was the culprit for the downtime as of yet. With so many different clients using the equipment and especially huge complicated networks environment that NHN operates, it is very difficult for anyone to pin point the root cause.”

Jun also said in unpleasant tone, “in respect to portal’s image, having enormous capacity servers and storage, an incident like this will give them a big blow and by the same token, IBM Korea’s outsourcing service will naturally turn the blame to the equipment manufacture for its defense.”

Nevertheless, since the down incident from the 9th IBM Korea pointed the finger by saying “It’s probable the problem lies with the network equipment” and if we backtrack the situation up till’ now, the initial findings to the location and source was known but the definite cause has not been found as of yet.

When reviewing all the reported facts by the industry analysts, we can point our finger at Foundry’s switch equipment but actual cause is yet to be determined. In addition, the delayed response to the downtime due to its inadequate troubleshooting leaves us few questionable facts.

With so many different systems monitoring in operation why was there a delay in finding the cause? We can only assume that they are in hot waters to find the root cause right now.

According to one trustworthy source “Rather than blaming the cause to the network equipment itself, the real issue here is with the inability to find and response appropriately in timely manner. Therefore the ultimate blame could lie with the mismanaging the system itself”

If that is true, it is probable that the finger pointing will turn to IBM Korea once again. It will be interesting to see the outcome of the downtime incident between the IT outsourcer and the troubled website.