GitLab Is Slow as a Turtle

GitLab System Status

SUBSCRIBESUBSCRIBE

Active Incident Updated a few seconds ago

Updated a few seconds ago

This status page is exclusively intended for monitoring GitLab.com and its associated services. If there are any performance or service interruptions, an update will be posted here. If you are experiencing an issue that is not related to an active GitLab.com incident, or if you are encountering service interruptions on GitLab Dedicated, please submit a request via https://support.gitlab.com.

Problems related to git operationsDegraded Performance

Incident Status

Degraded Performance

Components

Website, Git Operations

Locations

Google Compute Engine

August 3, 2026 14:59 UTC INVESTIGATING

Impact is limited to projects on a single Gitaly node. The team is currently focused on relieving pressure from the overloaded Gitaly node to mitigate impact in the affected projects. For more info, see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625

August 3, 2026 14:31 UTC INVESTIGATING

The team is investigating an issue related to a Gitaly node. Customers may experience errors or slowness when performing git operations. For more info see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625

Website Google Compute Engine

Degraded Performance

API Google Compute Engine

Operational

Git Operations Google Compute Engine

Degraded Performance

Package Registry Google Compute Engine

Operational

Container Registry Google Compute Engine

Operational

GitLab Pages Google Compute Engine

Operational

CI/CD Google Compute Engine

Operational

CI/CD - Hosted runners on Linux Google Compute Engine

Operational

CI/CD - Hosted runners on Windows Google Compute Engine

Operational

CI/CD - Hosted runners on macOS Google Compute Engine AWS

Operational

CI/CD - Hosted runners for GitLab community contributions Google Compute Engine

Operational

CI/CD - Self-managed runners Self-Managed Runner Connectivity

Operational

SAML SSO - GitLab SaaS Google Compute Engine

Operational

Background Processing Google Compute Engine

Operational

GitLab Customers Portal Google Compute Engine

Operational

Support Services Zendesk

Operational

packages.gitlab.com AWS

Operational

version.gitlab.com AWS

Operational

forum.gitlab.com Digital Ocean

Operational

docs.gitlab.com Google Compute Engine

Operational

Canary Google Compute Engine

Operational

GitLab Duo Google Compute Engine

Operational

GitLab agent server for Kubernetes Google Compute Engine

Operational

Status History

Subscribe to receive status updates by email

CloseSubscribeManage Subscription

Manage Existing SubscriptionCreate New Subscription

Subscribe to receive status updates by webhook

Each status update will POST a JSON payload to this URL

Email address for managing webhook

CloseSubscribeManage Subscription

Manage Existing SubscriptionCreate New Subscription

Subscribe to receive status updates in Microsoft Teams

Enter your Microsoft Teams webhook. View Instructions

Email address for managing subscription

CloseSubscribeManage Subscription

Manage Existing SubscriptionCreate New Subscription

Subscribe to receive status updates via RSS

RSS Feed

Follow our status updates on Twitter/X

@gitlabstatus

Subscribe to receive status updates in Slack

Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/C03SKGJ1P

Email address

CloseManage Subscription

Manage Existing SubscriptionCreate New Subscription

Subscribe to receive status updates via iCalendar

iCalendar Feed

GitLab Is Slow as a Turtle

Related Articles

(no title)

Scientists reverse brain aging, with a nasal spray

AI has torched the market for junior programmers

Al Vigier: Canada's AI strategy shouldn't include secret Palantir bills

Google will expand age checks on Android worldwide till the end of the year