GitLab.com settings

These settings are used on GitLab.com, and are available toGitLab SaaS customers.

See some of these settings on theinstance configuration page for GitLab.com.

Account and limit settings

GitLab.com uses these account limits. If a setting is not listed,the default valueis the same as for GitLab Self-Managed instances:

If you are near or over the repository size limit, you can:

• Reduce your repository size with Git.
• Purchase additional storage.

Backups

To back up an entire project on GitLab.com, you can export it:

• Through the UI.
• Through the API. Youcan also use the API to programmatically upload exports to a storage platform,such as Amazon S3.

With exports, be aware ofwhat is and is not includedin a project export.

To back up the Git repository of a project or wiki, clone it to another computer.All filesuploaded to a wiki after August 22, 2020are included when you clone a repository.

CI/CD

GitLab.com uses theseGitLab CI/CD settings.Any settings or feature limits not listed here use the defaults listed inthe related documentation:

Container registry

To use the GitLab container registry, Docker clients must have access to:

• The registry endpoint and GitLab.com for authorization.
• Google Cloud Storage or Google Cloud Content Delivery Network to download images.

GitLab.com is fronted by Cloudflare.For incoming connections to GitLab.com, you must allow CIDR blocks of Cloudflare(IPv4 andIPv6).

Diff display limits

The settings for the display of diff files cannot be changed on GitLab.com. These limitsapply to both the GitLab UI and API endpoints.

Diff limits can be changedin GitLab Self-Managed.

Email

Email configuration settings, IP addresses, and aliases.

Confirmation settings

GitLab.com uses these email confirmation settings:

• email_confirmation_settingis set toHard.
• unconfirmed_users_delete_after_daysis set to three days.

IP addresses

GitLab.com usesMailgun to send emails from themg.gitlab.com domain,and has its own dedicated IP addresses:

• 23.253.183.236
• 69.72.35.190
• 69.72.44.107
• 159.135.226.146
• 161.38.202.219
• 192.237.158.143
• 192.237.159.239
• 198.61.254.136
• 198.61.254.160
• 209.61.151.122

The IP addresses formg.gitlab.com are subject to change at any time.

Service Desk alias

GitLab.com has a mailbox configured for Service Desk with the email address:contact-project+%{key}@incoming.gitlab.com. To use this mailbox, configure thecustom suffix in projectsettings.

Gitaly RPC concurrency limits on GitLab.com

Per-repository Gitaly RPC concurrency and queuing limits are configured for different types of Gitoperations, likegit clone. When these limits are exceeded, afatal: remote error: GitLab is currently unable to handle this request due to load message isreturned to the client.

A fetch or clone operation is concurrent when the operation starts before a previous operation finishes.

For administrator documentation, seelimit RPC concurrency.

GitLab Pages

Some settings forGitLab Pages differ from thedefaults for GitLab Self-Managed:

The maximum size of your Pages site depends on the maximum artifact size,which is part of theGitLab CI/CD settings.

Rate limits also exist for GitLab Pages.

GitLab.com at scale

In addition to the GitLab Enterprise Edition Linux package install, GitLab.com usesthe following applications and settings to achieve scale. All settings arepublicly available, asKubernetes configurationorChef cookbooks.

Consul

Service discovery:

• gitlab-cookbooks /gitlab_consul · GitLab

Elastic cluster

We use Elasticsearch and Kibana for part of our monitoring solution:

• gitlab-cookbooks /gitlab-elk · GitLab
• gitlab-cookbooks /gitlab_elasticsearch · GitLab

Fluentd

We use Fluentd to unify our GitLab logs:

• gitlab-cookbooks /gitlab_fluentd · GitLab

Grafana

For the visualization of monitoring data:

• gitlab-cookbooks /gitlab-grafana · GitLab

HAProxy

High Performance TCP/HTTP Load Balancer:

• gitlab-cookbooks /gitlab-haproxy · GitLab

Prometheus

Prometheus complete our monitoring stack:

• gitlab-cookbooks /gitlab-prometheus · GitLab

Sentry

Open source error tracking:

• gitlab-cookbooks /gitlab-sentry · GitLab

GitLab-hosted runners

Use GitLab-hosted runners to run your CI/CD jobs on GitLab.com and GitLab Dedicated to seamlesslybuild, test, and deploy your application on different environments.

For more information, seeGitLab-hosted runners.

Hostname list

Add these hostnames when you configure allow-lists in local HTTP(S) proxies,or other web-blocking software that governs end-user computers. Pages onGitLab.com load content from these hostnames:

• gitlab.com
• *.gitlab.com
• *.gitlab-static.net
• *.gitlab.io
• *.gitlab.net

Documentation and GitLab company pages served overdocs.gitlab.com andabout.gitlab.comalso load certain page content directly from common public CDN hostnames.

Container registry hostname list

Add these additional hostnames to your allow-lists if you pull images fromregistry.gitlab.com:

• *.storage.googleapis.com
• *.cdn.registry.gitlab-static.net

Imports

GitLab.com uses settings to limit importing data into GitLab.

Default import sources

Theimport sources (migration tools) that are available to you by default depend onwhich GitLab you use:

• GitLab.com: All available import sources are enabled by default.
• GitLab Self-Managed: No import sources are enabled by default, and must beenabled.

Import placeholder user limits

Imports into GitLab.com limit the number ofplaceholder usersfor each top-level namespace. The limits differ depending on your plan and seat count.For more information, see thetable of placeholder user limits for GitLab.com.

IP range

GitLab.com uses the IP ranges34.74.90.64/28 and34.74.226.0/24 for traffic from its Web/APIfleet. This whole range is solely allocated to GitLab. Connections from webhooks orrepository mirroring come from these IP addresses. You should allow these connections.

• Incoming connections - GitLab.com is fronted by Cloudflare. For incoming connections to GitLab.com,allow CIDR blocks of Cloudflare (IPv4 andIPv6).

• Outgoing connections from CI/CD runners - We don’t provide static IP addresses for outgoingconnections from CI/CD runners. However, these guidelines can help:

  • Linux GPU-enabled and Linux Arm64 runners are deployed into Google Cloud, inus-central1.
  • Other GitLab.com instance runners are deployed into Google Cloud inus-east1.
  • macOS runners are hosted on AWS in theus-east-1 region, with runner managers hosted on Google Cloud.

To configure an IP-based firewall, you must allow bothAWS IP address ranges andGoogle Cloud IP address ranges.

See how to look upIP address ranges or CIDR blocks for GCP.

Maximum number of reviewers and assignees

Merge requests enforce these maximums:

• Maximum assignees: 200
• Maximum reviewers: 200

Merge request limits

GitLab limits each merge request to 1000diff versions.Merge requests that reach this limit cannot be updated further. Instead,close the affected merge request and create a new merge request.

Diff commits limit

GitLab limits each merge request to 1,000,000 (one million) diff commits.Merge requests that reach this limit cannot be updated further. Instead,close the affected merge request and create a new merge request.

Password requirements

GitLab.com sets these requirements for passwords on new accounts and password changes:

• Minimum character length 8 characters.
• Maximum character length 128 characters.
• All characters are accepted. For example,~,!,@,#,$,%,^,&,*,(),[],_,+,=, and-.

Group creation

On GitLab.com,top-level group creation is only allowed through the UI. Only administrators can use the API to create top-level groups.

Project and group deletion

Settings related to the deletion of projects and groups.

Delayed group deletion

Groups are permanently deleted after a 30-day delay.

See how toview and restore groups marked for deletion.

Delayed project deletion

Projects are permanently deleted after a 30-day delay.

See how toview and restore projects marked for deletion.

Dormant project deletion

Dormant project deletion is disabled on GitLab.com.

Package registry limits

Themaximum file sizefor a package uploaded to theGitLab package registryvaries by format:

Puma

GitLab.com uses the default of 60 seconds forPuma request timeouts.

Rate limits on GitLab.com

When a request is rate limited, GitLab responds with a429 statuscode. The client should wait before attempting the request again. Theremay also be informational headers with this response detailed inrate limiting responses. Rate limiting responsesfor the Projects, Groups, and Users APIs do not include informational headers.

The following table describes the rate limits for GitLab.com:

More details are available on the rate limits forprotected paths andraw endpoints.

GitLab can rate-limit requests at several layers. The rate limits listed hereare configured in the application. These limits are the mostrestrictive for each IP address.

Group and project import by uploading export files

To help avoid abuse, GitLab.com uses rate limits:

• Project and group imports.
• Group and project exports that use files.
• Export downloads.

For more information, see:

• Project import/export rate limits.
• Group import/export rate limits.

IP blocks

IP blocks can occur when GitLab.com receives unusual traffic from a singleIP address that the system views as potentially malicious. This can be based onrate limit settings. After the unusual traffic ceases, the IP address isautomatically released depending on the type of block, as described in afollowing section.

If you receive a403 Forbidden error for all requests to GitLab.com,check for any automated processes that may be triggering a block. Forassistance, contactGitLab Supportwith details, such as the affected IP address.

Git and container registry failed authentication ban

GitLab.com responds with HTTP status code403 for 15 minutes when a single IP addresssends 300 failed authentication requests in a 1-minute period.

This applies only to Git requests and container registry (/jwt/auth) requests(combined).

This limit:

• Is reset by requests that authenticate successfully. For example, 299failed authentication requests followed by 1 successful request, followed by299 more failed authentication requests, does not trigger a ban.
• Does not apply to JWT requests authenticated bygitlab-ci-token.

No response headers are provided.

git requests overhttps always send an unauthenticated request first, which for private repositories results in a401 error.git then attempts an authenticated request with a username, password, or access token (if available).These requests might lead to a temporary IP block if too many requests are sent simultaneously.To resolve this issue, useSSH keys to communicate with GitLab.

Non-configurable limits

For more information about non-configurable rate limits used on GitLab.com, seenon-configurable limits

Pagination response headers

For performance reasons, if a query returns more than 10,000 records,GitLab excludes some headers.

Protected paths throttle

If the same IP address sends more than 10 POST requests in a minute to protected paths, GitLab.comreturns a429 HTTP status code.

See the source below for which paths are protected. They include user creation,user confirmation, user sign in, and password reset.

User and IP rate limitsincludes a list of the headers responded to blocked requests.

SeeProtected Paths for more details.

Rate limiting responses

For information on rate limiting responses, see:

• List of headers on responses to blocked requests.
• Customizable response text.

SSH maximum number of connections

GitLab.com defines the maximum number of concurrent, unauthenticated SSHconnections by using theMaxStartups setting.If more than the maximum number of allowed connections occur concurrently, theyare dropped and users getanssh_exchange_identification error.

Visibility settings

Projects, groups, and snippets have theInternal visibilitysettingdisabled on GitLab.com.

Sidekiq

GitLab.com runsSidekiq as anexternal processfor Ruby job scheduling.

The current settings are in theGitLab.com Kubernetes pod configuration.

SSH keys and authentication

Settings related to authentication with SSH. For information about maximum connections,seeSSH maximum number of connections.

Alternative SSH port

GitLab.com can be reached by using adifferent SSH port forgit+ssh.

An example~/.ssh/config is the following:

Host gitlab.com  Hostname altssh.gitlab.com  User git  Port 443  PreferredAuthentications publickey  IdentityFile ~/.ssh/gitlab

SSH host keys fingerprints

Go to the current instance configuration to see the SSH host key fingerprints onGitLab.com.

1. Sign in to GitLab.
2. On the left sidebar, selectHelp () >Help.
3. On the Help page, selectCheck the current instance configuration.

In the instance configuration, you see theSSH host key fingerprints:

The first time you connect to a GitLab.com repository, one of these keys isdisplayed in the output.

SSH key restrictions

GitLab.com uses the defaultSSH key restrictions.

SSHknown_hosts entries

To skip manual fingerprint confirmation in SSH, add the following to.ssh/known_hosts:

gitlab.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAfuCHKVTjquxvt6CM6tdG4SLp1Btn/nOeHHE5UOzRdfgitlab.com ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCsj2bNKTBSpIYDEGk9KxsGh3mySTRgMtXL583qmBpzeQ+jqCMRgBqB98u3z++J1sKlXHWfM9dyhSevkMwSbhoR8XIq/U0tCNyokEi/ueaBMCvbcTHhO7FcwzY92WK4Yt0aGROY5qX2UKSeOvuP4D6TPqKF1onrSzH9bx9XUf2lEdWT/ia1NEKjunUqu1xOB/StKDHMoX4/OKyIzuS0q/T1zOATthvasJFoPrAjkohTyaDUz2LN5JoH839hViyEG82yB+MjcFV5MU3N1l1QL3cVUCh93xSaua1N85qivl+siMkPGbO5xR/En4iEY6K2XPASUEMaieWVNTRCtJ4S8H+9gitlab.com ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBFSMqzJeV9rUzU4kWitGjeR4PWSa29SPqJ1fVkhtj3Hw9xjLVXVYrU9QlYWrOLXBpQ6KWjbjTDTdDkoohFzgbEY=

Webhooks

The following limits apply forwebhooks.

Rate limits

For each top-level namespace, the number of times each minute that a webhook can be called.The limit varies depending on your plan and the number of seats in your subscription.

Security policy limits

The maximum number of policies that you can add to a security policy project. These limits apply to each policy type individually. For example, you can have five merge request approval policies and five scan execution policies in the same security policy project.

Other limits

For GitLab Self-Managed instance limits, see:

• Webhook rate limit.
• Number of webhooks.
• Webhook timeout.
• Parallel Pages deployments.