Search

Changes / GitLab / HTTP 500 errors affecting GitLab.com

GitLab: Critical incident: HTTP 500 errors affecting GitLab.com

Summary

Summary pending. The diff below shows exactly what changed.

Major incidentLabel: outage (model (Jev), 100%)Changed Detected Source: status.gitlab.com (opens in new tab)

Incident page: full timeline of updates →

What changed

AddedTitle#1
Before: not present
After: HTTP 500 errors affecting GitLab.com
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-08-27 11:46 UTC
AddedResolved time#5
Before: not present
After: 2026-08-27 15:34 UTC
AddedAffected components#6
Before: not present
After: CI/CD, Website
AddedUpdateinvestigating#7
Before: not present
After: There are elevated HTTP 500 errors affecting users accessing their Pipelines. Our engineers are actively investigating the issue and working to restore normal service.
AddedUpdatemonitoring#8
Before: not present
After: The issue has been identified and resolved. We are monitoring for changes. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22807
AddedUpdateresolved#9
Before: not present
After: Performance remains stable and prevention steps are being implemented. Find more information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22807

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Critical incident: HTTP 500 errors affecting GitLab.com (this change)Major incident

All GitLab changes → · GitLab profile · Markdown · JSON