GitLab: Incident silently edited: 503s on GitLab.com

Silent editNot classified yetChanged 2026-11-04 14:23 UTCstatus.gitlab.com

Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

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

ChangedUpdateinvestigating2026-10-16 16:25 UTC#1

…return but errors still intermittent. More details at: ~~https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261~~

…return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23402

ChangedUpdateidentified2026-10-16 16:40 UTC#2

…we work to resolve the issue. More details: ~~https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261~~

…we work to resolve the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23402

ChangedUpdateidentified2026-10-16 16:52 UTC#3

…are looking to resolve it. More details at: ~~https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261~~

…are looking to resolve it. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23402

ChangedUpdatemonitoring2026-10-16 17:05 UTC#4

…and are monitoring the situation. More details at: ~~https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261~~

…and are monitoring the situation. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23402

ChangedUpdateresolved2026-10-16 17:24 UTC#5

…GitLab Duo are operating normally. More details at: ~~https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261~~

…GitLab Duo are operating normally. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23402

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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

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

Oct 18
Before captured 05:07 UTC
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on Oct 19, 23:18 UTC. Record hash 7a70dec7a158435c…
Download proof

Rewindex captured a newer version after the last checkpoint; the next run (00:41 UTC) commits it.

History of this incident

TodayWednesday, November 4Wed, Nov 4

1 rewrite

Edited
14:23Edited by the vendor
503s on GitLab.comthis change

Friday, October 16

1 incident change

Outage
16:10Critical incident
503s on GitLab.com
GitLab.com experienced critical-impact 503 errors and site slowness from 2026-10-16 16:10 UTC to 2026-10-16 17:24 UTC, lasting 1 h 14 min. Most services recovered before GitLab Duo slowness cleared; GitLab reported full resolution but did not specify the cause or remediation steps.

Cite this

Incident silently edited: 503s on GitLab.com on GitLab’s status page, changed 2026-11-04 14:23 UTC (change 2 of 2).

Title: Incident silently edited: 503s on GitLab.com
Vendor: GitLab
Date: 2026-11-04 14:23 UTC
URL: https://rewindex.com/change/red9485d4930552

All GitLab changes GitLab profile Markdown JSON