Click Below to Get the Code

Browse, clone, and build from real-world templates powered by Harper.
Blog
GitHub Logo

How One Retailer Served 2 Million Product Pages During a Major Outage

When a major U.S. retailer's origin system went down, Harper seamlessly stepped in as a resilience layer, serving 2 million product page requests from a pre-warmed cache with ultra-low latency (P95 ~2ms), ensuring most customers never noticed the outage. Designed for high availability, Harper’s architecture—featuring pre-rendered full-page HTML, a fused stack for low latency, and geographically distributed nodes—allowed the retailer to preserve 80% of traffic and revenue during the incident. This event highlights the critical role of robust infrastructure in maintaining user experience and business continuity during backend failures.
Blog

How One Retailer Served 2 Million Product Pages During a Major Outage

By
Aleks Haugom
April 29, 2025
By
Aleks Haugom
April 29, 2025
April 29, 2025
When a major U.S. retailer's origin system went down, Harper seamlessly stepped in as a resilience layer, serving 2 million product page requests from a pre-warmed cache with ultra-low latency (P95 ~2ms), ensuring most customers never noticed the outage. Designed for high availability, Harper’s architecture—featuring pre-rendered full-page HTML, a fused stack for low latency, and geographically distributed nodes—allowed the retailer to preserve 80% of traffic and revenue during the incident. This event highlights the critical role of robust infrastructure in maintaining user experience and business continuity during backend failures.
Aleks Haugom
Senior Manager of GTM & Marketing

When a top U.S. retailer’s origin system went down, 2 million shoppers never noticed.

Their product pages kept loading. Revenue kept flowing. And the engineering team could breathe a little easier.

Why? Harper was quietly running in the background, acting as a resilience layer built to handle exactly this kind of chaos.

In the video below, I sit down with Daniel Abbott, Technical Account Manager at Harper, to break down exactly how the system responded in real-time, how it was architected to handle failure gracefully, and what lessons your team can take away to prepare for the next outage you can’t afford to have.

What Happened: The Quick Version

  • A major U.S. retailer experienced a critical outage at their origin layer.
  • Harper instantly took over product page delivery with 40 million pre-rendered pages in cache.
  • Over the span of one hour, Harper served 2 million requests at a P95 latency of approximately 2 milliseconds.
  • The result: 80% of traffic was preserved during the downtime, and most customers never knew there was an issue.

Why Harper Was Built for This

Full-Page HTML, Pre-Warmed and Ready: The retailer preloads critical product pages into Harper via periodic cache warm-ups. Each page is stored as fully rendered HTML, so when the origin is unavailable, Harper serves the exact same experience—no degraded templates, no missing content.

Low Latency by Design: Harper’s fused stack approach means there are no extra network hops between compute, data, and cache. The result is consistently fast page delivery, even under heavy load. During the outage, Harper’s processing latency remained at or below 2 milliseconds for 95% of site visitors.

Distributed, Redundant, and Built for Failover: For this deployment, Harper was running across six geographically distributed locations (2 nodes at each location). Each node holds its own copy of the dataset, enabling local reads and eliminating the need to route across regions. Smart load balancing ensures only the healthiest, fastest nodes handle traffic.

Real Business Impact: This wasn’t just an engineering win. By keeping product pages live, the retailer preserved revenue, avoided customer frustration, and gained time to resolve the underlying issue. That’s the true value of resilience at the infrastructure layer.

Lessons for Engineering Teams

This incident is a clear reminder that the cloud doesn't guarantee resilience. Without proper architecture, origin failures still result in downtime, lost sales, and reputational damage.

Harper can mitigate this risk by eliminating the origin dependency at the moment it matters most. Its fully distributed design, combined with tight data coupling and smart page caching, allows teams to deliver consistent user experiences even when their backend systems are under stress.

Looking to Build Something Similar?

If your team supports a high-traffic retail website—or any application where uptime equals revenue—it's worth asking: how would your system handle a full origin failure?

If the answer isn’t crystal clear, Harper can help.

Book a demo—we’ll walk you through exactly how to implement this level of protection in your environment.

When a top U.S. retailer’s origin system went down, 2 million shoppers never noticed.

Their product pages kept loading. Revenue kept flowing. And the engineering team could breathe a little easier.

Why? Harper was quietly running in the background, acting as a resilience layer built to handle exactly this kind of chaos.

In the video below, I sit down with Daniel Abbott, Technical Account Manager at Harper, to break down exactly how the system responded in real-time, how it was architected to handle failure gracefully, and what lessons your team can take away to prepare for the next outage you can’t afford to have.

What Happened: The Quick Version

  • A major U.S. retailer experienced a critical outage at their origin layer.
  • Harper instantly took over product page delivery with 40 million pre-rendered pages in cache.
  • Over the span of one hour, Harper served 2 million requests at a P95 latency of approximately 2 milliseconds.
  • The result: 80% of traffic was preserved during the downtime, and most customers never knew there was an issue.

Why Harper Was Built for This

Full-Page HTML, Pre-Warmed and Ready: The retailer preloads critical product pages into Harper via periodic cache warm-ups. Each page is stored as fully rendered HTML, so when the origin is unavailable, Harper serves the exact same experience—no degraded templates, no missing content.

Low Latency by Design: Harper’s fused stack approach means there are no extra network hops between compute, data, and cache. The result is consistently fast page delivery, even under heavy load. During the outage, Harper’s processing latency remained at or below 2 milliseconds for 95% of site visitors.

Distributed, Redundant, and Built for Failover: For this deployment, Harper was running across six geographically distributed locations (2 nodes at each location). Each node holds its own copy of the dataset, enabling local reads and eliminating the need to route across regions. Smart load balancing ensures only the healthiest, fastest nodes handle traffic.

Real Business Impact: This wasn’t just an engineering win. By keeping product pages live, the retailer preserved revenue, avoided customer frustration, and gained time to resolve the underlying issue. That’s the true value of resilience at the infrastructure layer.

Lessons for Engineering Teams

This incident is a clear reminder that the cloud doesn't guarantee resilience. Without proper architecture, origin failures still result in downtime, lost sales, and reputational damage.

Harper can mitigate this risk by eliminating the origin dependency at the moment it matters most. Its fully distributed design, combined with tight data coupling and smart page caching, allows teams to deliver consistent user experiences even when their backend systems are under stress.

Looking to Build Something Similar?

If your team supports a high-traffic retail website—or any application where uptime equals revenue—it's worth asking: how would your system handle a full origin failure?

If the answer isn’t crystal clear, Harper can help.

Book a demo—we’ll walk you through exactly how to implement this level of protection in your environment.

When a major U.S. retailer's origin system went down, Harper seamlessly stepped in as a resilience layer, serving 2 million product page requests from a pre-warmed cache with ultra-low latency (P95 ~2ms), ensuring most customers never noticed the outage. Designed for high availability, Harper’s architecture—featuring pre-rendered full-page HTML, a fused stack for low latency, and geographically distributed nodes—allowed the retailer to preserve 80% of traffic and revenue during the incident. This event highlights the critical role of robust infrastructure in maintaining user experience and business continuity during backend failures.

Download

White arrow pointing right
When a major U.S. retailer's origin system went down, Harper seamlessly stepped in as a resilience layer, serving 2 million product page requests from a pre-warmed cache with ultra-low latency (P95 ~2ms), ensuring most customers never noticed the outage. Designed for high availability, Harper’s architecture—featuring pre-rendered full-page HTML, a fused stack for low latency, and geographically distributed nodes—allowed the retailer to preserve 80% of traffic and revenue during the incident. This event highlights the critical role of robust infrastructure in maintaining user experience and business continuity during backend failures.

Download

White arrow pointing right
When a major U.S. retailer's origin system went down, Harper seamlessly stepped in as a resilience layer, serving 2 million product page requests from a pre-warmed cache with ultra-low latency (P95 ~2ms), ensuring most customers never noticed the outage. Designed for high availability, Harper’s architecture—featuring pre-rendered full-page HTML, a fused stack for low latency, and geographically distributed nodes—allowed the retailer to preserve 80% of traffic and revenue during the incident. This event highlights the critical role of robust infrastructure in maintaining user experience and business continuity during backend failures.

Download

White arrow pointing right

Explore Recent Resources

Blog
GitHub Logo

Answer Engine Optimization: How to Get Cited by AI Answers

Answer Engine Optimization (AEO) is the next evolution of SEO. Learn how to prepare your content for Google’s AI Overviews, Perplexity, and other answer engines. From structuring pages to governing bots, discover how to stay visible, earn citations, and capture future traffic streams.
Search Optimization
Blog
Answer Engine Optimization (AEO) is the next evolution of SEO. Learn how to prepare your content for Google’s AI Overviews, Perplexity, and other answer engines. From structuring pages to governing bots, discover how to stay visible, earn citations, and capture future traffic streams.
Colorful geometric illustration of a dog's head in shades of purple, pink and teal.
Martin Spiek
SEO Subject Matter Expert
Blog

Answer Engine Optimization: How to Get Cited by AI Answers

Answer Engine Optimization (AEO) is the next evolution of SEO. Learn how to prepare your content for Google’s AI Overviews, Perplexity, and other answer engines. From structuring pages to governing bots, discover how to stay visible, earn citations, and capture future traffic streams.
Martin Spiek
Sep 2025
Blog

Answer Engine Optimization: How to Get Cited by AI Answers

Answer Engine Optimization (AEO) is the next evolution of SEO. Learn how to prepare your content for Google’s AI Overviews, Perplexity, and other answer engines. From structuring pages to governing bots, discover how to stay visible, earn citations, and capture future traffic streams.
Martin Spiek
Blog

Answer Engine Optimization: How to Get Cited by AI Answers

Answer Engine Optimization (AEO) is the next evolution of SEO. Learn how to prepare your content for Google’s AI Overviews, Perplexity, and other answer engines. From structuring pages to governing bots, discover how to stay visible, earn citations, and capture future traffic streams.
Martin Spiek
Case Study
GitHub Logo

The Impact of Early Hints - Auto Parts

A leading U.S. auto parts retailer used Harper’s Early Hints technology to overcome Core Web Vitals failures, achieving faster load speeds, dramatically improved indexation, and an estimated $8.6M annual revenue uplift. With minimal code changes, the proof-of-concept validated that even small performance gains can unlock significant growth opportunities for large-scale e-commerce businesses.
Early Hints
Case Study
A leading U.S. auto parts retailer used Harper’s Early Hints technology to overcome Core Web Vitals failures, achieving faster load speeds, dramatically improved indexation, and an estimated $8.6M annual revenue uplift. With minimal code changes, the proof-of-concept validated that even small performance gains can unlock significant growth opportunities for large-scale e-commerce businesses.
Colorful geometric illustration of a dog's head resembling folded paper art in shades of teal and pink.
Harper
Case Study

The Impact of Early Hints - Auto Parts

A leading U.S. auto parts retailer used Harper’s Early Hints technology to overcome Core Web Vitals failures, achieving faster load speeds, dramatically improved indexation, and an estimated $8.6M annual revenue uplift. With minimal code changes, the proof-of-concept validated that even small performance gains can unlock significant growth opportunities for large-scale e-commerce businesses.
Harper
Sep 2025
Case Study

The Impact of Early Hints - Auto Parts

A leading U.S. auto parts retailer used Harper’s Early Hints technology to overcome Core Web Vitals failures, achieving faster load speeds, dramatically improved indexation, and an estimated $8.6M annual revenue uplift. With minimal code changes, the proof-of-concept validated that even small performance gains can unlock significant growth opportunities for large-scale e-commerce businesses.
Harper
Case Study

The Impact of Early Hints - Auto Parts

A leading U.S. auto parts retailer used Harper’s Early Hints technology to overcome Core Web Vitals failures, achieving faster load speeds, dramatically improved indexation, and an estimated $8.6M annual revenue uplift. With minimal code changes, the proof-of-concept validated that even small performance gains can unlock significant growth opportunities for large-scale e-commerce businesses.
Harper