Latency Profiles
Response latency adds a configurable delay before Beeceptor returns a response. Use it to simulate a slow or unpredictable API and verify how your application handles delayed responses, timeouts, and retries.
This endpoint-level setting applies to all types of responses, regardless of how they are generated. This includes responses from Mock Rules, an API specification, Routing, and Local Tunneling. Configure the latency once for the endpoint, then override it for individual Mock Rules when needed.
This feature is available with paid plans.
Latency Profiles
Choose a profile based on the response behavior you want to simulate:
| Profile | Behavior |
|---|---|
| None | Adds no latency. |
| Fixed | Delays every response by the same duration. |
| Random Range | Varies the delay between the minimum and maximum values. |
| Log-normal Distribution | Produces mostly fast responses with occasional slower ones, within the configured range. |
| Load Dependent | Simulates latency that changes dynamically based on the current request load (RPS) on the endpoint or mock server. |
Use Random Range when you want response times to vary evenly across a defined range. The chart previews the possible delays.

Use Log-normal Distribution to model an API that usually responds quickly but is occasionally slow. The chart previews the expected response times before you save the profile.

Note: The chart is for visual reference only. Actual response delays in simulation will follow a similar pattern, but may not be precisely identical to the chart previewed.
Configure
- Navigate to Endpoint Settings page.
- Open Runtime Behavior tab, and find Response Latency.
- Select a latency profile and setup boundaries in milliseconds.
- Review the distribution, if available, and click Save.
You must enter numeric values as whole numbers from 0 to 600000 milliseconds (10 minutes). For a log-normal profile, the maximum must be greater than the minimum. The mean and spread must both be greater than zero.
Override in Mock Rule
Each Mock Rule can inherit the endpoint latency or use its own delay:
- Inherit endpoint applies the endpoint's current latency profile.
- Fixed delay overrides the endpoint latency with the delay configured on the Mock Rule.
For weighted responses, each response can independently inherit the endpoint latency or use its own fixed delay.