Quantcast StorefrontBacktalk » Blog Archive » Walgreens, Lowe’s Battle E-Commerce Trouble On Pearl Harbor Day
advertisement
advertisement

Walgreens, Lowe’s Battle E-Commerce Trouble On Pearl Harbor Day

Written by Fred J. Aun
December 8th, 2009
Like this story? Share it
To share this story with people in your social network, please click on the network icons below.

High traffic on Monday (Dec. 7) was blamed for a day of uptime problems at Walgreens.com. A similar long outage plagued Lowes.com the same day, with the company’s only explanation being a posted note that referred to “maintenance.”

Problems at the Walgreens site began at 1:09 P.M. (New York time), according to site monitoring company AlertBot. The site remained either offline or slow to respond until about 2:16 P.M. But even after it came back to life, the site suffered sporadic similar issues throughout the afternoon.

“During the downtime of slightly more than an hour, Walgreens.com was experiencing some difficulties, including the site taking more than 30 seconds to load and users not being able access the site at all,” said AlertBot Sales and Marketing Manager Justin Noll. “The failures began around 1:00 P.M. with the Web site experiencing a complete blackout. It then came back online, only to load extremely slowly, and then went back offline.” Walgreens Spokesman Jim Cohn attributed the problems to “high customer response to a Walgreens.com promotion.” Cohn said the problem was diagnosed and repaired shortly after 4 P.M., a report backed up by AlertBot’s analysis, which showed solid uptime returned at 4:20 P.M.

Meanwhile, the Lowe’s site began experiencing very long load times at about 3:26 P.M., according to AlertBot and Dotcom-Monitor. This situation lasted for about 20 minutes, after which the homepage became unavailable entirely and the company put up an apology placeholder page that blamed the situation on site work. “To serve you better, we are currently performing maintenance on Lowes.com,” said the page.

Life returned about 50 minutes later, but the resuscitation was short-lived. Lowes.com failed again at about 4:45 P.M. and stayed down, for the most part, until about 6:05 P.M., according to monitors. Another 15-minute outage began about 45 minutes later, followed by 45 minutes of uptime and another crash that was still in effect as of 8 P.M.

A Lowe’s spokesperson said she was unaware of the Web site problems and promised to investigate, but she never returned a call to offer an explanation.

AlertBot’s Noll questioned the logic of Lowe’s on-site claim regarding site maintenance as the cause for the outage. “Scheduled maintenance is typically performed between 12:00 A.M. and 2 A.M. because that is typically the lowest traffic time,” he said. Doing ‘maintenance’ in the middle of the day just doesn’t make sense.”


advertisement

Leave a Reply

Newsletter

Quickly catch-up on the latest in E-Commerce and Retail Tech with our free weekly newsletter, with urgent bulletins as news merits.
advertisement

Most Recent Comments

Kill All The Passwords

This article does mention, but does not give enough attention to, the fact that the attacks discussed are only feasible when the encrypted password file can be copied and subjected to an offline attack. The trick is to have authentication performed on a separate, much more strongly secured host - such as an Active Directory Domain Controller, or a Kerberos server, or a NIS+ server, or even using something as banal as an LDAP-over-SSL authentication dialog. In these environments, the odds of the "password file" being stolen and subjected to an offline attack go to near zero, and only online attacks may be carried out by the attacker. With sensible exponential backoff between failed password attempts, lockout after a modest number of failed attempts on a single account, and pattern detection, that minimum 7 character password is quite secure enough. Passwords aren't dead yet for security purposes, and they will be with us for a very long while to come for practical purposes. The trick is to employ them correctly. Read more...
The possibilities you describe are years away from being implemented at best, so for the moment passwords are an ugly reality. Luckily, password managers can easily manage hundreds of passwords of any length. The only thing a user needs to remember is the master password. It seems like an easier task to educate users on how to use password managers rather than implement complex security technology on a global basis. Read more...