Student pricing is available for eligible university email holders. View plans

NextSprints
NextSprints Icon NextSprints Logo
Product Design

Master the art of designing products

Product Improvement

Identify scope for excellence

Product Success Metrics

Learn how to define success of product

Product Root Cause Analysis

Ace root cause problem solving

Product Trade-Off

Navigate trade-offs decisions like a pro

All Questions

Explore all questions

Meta (Facebook) PM Interview Course

Practice Meta-focused PM cases

Amazon PM Interview Course

Practice Amazon-focused PM cases

Apple PM Interview Course

Practice Apple-focused PM cases

Google PM Interview Course

Practice Google-focused PM cases

Microsoft PM Interview Course

Practice Microsoft-focused PM cases

All Courses

Explore all courses

1:1 PM Coaching

Practice in a one-to-one session

Resume Review

Narrate impactful stories via resume

Guides Pricing
nextsprints logo

Not a member?

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement.

nextsprints logo

Register to continue.

Login with Google Login with LinkedIn

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement .

Company focus

Xandr

What caused the sudden 30% decrease in bid requests processed by Xandr's Prebid Server yesterday?

Prepared by NextSprints

15 mins
Report an error
Problem Solving Technical Knowledge Data Analysis Advertising Technology Programmatic Advertising Real-Time Bidding Data Analysis Root Cause Analysis System Performance Ad Tech Troubleshooting
Product Management Root Cause Analysis Question: Investigating sudden decrease in Xandr's Prebid Server bid requests

Introduction

The sudden 30% decrease in bid requests processed by Xandr's Prebid Server yesterday is a critical issue that demands immediate attention. This analysis will systematically identify, validate, and address the root cause while considering both short-term and long-term implications for our ad tech ecosystem.

I'll approach this problem by first clarifying key details, ruling out external factors, and then diving deep into our product mechanics, metrics, and potential internal causes. My goal is to pinpoint the root cause and develop a comprehensive plan to resolve the issue and prevent future occurrences.

Framework overview

This analysis follows a structured approach covering issue identification, hypothesis generation, validation, and solution development.

Step 1

Clarifying Questions (3 minutes)

  • Looking at the timing, I'm thinking this could be related to a recent deployment. Has there been any significant code push or configuration change in the last 48 hours?

Why it matters: Recent changes often correlate with sudden performance shifts. Expected answer: Yes, there was a deployment yesterday morning. Impact on approach: If confirmed, I'd focus on analyzing the changes in that deployment.

  • Considering the scale of the decrease, I'm wondering about the geographic distribution. Is this 30% decrease uniform across all regions, or are some areas more affected than others?

Why it matters: Helps identify if it's a global issue or localized to specific infrastructure. Expected answer: The decrease is more pronounced in North America and Europe. Impact on approach: I'd prioritize investigating region-specific factors if the impact is uneven.

  • Given the nature of Prebid Server, I'm curious about the demand-side impact. Have we seen any corresponding changes in fill rates or CPMs from major DSPs?

Why it matters: Helps determine if the issue is isolated to our system or part of a broader market trend. Expected answer: Fill rates have remained stable, but CPMs have decreased slightly. Impact on approach: If DSP metrics are stable, I'd focus more on internal technical issues.

  • Considering potential data anomalies, I'm wondering about our monitoring systems. Have there been any alerts or unusual patterns in our error logs or latency metrics?

Why it matters: Helps rule out measurement errors and points to potential system failures. Expected answer: There was a spike in timeout errors starting yesterday morning. Impact on approach: I'd prioritize investigating our timeout handling and network performance.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025