rate_limits_on_git_ssh_operations.md

stage	group	info	description
Create	Source Code	To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments	Configure rate limits on Git SSH operations on your self-managed GitLab instance.

Rate limits on Git SSH operations

DETAILS: Tier: Free, Premium, Ultimate Offering: Self-managed

• Available by default in GitLab 15.8. Feature flag rate_limit_gitlab_shell removed.

GitLab applies rate limits to Git operations that use SSH by user account and project. When the rate limit is exceeded, GitLab rejects further connection requests from that user for the project.

The rate limit applies at the Git command (plumbing) level. Each command has a rate limit of 600 per minute. For example:

• git push has a rate limit of 600 per minute.
• git pull has its own rate limit of 600 per minute.

Because the same commands are shared by git-upload-pack, git pull, and git clone, they share a rate limit.

Configure GitLab Shell operation limit

• Introduced in GitLab 16.2.

Git operations using SSH is enabled by default. Defaults to 600 per user per minute.

1. On the left sidebar, at the bottom, select Admin.
2. Select Settings > Network.
3. Expand Git SSH operations rate limit.
4. Enter a value for Maximum number of Git operations per minute.
   • To disable the rate limit, set it to 0.
5. Select Save changes.