rewindex

ChangesGitLabIntermittent 500 on GitLab.com

GitLab: Incident silently edited: Intermittent 500 on GitLab.com

Silent editWording only (typesafe/jev-1.13-20260917, 97%)Changed status.gitlab.com (opens in new tab)
Summary

GitLab renamed the incident from “Intermittent 503 on GitLab.com” to “Intermittent 500 on GitLab.com,” changing the HTTP error code identified in the title. The edit provides no additional impact, timing, cause or fix details.

Machine-written from the diff below (Sol; type: incident edit). Check the diff before relying on it.

Incident page: the full timeline of updates

Part of an outage event

Google Cloud europe-west2 outage, Oct 20, 2026 · 19 vendors, 19 incidents

GitLab’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (timing only, posted +1 h vs Google Cloud’s own post)

See the cascade chart and every vendor →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

What changed

Struck in red is what GitLab removed; blue is what they added. Muted text is unchanged context.

ChangedTitle#1
Before: Intermittent 503 on GitLab.com
After: Intermittent 500 on GitLab.com

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

History of this incident

YesterdayTuesday, October 20Tue, Oct 20

1 rewrite, 3 incident changes

All GitLab changesGitLab profileMarkdownJSON