Jito Rate Limits

Reference doc — last updated April 2026

Default Rate Limits (No Auth Required)

Protocol	Default Limit	Auth Required
JSON-RPC	1 RPS per IP per region	No
gRPC	~5 RPS	No

No authentication is needed at the default level. Rate limits are enforced per IP, per region.

Requesting a Rate Limit Increase

Application Form: https://forms.google.com/8jZmKX1KZA71jXp38

Required Fields

Project Name
Contact email (info@nodius.xyz if no other email is preferred)
Email
Current Block Engine Access Pubkey or UUID for JSON-RPC
Requested Rate Limit
Justification (tip amounts, landing rates, use case)

Approval Details

Default approval: 10 RPS
Higher limits: Require strong justification — demonstrate meaningful tip volume and landing rates
Timeline: Days to weeks. Not all applications are approved.
Cost: No direct cost for the rate limit increase itself. You still pay tips (minimum 1,000 lamports per bundle/transaction).

Authentication

Once approved, authenticate requests using the HTTP header:

x-jito-auth: <YOUR_UUID>

This applies to JSON-RPC endpoints. gRPC uses the Block Engine access pubkey.

Workaround: Multi-Region Distribution

Jito operates endpoints across multiple regions. Since rate limits are per-IP per-region, distributing requests across regions effectively multiplies your throughput:

5 regional endpoints × 1 RPS default = 5 RPS aggregate (no auth needed)
Combine with an approved rate limit increase for even higher throughput

Alternatives to Direct Jito Access

Provider	Product	Notes
QuickNode	Lil' JIT	Jito bundle submission via QuickNode infrastructure
Helius	Helius Sender	Managed transaction sending with Jito integration

These abstract away direct Jito rate limit management.

Resources

Jito Discord: https://discord.gg/jito
Application Form: https://forms.google.com/8jZmKX1KZA71jXp38