Egg blames Web downtime on single network switch


Egg blames Web downtime on single network switch

After its customers reported difficulties accessing their account details last week, online bank Egg blamed the problems on a single network switch

John Sabine

The bank claims an intermittent fault in the switch brought down the entire secure customer service area of its Web site, affecting up to 1.33 million customers.

The problem was initially said to be in back-end hardware and first began to affect customer log-ins last Monday. New sign-ups and the site's home page were unaffected.

Egg claimed to have implemented a fix by Thursday evening, but customer access problems were still being reported over the weekend and the site remained slow on Monday. Egg blamed this on "unprecedented demand".

It took Egg until the end of last week to post a statement on its site, apologising "unreservedly" to all customers who had experienced problems.

Graham Fisher, IT analyst at Bloor Research, criticised Egg for the delay in addressing the fault. He said he would have expected Egg to solve the problems far more quickly, especially as its business is based online. More importantly, he suspected a security breach may have been at issue and expressed surprise that Egg had taken so long to post a statement on its site.

"Companies that take this approach of not being upfront and honest are only damaging themselves," he said, adding, "Some people will be worried (by this) because privacy and security issues have a high profile at the moment."

Email Alerts

Register now to receive IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

This was first published in January 2001


COMMENTS powered by Disqus  //  Commenting policy