Connected evidence
Follow a shared identifier, source page or planning group across source records. Dates show chronology; a connection does not establish cause, a shared rollout or applicability to your environment.
GitLab.com: 404s on customers.gitlab.com
Lead record- Why these records are connected
- Records sharing a curated source identity or subject key; inspect each source before treating them as one change.
- Connection key
inc:gitlab:2026-10-20- Public snapshot refreshed
- today 22:31 UTC
- Distinct source events
- 2
- Source records represented
- 2
Current snapshot membership is shown here. Source histories and cited revisions remain on each record. Future source targets are labelled separately from observed changes. Browse connections.
Evidence in chronological order
- Tue 20 Oct · Dated source evidence · Service incident GitLab.com: Intermittent 500 on GitLab.comWebsite · observed for at least 167 min Source: Derived from the linked evidence · source check: not recorded hereYour review: not selected in your watchlist or stack; no review is inferred.
- Tue 20 Oct · Dated source evidence · Service incident GitLab.com: 404s on customers.gitlab.comGitLab Customers Portal · observed for at least 203 min Source: Derived from the linked evidence · source check: not recorded hereYour review: not selected in your watchlist or stack; no review is inferred.The provider called it an outage