Blog Post

Amazon Search Outage Offers Two Lessons

Amazon search outage in 2016 offers two object lessons on the digital customer experience: monitor everything and communicate proactively.

Today’s Amazon search outage offers two object lessons on the digital customer experience: monitor everything and communicate proactively. Retailers chasing the industry leader can implement a pair of simple tactics to keep performance issues from turning away buyers.

First, the ultimate goal of End-User Experience Monitoring (EUM) is to find a problem before your customers do and fix it before it impacts their experience. Too many sites rely on basic uptime monitoring—sometimes limited to just a home page—to detect slowdowns and outages. This approach would have completely missed an issue like Amazon’s.

Transaction monitoring on the other hand would have identified the problem right away. In fact, it did. Here is what the outage looked like from Catchpoint’s vantage point:

On June 2, 2016 users from multiple locations faced issues searching for a product on Amazon’s desktop as well as mobile websites. The problem started around 5:15am EDT and lasted for more than 3 hours, until 8:47am EDT.

While the homepage for the Seattle-based ecommerce company was accessible during this time period, there were problems accessing the ‘Categories’ pages and when searching for products. As you can see below, the HTTP status code returned when accessing the page was 503, or service temporarily unavailable.

AMZN Search_3_705

Adding transaction monitoring to your EUM system—the first lesson here—lets you see and troubleshoot interruptions in processes like these immediately.

The second lesson stems from what customers see during outages. During this time period, Amazon users were greeted with the following error messages:

AMZN Search_4_705

AMZN Search_5_705

These error messages reassure users that Amazon knows about the issue, suggest actions that customers can take to continue shopping, and apologize for a potentially frustrating experience. Communicating like this can prevent complaints from flooding the customer service system, keep buyers on the site and transacting, and avoid a flurry of social media criticism.

But transaction monitoring is the key to identifying problems like these so that customer expectations can be managed. Even better, it can help you resolve problems before customers see them in the first place.

News & Trends
Synthetic Monitoring
SLA Management
Workforce Experience
Media and Entertainment

You might also like

Blog post

Incident Review – The Third AWS Outage in December: When it Rains, it Pours

Blog post

Incident Review - Rolling Comcast Outage Disrupts Work from Home for Millions of Users Across the U.S.

Blog post

The Complementary Power of RUM & Internet Synthetic Monitoring

Blog post

Navigating the Serverless Landscape: Lessons from our Tracing Collector API Journey