Skip to Content
NodesThroughput

Throughput

Understand how throughput works on Conduit and how to handle 429 rate limits.

What is throughput?

“Throughput” is the volume of requests your application can successfully send to Conduit RPC gateways within a period of time. Today limits are enforced primarily in requests per second (RPS).

Current limits

TierThroughput
Unauthenticated100 RPS
Free Plan500 RPS
Pro Plan10,000 RPS

Additional limits:

LimitValue
Max request time35s
Max batch request size5 MB

Method-specific limits

When using the indexed logs backend:

  • eth_getLogs: up to 10,000 log events per request
  • eth_getLogs block range: up to 2,000 blocks per request

Tips for eth_getLogs:

  • Page by block range (e.g., chunks of ≤2,000 blocks) and by topics to keep event counts below limits

  • Prefer stable block tags (e.g., a specific block number) when possible

  • Requesting more than 10,000 logs fails with HTTP 400 (error code -32005). Example response:

    { "jsonrpc": "2.0", "error": { "code": -32005, "message": "logs count limit exceeded (10000) consider refine/narrow down your query" }, "id": 0 }

Handling 429 (rate limited)

If you receive HTTP 429:

  • Back off and retry with exponential backoff and jitter; honor Retry-After if present
  • Reduce concurrency; queue or rate limit at the client
  • Use batch requests to reduce overhead (stay under 5 MB)
  • Prefer WebSocket subscriptions for high-frequency event use cases
  • For large log scans, paginate ranges rather than one wide query

Best practices

  • Understand method cost: some methods are heavier than others. See Compute Units
  • Batch sensibly: group similar calls into a single batch where appropriate
  • Cache read results and pin to specific block numbers when possible to avoid repeated work
  • Use separate API keys per environment and service to isolate traffic. See Get an API key and Access Control & Settings

Increasing limits

Upgrade your plan or contact us for higher limits:

  • See Pricing & Costs
  • Pro and Enterprise plans support significantly higher sustained throughput

We are migrating to CU/s based rate limiting. When enabled for your org, throughput will be enforced as compute units per second. Learn how CUs are measured in Compute Units.

Last updated on