Search

Companies / GitLab / incidents

GitLab: Degraded performance affecting package pulls from registry(packages.gitlab.com)

Impact: minorStatus: resolvedStarted Resolved (7.3 h)11 updatesSource: status.gitlab.com (opens in new tab)

Affected components: Package Registrypackages.gitlab.com

Timeline of updates

  1. identified

    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.

  2. identified

    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.

  3. identified

    Work to resolve the package registry issue is ongoing. During this time, some users may continue to experience slow or unsuccessful Omnibus package downloads.

  4. identified

    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.

  5. identified

    No material updates to report at this time. We are continuing to investigate the current issue and engineers are working to determine remediation steps.

  6. identified

    Mitigation efforts are ongoing to address the issue affecting package pulls from our registry. Slow or failed Omnibus package downloads may still occur.

  7. identified

    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.

  8. identified

    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.

  9. identified

    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.

  10. identified

    Mitigation efforts remain in progress. We're continuing to monitor the implementation and will provide another update once additional progress has been made.

  11. resolved

    Mitigation efforts have been successfully completed, and service has returned to normal. This incident has been resolved.

Impact, status and times are the vendor’s own, as last archived. View on status.gitlab.com (opens in new tab). GitLab profile · Recent GitLab incidents · Markdown · JSON