ChangeIntelIT change radar
Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 254/255 feeds/APIs · 0/410 docs · checked 17:13 UTC Customize Public modeDiscuss ChangeIntel on Discord

503s on GitLab.com

Started today 16:10 UTC, left the provider's feed by today 17:25 UTC: at least 1 h 10 min.

1 h 10 min+ At least, from when ChangeIntel read it
5Updates posted

What it affected

As the provider names it

WebsiteAPIGit OperationsPackage RegistryContainer RegistryGitLab PagesCI/CDCI/CD - Hosted runners on LinuxCI/CD - Hosted runners on WindowsCI/CD - Hosted runners on macOSCI/CD - Hosted runners for GitLab community contributionsCI/CD - Self-managed runnersSAML SSO - GitLab SaaSBackground ProcessingGitLab Customers PortalSupport Servicespackages.gitlab.comversion.gitlab.comforum.gitlab.comdocs.gitlab.comCanaryGitLab DuoGitLab agent server for Kubernetes

What the provider posted

Newest first
  1. today 17:05 UTCMonitoringWe have taken steps to resolve the slowness and 503s on GitLab.com and are monitoring the situation. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
  2. today 16:52 UTCIdentifiedMost services on GitLab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
  3. today 16:40 UTCIdentifiedWe have identified the cause of 503s on GitLab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
  4. today 16:25 UTCInvestigatingWe are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
  5. today 16:10 UTCInvestigatingWe are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details.

Around it

From the sources ChangeIntel reads; a match in time is not a cause

What changed

First observed 16 Oct 2026
  1. 16 Oct 2026 Observed stateOngoing → Ended
  2. 16 Oct 2026 StageIdentified → Monitoring
  3. 16 Oct 2026 SummaryMost services on GitLab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261 → We have taken steps to resolve the slowness and 503s on GitLab.com and are monitoring the situation. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
  4. 16 Oct 2026 SummaryWe have identified the cause of 503s on GitLab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261 → Most services on GitLab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
  5. 16 Oct 2026 StageInvestigating → Identified
  6. 16 Oct 2026 SummaryWe are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261 → We have identified the cause of 503s on GitLab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
  7. 16 Oct 2026 SummaryWe are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details. → We are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261

The most recent 100 field changes are listed. Complete recorded revisions are kept separately.

Cite this recorded revision to keep the same title, summary, facts and links when the page changes.

A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.

Keep track

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Oct 17:13 UTC · 254 of 255 readable · 253 fully read · documentation 0/410 current