← Back to archive

Tail Latency Might Matter More Than You Think

Tail Latency Might Matter More Than You Think

You’ve probably heard people say, "Yeah, our service usually responds in ~10ms, but sometimes it takes 100ms." That sometimes - that’s what tail latency is. It sounds like a small thing (just 1 in 1000 requests, right?) - but it’s actually a huge deal, especially when you’re working with microservices or any system with lots of service calls.

When you’re doing parallel fan-out, where one service calls many others at once, or serial chains, where one service depends on another and another... the probability that at least one of those calls will be slow shoots way up. In a fan-out with 10 services, the chance of hitting tail latency jumps from 1% to 10%. Add more services, and it snowballs. What was rare becomes normal - and that’s when users start getting frustrated.

Tail latency doesn't just increase the average wait - it increases the variance massively. In one example, it boosted variance by a factor of 25! That’s not a small fluctuation. That’s chaos in your response times.

If you're building or maintaining anything with multiple service calls, don’t ignore tail latency. It’s not a rare glitch. In complex systems, it's practically expected. And it's one of those things that can quietly erode user experience if you're not watching the right metrics.

Tail Latency Might Matter More Than You Think

Originally posted on X

PS: I'm pretty active on 𝕏 if you'd like to follow along

Archive

2026

2025

2024

2018