Rate limits
Understand request rate limits to help control your implementation's network traffic.
Read time 1 minuteLast updated a day ago
The Multiplayer Services SDK 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 of the session request types for players and service accounts. Because service accounts are allowed much more control and are likely to be managing multiple lobbies at a time, their rate limits are more relaxed. Service Account rate limiting is on a per IP address basis. The number of requests taken in account will be shared if several game servers are hosted on a same machine or if several machines are behind the same NAT gateway.
Request type | Player limit | Service account rate limit |
|---|---|---|
| Query for lobbies | 1 request per second | 100 requests per second |
| Create sessions | 20 per minute | 2000 per minute |
| Join sessions | 1 request per second | 2000 requests per minute |
| Create or Join sessions | 1 request per second | 2000 requests per minute |
| Quick Join sessions | 1 request per second | 600 requests per minute |
| Get sessions | 1 request per second | 100 requests per second |
| Get joined sessions | 1 request per second | 200 request per minute |
| Get hosted sessions | 1 request per second | 600 requests per minute |
| Delete sessions | 2 requests per second | 200 requests per second |
| Update sessions | 60 requests per minute | 6000 requests per minute |
| Bulk update sessions | N/A (forbidden) | 1 request per second |
| Leave sessions or remove players | 5 requests per second | 500 requests per second |
| Update players | 60 requests per minute | 6000 requests per minute |
| Reconnect to session | 1 request per second | 1000 requests per minute |
| Get migration data information | 1 request per second | 100 requests per second |