🔒 Paid
Partial Regional Dependency Failure
A dependency shared by your US, EU, and APAC regional services is behaving differently by region at the same time: one region's calls are succeeding normally, one is running measurably slower, and one is intermittently failing outright. All three regions serve live customer traffic concurrently, and taking any region off live calls trades that region's full service for a degraded fallback response. Stabilize the platform while accounting for the fact that each region's dependency health is not the same.
- Difficulty
- Staff
- Expected Time
- ~20 min
- Category
- Microservices & Dependencies
Skills
- Diagnosing region-by-region divergence in a shared dependency
- Distinguishing a targeted regional mitigation from a uniform global one
- Recognizing when a global control sacrifices a healthy region unnecessarily
- Weighing fallback availability against live-call correctness per region
System Architecture
- Global API
- US Regional Service
- EU Regional Service
- APAC Regional Service
- Shared Dependency
This is a Pro scenario. Upgrade to Pro to unlock it.
Upgrade to ProBack to Incidents