Matchmaker limitations
Review the rate limits and configuration restrictions that apply to the Matchmaker service.
Read time 1 minuteLast updated 2 days ago
Important
Unity Matchmaker will support Multiplay Hosting until the deprecation date of March 31st, 2026. To aid your migration away from Multiplay Hosting, migration examples for alternative hosting providers are available. Matchmaker will continue to work with Relay and Distributed Authority after the Multiplay Hosting deprecation.
Rate limits
The Matchmaker service uses rate limits to help control network traffic by restricting the number of requests received by the API within any given second. The following table shows the rate limit for each Matchmaker service request for Players and Service Accounts:Request type | Player auth rate limit | Service account rate limit |
|---|---|---|
| Create ticket | 1 request per second | 66,000 requests per second |
| Get ticket status | 1 request per second | 660,000 requests per second |
| Delete ticket | 1 request per second | 66,000 requests per second |
| Create backfill ticket | N/A | 1 request per second |
| Update backfill ticket | N/A | 1 request per second |
Matchmaker requests limitations
Ticket creation requests are limited to 25 KB. The matchmaking ticket properties have the following size limitations:Ticket property | Length limit |
|---|---|
| Player ID | 64 characters |
| Number of players | 150 or the maximum number of players in a team |
| Number of custom data properties | 128 |
| Custom Data property name | 64 characters |
| Custom Data string propterty | 200 characters |
| Custom Data array size | 100 items |
Queue and pool limitations
The limit for queues is 10. The limit for pools is 10 pools per queue.Matchmaking configuration
The following table shows the matchmaking configuration limits:Configuration properties | Length Limit |
|---|---|
| Teams | 100 |
| Team rules | 25 |
| Match rules | 25 |
| Relaxations per rule | 25 |