Skip to content

rate-limits.mdx

Latest commit

 

History

History
143 lines (104 loc) · 5.53 KB

rate-limits.mdx

File metadata and controls

143 lines (104 loc) · 5.53 KB
title Rate limits
sidebarTitle Rate limits

This page describes API and sandbox rate limits of the E2B platform.

Table of Contents

Here's a limits breakdown table based on the plan:

Plan Hobby Pro Enterprise
Sandbox lifecycle & management API 20,000 / 30s 20,000 / 30s Custom
Sandbox operations 40,000 / 60s per IP 40,000 / 60s per IP Custom
Concurrent sandboxes 20 100 - 1,100* Custom
Sandbox creation rate 1 / sec 5 / sec Custom
Egress connections per sandbox 2,500 2,500 Custom
*Pro plan default is 100 concurrent sandboxes. Higher concurrency of up to 1,100 is available as a separate purchasable add-on.

Sandbox lifecycle and management API

20,000 requests per 30 seconds

This rate limit applies to lifecycle and management operations such as sandbox create, kill, update, list, and other.

Sandbox operations and requests to sandboxes

40,000 requests per 60 seconds

This rate limits applies to operations to/within running sandboxes such as running code, listing files, running commands, etc. This also includes requests made to custom ports in the sandbox.


This limit is enforced globally across all sandbox operations from a single IP address.

Concurrent sandboxes

Number of concurrent sandboxes differs based on the pricing tier.

Hobby tier

Up to 20 concurrent sandboxes

Pro tier

Starts at 100 concurrent sandboxes

Can go up to 1,100 with additional [add-ons available for purchase](https://e2b.dev/dashboard/?tab=billing).

Enterprise tier

Custom limit - 1,100+ concurrent sandboxes

Sandbox creation rate

This limit controls how quickly you can create new sandboxes.

Hobby tier

1 sandbox per second

Pro tier

5 sandboxes per second

Enterprise tier

Custom limit - 5+ sandboxes per second

Egress connections

2,500 connections per sandbox

This limit controls the maximum number of outbound (egress) network connections that can be established from a single sandbox.

Reaching limits

When you reach the limits of your plan, subsequent requests/function calls will be effectively dropped and return the following:

  • the 429 Too Many Requests HTTP status code (when calling API/sandbox ports directly)
  • RateLimitError in the JS/TS SDK
  • RateLimitException in the Python SDK

For example, if you're on the Pro tier (without any concurrency add-ons), you can create up to 100 sandboxes running concurrently. If the 100 sandboxes are still running, requests for creating new sandboxes from the SDKs (Sandbox.create() in JS/TS or Sandbox.create() in Python) will fail and return RateLimitError or RateLimitException respectively. Once the number of running sandboxes drops below 100, or you purchase a concurrency add-on, you’ll be able to create new sandboxes again.

Increasing and avoiding rate limits

You can avoid rate limits by upgrading your plan or contacting our sales team to discuss your specific requirements and we can provide tailored limits to meet your needs at enterprise@e2b.dev.