🔒 Paid

Cross-Region Latency Spike

Round-trip latency between the US and EU regions has spiked sharply, and both regions otherwise report healthy local metrics — this is specifically a problem with the link between them. Payment authorization must remain strongly consistent across regions: a business requirement, because an authorization decided independently by both regions during this kind of network degradation risks a double charge that cannot be safely undone afterward. No other business constraint requires the rest of the platform's cross-region traffic to stay synchronous. Diagnose what is actually driving customer-facing latency in each region, and decide how to respond without compromising the one operation that cannot afford it.

Difficulty
Staff
Expected Time
~15 min
Category
Distributed Systems

Skills

  • Reasoning about consistency vs. availability vs. latency tradeoffs
  • Identifying which operations genuinely require strong consistency
  • Distinguishing a link-latency problem from a regional-health problem
  • Recognizing when a correctness-critical path must be left alone even under pressure

System Architecture

  • US Region
  • Global Services
  • EU Region

This is a Pro scenario. Upgrade to Pro to unlock it.

Upgrade to ProBack to Incidents