Search

Changes / GitLab / 500 Errors on GitLab.com

GitLab: Critical incident: 500 Errors on GitLab.com

Summary

Summary pending. The diff below shows exactly what changed.

Major incidentLabel: critical (vendor)Changed Detected Source: status.gitlab.com (opens in new tab)

Incident page: full timeline of updates →

What changed

AddedTitle#1
Before: not present
After: 500 Errors on GitLab.com
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-10-07 17:28 UTC
AddedResolved time#5
Before: not present
After: 2025-10-07 18:36 UTC
AddedAffected components#6
Before: not present
After: Website
AddedUpdateinvestigating#7
Before: not present
After: Our team is currently investigating 500 errors on GitLab.com.
AddedUpdateinvestigating#8
Before: not present
After: Our team is still investigating this issue but error rate is currently improving.
AddedUpdateinvestigating#9
Before: not present
After: Our team is still investigating . No material updates at this time.
AddedUpdateinvestigating#10
Before: not present
After: We're seeing that behavior is largely normal at this time. Our team is still investigating the root cause.
AddedUpdateinvestigating#11
Before: not present
After: No material updates at this time.
AddedUpdateresolved#12
Before: not present
After: This issue is now resolved. We experienced unavailability accompanied with 500 errors around 17:15 - 17:30 UTC. This has now returned to normal operations. Our team is continuing to investigate the root cause.

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: 500 Errors on GitLab.com (this change)Major incident

All GitLab changes → · GitLab profile · Markdown · JSON