# Solana gRPC Filter limits ### Stop Optimizing Around Your Provider's Limits Most Yellowstone gRPC providers cap what you can filter, meter what you stream, and charge for what you use. [Shyft](https://shyft.to/) doesn't. Every limit below is set for serious production workloads — MEV bots, data indexers, and high-frequency trading infrastructure — not to push you toward a higher plan.

	Shyft	Other Providers
Bandwidth Metering	Truly unmetered	May or may not be metered
Additional Data Charges (Egress)	Truly unlimited, no metering & no egress charges.	Data charges applied based on egress for some
IP Limits	No IP based limits	Very limited for some
Concurrent Connections	Very generous compared to others	Very limited for some
Transaction Filter Addresses (`accountInclude`)	150k addresses per filter	Very limited for some
Account Filter Addresses (`accountInclude`)	400k addresses per filter	Very limited for some
Filters per Subscribe Request	10 per Subscribe Request	Very limited for some
Subscribe Request Updates	Unlimited	Rate limited for most
Token Program Allowed in `accountInclude`	Allowed	Restricted for most
System Program Allowed in `accountInclude`	Allowed	Restricted for most

### Filter Limits Filtering is where most providers quietly fall short. Shyft sets filter limits that actually work in production — whether you're tracking thousands of wallets, monitoring multiple programs, or running a multi-strategy MEV bot. | Filter Type | Shyft Limits | | --------------------------------------------------- | ----------------------------------------- | | **Transaction Filter Addresses** (`accountInclude`) | 150,000 / filter | | **Account Filter Addresses** (`accountInclude`) | 400,000 / filter | | **Filters per Subscribe Request** | 10 | | **Subscribe Request Update Rate** | Unlimited | | **Concurrent Connections** | 10 (Build), 20 (Grow) and 50 (Accelerate) | | Number of IPs Allowed | Unlimited. No IP based Limits | {% hint style="info" %} Looking for the fastest way to stream solana events into your stack? [Shyft's Yellowstone gRPC service](https://shyft.to/solana-yellowstone-grpc) is the most robust real-time geyser streaming solution on Solana, built for developers who need 100% reliability at scale. {% endhint %} ### Global Infrastructure Shyft's Yellowstone gRPC nodes are deployed across 6 global regions spanning the US, Europe, and Asia — with intelligent failover and highly available cluster pools in every region. The regions include: * New York (NY) * Ashburn (VA) * Amsterdam (AMS) * Frankfurt (FRA) * London (EU) * Singapore (SGP) * Tokyo (Coming Soon)

### What's Always Unlimited — On Every Plan Regardless of which plan you're on, the following are always unlimited: * **Bandwidth** — stream as much data as your application needs * **Data (TBs streamed)** — no quota, no throttling based on volume * **Whitelisted IPs** — add as many server IPs as your infrastructure requires * **Subscribe Request Update Rate** — update your subscriptions as frequently as needed, no rate limiting applied ### Yellowstone gRPC Connection Limits by Plan Your concurrent gRPC connection limit determines how many simultaneous streams you can open at once.

Limit Name	BUILD	GROW	ACCELERATE	DEDICATED NODE
IP Limits	Unlimited	Unlimited	Unlimited	Unlimited
Connections	10	20	50	Unlimited
Cost of Additional Connections	$100 for every 10 connections	$100 for every 10 connections	$100 for every 10 connections	No Cost

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.shyft.to/solana-yellowstone-grpc/solana-grpc-filter-limits.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.