Search

Companies / GitLab / incidents

GitLab: 500 errors when fetching commits on GitLab.com

Impact: criticalStatus: resolvedStarted Resolved (3.6 h)6 updatesSource: status.gitlab.com (opens in new tab)

Affected components: APICI/CDGit OperationsWebsite

Timeline of updates

  1. investigating

    We are investigating an issue causing a subset of requests to GitLab.com receiving 500 errors. We will provide updates as we learn more from our investigation. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

  2. investigating

    We are still investigating the root cause for 500 errors while fetching commits on GitLab.com. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

  3. investigating

    Investigation for the root cause of 500 errors while fetching commits on GitLab.com is still ongoing. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

  4. monitoring

    Our monitoring shows the error rate decreasing towards normal thresholds. We're continuing to monitor the incident. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

  5. monitoring

    The error rate has continued to remain within normal thresholds. We're continuing to monitor the error rate. Further developments can be read here: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

  6. resolved

    The error rate remains within normal thresholds and the issue is now resolved. Further details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729

Rewindex changes for this incident

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