GitLab incident
Degraded performance affecting package pulls from registry(packages.gitlab.com)
GitLab experienced a minor incident on July 15, 2026 affecting Package Registry and packages.gitlab.com and 1 more component, lasting 7h 16m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jul 15, 2026, 02:12 PM UTC
We are investigating degraded performance affecting package pulls from our registry. Users may experience slow or failed Omnibus package downloads while we investigate. Currently, the engineering team has identified the cause of the degraded performance and is currently working to resolve the issue. Users may continue to experience slow or failed Omnibus package downloads while mitigation is in progress. Back to current status 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
- identified Jul 15, 2026, 02:12 PM UTC
We are investigating degraded performance affecting package pulls from our registry. Users may experience slow or failed Omnibus package downloads while we investigate. Currently, the engineering team has identified the cause of the degraded performance and is currently working to resolve the issue. Users may continue to experience slow or failed Omnibus package downloads while mitigation is in progress.
- identified Jul 15, 2026, 03:33 PM UTC
We continue to work on resolving the issue with package pulls from our registry. Users may still experience slow or failed Omnibus package downloads. We will share another update as soon as we have more information.
- identified Jul 15, 2026, 03:33 PM UTC
We continue to work on resolving the issue with package pulls from our registry. Users may still experience slow or failed Omnibus package downloads. We will share another update as soon as we have more information.
- identified Jul 15, 2026, 04:21 PM UTC
Work to resolve the package registry issue is ongoing. During this time, some users may continue to experience slow or unsuccessful Omnibus package downloads.
- identified Jul 15, 2026, 04:21 PM UTC
Work to resolve the package registry issue is ongoing. During this time, some users may continue to experience slow or unsuccessful Omnibus package downloads.
- identified Jul 15, 2026, 04:54 PM UTC
Recovery efforts remain in progress for the issue impacting package pulls from our registry. Some Omnibus package downloads may continue to be slow or fail until the issue is resolved.
- identified Jul 15, 2026, 04:54 PM UTC
Recovery efforts remain in progress for the issue impacting package pulls from our registry. Some Omnibus package downloads may continue to be slow or fail until the issue is resolved.
- identified Jul 15, 2026, 05:25 PM UTC
No material updates to report at this time. We are continuing to investigate the current issue and engineers are working to determine remediation steps.
- identified Jul 15, 2026, 05:25 PM UTC
No material updates to report at this time. We are continuing to investigate the current issue and engineers are working to determine remediation steps.
- identified Jul 15, 2026, 06:19 PM UTC
Mitigation efforts are ongoing to address the issue affecting package pulls from our registry. Slow or failed Omnibus package downloads may still occur.
- identified Jul 15, 2026, 06:19 PM UTC
Mitigation efforts are ongoing to address the issue affecting package pulls from our registry. Slow or failed Omnibus package downloads may still occur.
- identified Jul 15, 2026, 06:57 PM UTC
We've identified the root cause of the issue and are continuing to implement mitigation measures. We'll provide additional updates as progress is made.
- identified Jul 15, 2026, 06:57 PM UTC
We've identified the root cause of the issue and are continuing to implement mitigation measures. We'll provide additional updates as progress is made.
- identified Jul 15, 2026, 07:36 PM UTC
We have no material updates at this time. Our team remains focused on mitigation efforts and will continue to share updates as we make progress.
- identified Jul 15, 2026, 07:36 PM UTC
We have no material updates at this time. Our team remains focused on mitigation efforts and will continue to share updates as we make progress.
- identified Jul 15, 2026, 08:12 PM UTC
There are no significant updates to share at this time. Mitigation efforts are still underway, and we will continue to provide updates as they become available.
- identified Jul 15, 2026, 08:12 PM UTC
There are no significant updates to share at this time. Mitigation efforts are still underway, and we will continue to provide updates as they become available.
- identified Jul 15, 2026, 08:44 PM UTC
Mitigation efforts remain in progress. We're continuing to monitor the implementation and will provide another update once additional progress has been made.
- identified Jul 15, 2026, 08:44 PM UTC
Mitigation efforts remain in progress. We're continuing to monitor the implementation and will provide another update once additional progress has been made.
- resolved Jul 15, 2026, 09:29 PM UTC
Mitigation efforts have been successfully completed, and service has returned to normal. This incident has been resolved.