Container network latency
Simulate unreliable network conditions in containers by adding latency to API calls. Test whether your users are affected when network response times degrade to hundreds or thousands of milliseconds.
Latency
Containers
6 minutes
How this Scenario works
This Scenario adds increasing levels of network latency to your containers, simulating unreliable network conditions that are especially common in microservice architectures—where services make frequent API calls across a growing number of containers.
Why run this Scenario?
- Validate that containerized microservices handle degraded network conditions without cascading failures.
- Test timeout and retry configurations for container-to-container communication.
- Identify services in your container network that are overly sensitive to latency increases.
- Verify that container-level network monitoring detects latency increases and triggers alerts.
What to expect when you run it
When network latency increases significantly within containers, our services continue to respond within acceptable bounds and users experience minimal impact.
More Scenarios to try
Avoid downtime. Use Gremlin to turn failure into resilience.
Gremlin empowers you to proactively root out failure before it causes downtime. See how you can harness chaos to build resilient systems by requesting a demo of Gremlin.
.svg)