GitLab is currently experiencing a minor incident affecting Website and GitLab agent server for Kubernetes (Google Compute Engine), which began 4h ago. The vendor's full update timeline is below.
Affected components
Update timeline
- investigating Sep 24, 2026, 01:43 PM UTC
We have received reports that some users are unable to access projects and are encountering 500 error messages. Our team is currently investigating the cause.
- investigating Sep 24, 2026, 01:48 PM UTC
We have received reports that some users are unable to access projects and are encountering 500 error messages. Our team is currently investigating the cause. Website Google Compute Engine Partial Service Disruption API Google Compute Engine Operational Git Operations Google Compute Engine Partial Service Disruption 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 Close Subscribe Manage Subscription Manage Existing Subscription Create 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 Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close 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 Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close
- investigating Sep 24, 2026, 01:48 PM UTC
We have received reports that some users are unable to access projects and are encountering 500 error messages. Our team is currently investigating the cause. You can follow developments here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23015 Website Google Compute Engine Partial Service Disruption API Google Compute Engine Operational Git Operations Google Compute Engine Partial Service Disruption 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 Close Subscribe Manage Subscription Manage Existing Subscription Create 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 Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close 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 Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close
- investigating Sep 24, 2026, 02:10 PM UTC
A temporary mitigation has been implemented however the cause of the incident is still being investigated.
- investigating Sep 24, 2026, 02:44 PM UTC
The incident team is continuing to investigate the issue to identify its root cause and implement an appropriate resolution.