Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Gitlab

    Last checked Oct 26, 10:15 PM UTC

    Gitlab status

    AI-powered DevSecOps platform for efficient code delivery and team collaboration.

    Experiencing an issue?

    Gitlab logo

    Is Gitlab down?

    Degraded performance

    Having issues with Gitlab?

    Share your experience to help others stay informed.

    Current statusHealth graphOutage reportsOutage mapSocial signalsStatus historyComponentsIncident historyMaintenanceCommunityReviewsAboutFAQsMonitor serviceSimilar servicesComparison

    Latest activity

    Last 24 hours
    1. Official status checked

      Gitlab is experiencing issues

      Official provider status
      Oct 26, 10:15 PM UTC
    2. Official maintenance active

      Investigating delayed CI job pickup — September 2, 2026 11:54 UTC Identified - We are investigating an incident affecting GitLab.com CI/CD jobs using instance runners. Some jobs may remain pending longer than expected or may not be picked up by a runner, which can delay pipelines and deployments. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22845 September 2, 2026 12:43 UTC Resolved - The incident affecting GitLab.com CI/CD jobs using instance runners is now resolved. Some jobs were delayed or remained pending while a manually initiated pg_repack database maintenance operation caused contention on the CI database, affecting runner communication and job pickup. The maintenance operation was terminated and runner metrics recovered. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22845

      Official provider status
      Sep 2, 12:43 PM UTC

    Gitlab outage reports

    0 individual report entries in the last 24 hours. This list includes legacy imports; external source aggregates are shown in the chart.

    30 reports loaded

    Reports older than 24 hours

    Loudoun County, United States

    3 reports

    Major outage

    Sep 24, 11:25 PM – Sep 24, 11:27 PM · about 32 days ago

    View 3 reports
    1. Report 1 · Sep 24, 11:27:19 PM

      Major outage

    2. Report 2 · Sep 24, 11:26:57 PM

      Major outage

    3. Report 3 · Sep 24, 11:25:55 PM

      Major outage

    United States

    2 reports

    Major outage

    Sep 24, 11:26 PM – Sep 24, 11:27 PM · about 32 days ago

    View 2 reports
    1. Report 1 · Sep 24, 11:27:19 PM

      Major outage

    2. Report 2 · Sep 24, 11:26:26 PM

      Major outage

    Denver, United States

    3 reports

    Major outage

    Sep 24, 11:25 PM – Sep 24, 11:27 PM · about 32 days ago

    View 3 reports
    1. Report 1 · Sep 24, 11:27:19 PM

      Major outage

    2. Report 2 · Sep 24, 11:26:10 PM

      Major outage

    3. Report 3 · Sep 24, 11:25:29 PM

      Major outage

    Seattle, United States

    3 reports

    Major outage

    Sep 24, 11:25 PM – Sep 24, 11:27 PM · about 32 days ago

    View 3 reports
    1. Report 1 · Sep 24, 11:27:19 PM

      Major outage

    2. Report 2 · Sep 24, 11:26:20 PM

      Major outage

    3. Report 3 · Sep 24, 11:25:33 PM

      Major outage

    Dallas, United States

    1 report

    Degraded performance

    Sep 24, 11:27 PM · about 32 days ago

    New York, United States

    2 reports

    Degraded performance

    Sep 24, 11:26 PM – Sep 24, 11:27 PM · about 32 days ago

    View 2 reports
    1. Report 1 · Sep 24, 11:27:19 PM

      Degraded performance

    2. Report 2 · Sep 24, 11:26:18 PM

      Degraded performance

    Chicago, United States

    2 reports

    Degraded performance

    Sep 24, 11:26 PM – Sep 24, 11:27 PM · about 32 days ago

    View 2 reports
    1. Report 1 · Sep 24, 11:27:19 PM

      Degraded performance

    2. Report 2 · Sep 24, 11:26:21 PM

      Degraded performance

    New York, United States

    3 reports

    Major outage

    Sep 24, 11:25 PM – Sep 24, 11:27 PM · about 32 days ago

    View 3 reports
    1. Report 1 · Sep 24, 11:27:08 PM

      Major outage

    2. Report 2 · Sep 24, 11:26:43 PM

      Major outage

    3. Report 3 · Sep 24, 11:25:53 PM

      Major outage

    United States

    2 reports

    Degraded performance

    Sep 24, 11:25 PM – Sep 24, 11:26 PM · about 32 days ago

    View 2 reports
    1. Report 1 · Sep 24, 11:26:57 PM

      Degraded performance

    2. Report 2 · Sep 24, 11:25:55 PM

      Degraded performance

    +1

    Chicago, United States

    4 reports

    Major outage

    Sep 24, 11:25 PM – Sep 24, 11:26 PM · about 32 days ago

    View 4 reports
    1. Report 1 · Sep 24, 11:26:56 PM

      Major outage

    2. Report 2 · Sep 24, 11:26:31 PM

      Major outage

    3. Report 3 · Sep 24, 11:25:56 PM

      Major outage

    4. Report 4 · Sep 24, 11:25:31 PM

      Major outage

    Denver, United States

    1 report

    Degraded performance

    Sep 24, 11:26 PM · about 32 days ago

    Seattle, United States

    2 reports

    Degraded performance

    Sep 24, 11:25 PM – Sep 24, 11:26 PM · about 32 days ago

    View 2 reports
    1. Report 1 · Sep 24, 11:26:51 PM

      Degraded performance

    2. Report 2 · Sep 24, 11:25:49 PM

      Degraded performance

    Loudoun County, United States

    1 report

    Degraded performance

    Sep 24, 11:26 PM · about 32 days ago

    Dallas, United States

    1 report

    Major outage

    Sep 24, 11:26 PM · about 32 days ago

    Similar reports from the same location are grouped in 5-minute windows. Counts reflect the reports shown.

    Gitlab status history

    Official status observations, not measured service uptime.

    Gitlab components

    Component nameStatus
    Gitlab Website - Google Compute Engine statusUp
    Gitlab API - Google Compute Engine statusUp
    Gitlab Git Operations - Google Compute Engine statusUp
    Gitlab Package Registry - Google Compute Engine statusUp
    Gitlab Container Registry - Google Compute Engine statusUp
    GitLab Pages - Google Compute Engine statusUp
    Gitlab CI/CD - Google Compute Engine statusUp
    Gitlab CI/CD - Hosted runners on Linux - Google Compute Engine statusUp
    Gitlab CI/CD - Hosted runners on Windows - Google Compute Engine statusUp
    Gitlab CI/CD - Hosted runners on macOS - Google Compute Engine statusUp

    About Gitlab monitoring on Uptimus

    Uptimus monitors Gitlab through its official status source and normalizes published incidents, maintenance windows and component health into one consistent service status.

    This page currently includes 24 monitored components, 61 indexed incidents, 2 maintenance windows and 36 days of known history.

    Uptimus is an independent monitoring service and is not affiliated with Gitlab. A healthy status does not guarantee that every user, device or region is unaffected.

    How Uptimus monitors Gitlab

    Get notified when Gitlab or one of its monitored components reports a major outage or another critical service disruption. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations. The available history contains 61 indexed incidents, giving each alert context beyond the current status. A recent indexed incident was “General slowness on Gitlab.com”.

    Get notified about degraded performance, partial impact and smaller incidents that do not represent a complete outage. Uptimus currently tracks 24 Gitlab components: Website - Google Compute Engine, API - Google Compute Engine, Git Operations - Google Compute Engine, Package Registry - Google Compute Engine. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.

    Maintenance notifications

    Get notified about Gitlab outages

    Monitor Gitlab with Uptimus and get alerts when its status changes.

    Start monitoring for free

    Gitlab outage map

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    View full map

    Gitlab outage map

    Loading report locations…

    Gitlab incident history

    Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.

    View more history
    Incident nameDurationStartedUTCAcknowledgedSeverity
    Official status·Resolved0mOct 23, 20265:04 PM UTCYesMinor
    Official status·Resolved0mOct 21, 20261:21 AM UTCYesMinor
    Official status·Resolved0mOct 20, 20269:55 AM UTCYesMinor
    Official status·Resolved0mOct 16, 20265:24 PM UTCYesMinor
    Official status·Resolved0mOct 16, 20261:21 PM UTCYesMajor
    Official status·Resolved0mOct 15, 20267:50 PM UTCYesMinor
    Official status·Resolved0mOct 15, 20269:02 AM UTCYesMinor
    Official status·Resolved0mOct 14, 202611:40 PM UTCYesMinor

    Scheduled maintenance

    Planned work published by the official provider.

    1. ✓

      Investigating delayed CI job pickup

      Maintenance

      September 2, 2026 11:54 UTC Identified - We are investigating an incident affecting GitLab.com CI/CD jobs using instance runners. Some jobs may remain pending longer than expected or may not be picked up by a runner, which can delay pipelines and deployments. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22845 September 2, 2026 12:43 UTC Resolved - The incident affecting GitLab.com CI/CD jobs using instance runners is now resolved. Some jobs were delayed or remained pending while a manually initiated pg_repack database maintenance operation caused contention on the CI database, affecting runner communication and job pickup. The maintenance operation was terminated and runner metrics recovered. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22845

      Started Sep 2, 2026, 12:43 PM UTC · Ongoing

    2. ✓

      Project and Group Deletions Delayed

      Resolved

      August 17, 2026 07:24 UTC Investigating - We are currently investigating an issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been scheduled for deletion may remain visible past their expected deletion date. August 17, 2026 08:18 UTC Investigating - We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 August 17, 2026 08:56 UTC Investigating - We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 August 17, 2026 09:16 UTC Investigating - We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 August 17, 2026 09:37 UTC Investigating - We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 August 17, 2026 09:58 UTC Investigating - We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 August 17, 2026 10:22 UTC Investigating - We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 August 17, 2026 10:44 UTC Investigating - We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 August 17, 2026 11:02 UTC Investigating - We are still investigating the issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Ones that have been scheduled for deletion may remain visible past their expected deletion date. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 August 17, 2026 11:20 UTC Identified - We've identified a fix for the issue affecting project and group deletions on GitLab.com. Due to routine DB maintenance there will be a delay for when the fix will land in production. Given the current state of a known fix and the known delay, we will post status updates every hour for this incident. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 August 17, 2026 12:37 UTC Identified - The fix is now in production and we're now working on processing the deletion queue via the deletion workers. The last 4 status updates were missing a "4" infrastructure work item link shared; this has been corrected on the status page. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 August 17, 2026 13:24 UTC Monitoring - We're continuing to monitor the deletion queue being processed via the deletion workers. Delay of deletions and visibility of scheduled/queued deletions would be experienced until the queue is cleared. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714 August 17, 2026 13:56 UTC Resolved - All deletion queues have been processed for projects, we expect the same to continue for group deletions. This incident is moved to resolved. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714

      Started Aug 17, 2026, 01:56 PM UTC · Resolved Aug 17, 2026, 01:56 PM UTC

    Receive alerts when Gitlab publishes planned, scheduled or active maintenance affecting the service. Uptimus has indexed 2 maintenance windows from the available Gitlab history. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.
    Recovery notifications
    Know when Gitlab or an affected component returns to healthy operation after an issue or outage. The current page contains 36 days of known status history, while resolved events remain available for later review. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.
    Status messages
    Uptimus stores the incident headline published by Gitlab and presents it with the normalized service status. The available history contains 61 indexed incidents, giving each alert context beyond the current status. A recent indexed incident was “General slowness on Gitlab.com”.
    Status details
    Incident and maintenance updates are preserved so you can follow investigations, mitigations and recovery progress. A recent official update preserved by Uptimus reads: “October 23, 2026 16:32 UTC Monitoring - We identified and resolved an issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are monitoring the platform to ensure the issue remains resolved. More details here: https://gitlab.com/…”.
    Component status filtering
    Choose all components or only the Gitlab products you use. Official alerts then respect that component selection. Uptimus currently tracks 24 Gitlab components: Website - Google Compute Engine, API - Google Compute Engine, Git Operations - Google Compute Engine, Package Registry - Google Compute Engine. Filtering changes which official alerts are delivered; it does not remove the provider's events from the public history.

    Fair questions, straight answers.

    Be the first to know when Gitlab goes down

    Start monitoring
    Similar services
    Comparison

    Uptimus vs Downdetector for Gitlab

    Downdetector public pages are led by user reports. Uptimus combines community activity with official provider incidents, maintenance windows and component health when the source publishes them.

    Uptimus vs Downdetector for Gitlab
    Comparison criteriaUptimusDowndetector
    Community outage reports for GitlabIncludedIncluded
    Adaptive baseline that separates isolated reports from wider disruptionIncludedIncluded
    24-hour report activity and regional outage viewIncludedIncluded
    One workspace for websites, provider status pages, Steam games and Android apps and gamesIncludedSeparate product
    Email, push and webhook alerts from the same workspaceIncludedSeparate product
    Official incident updates and status timeline for GitlabIncludedUser-report led
    Component health and maintenance windows kept separateIncludedLimited on public pages
    IncludedUser-report led · Limited on public pagesSeparate product

    The official status page for Gitlab reports normal operation. 0 reports were recorded for Gitlab in the last 24 hours. Last official check: Oct 26, 10:15 PM UTC.

    Rate this service

    How would you rate Gitlab over the last month?

    No reviews yet

    (One review per month limit)

    Social signals

    7 posts from X and Reddit.

    70
    Hacker News 50
    Hacker News 50@betterhn50
    X

    GitLab Outage https://t.co/sdgODG2FVE (https://t.co/kpFpN3vxzF)

    32 days ago·View on X
    Jonathan Cecil
    Jonathan Cecil@techwithjoe_io
    X

    GitLab is currently reporting an active outage affecting its services. Updates and status monitoring: https://t.co/AoPD98IDX4

    32 days ago·View on X
    Hacker News 20
    Hacker News 20@betterhn20
    X

    GitLab Outage https://t.co/ea7q1kXBrN (https://t.co/RPuSnUcI5P)

    32 days ago·View on X
    xkhdc
    xkhdc@xkhdc
    X

    @statusisdown gitlab is down

    32 days ago·View on X
    Gnyani !!
    Gnyani !!@gnyani7
    X

    Gitlab has been down with 502s all day, so the arcade is open. Top named score gets a month of Cursor Pro. https://t.co/uB3fRxxcKn https://t.co/d3f71q3rYT

    62 days ago·View on X
    Gnyani !!
    Gnyani !!@gnyani7
    X

    Gitlab has been down with 502s all day, so the arcade is open. Top named score gets a month of Cursor Pro. https://t.co/uB3fRxxcKn https://t.co/s7hb8cRhzJ

    62 days ago·View on X

    More services to monitor

    Discover other popular services and their current status

    Browse all services
    Paramount+Overwatch®WeaveDuo SecurityPipedriveStreamtimeTeamviewerChimeInnovoLingk

    Community Discussion

    Share your thoughts about Gitlab

    A
    @Doctor Chuck·Guest
    Error 503
    about 1 month ago
    @fabien deloye·Guest
    error 503
    3 months ago
    @Symph0ny·Guest
    microslopped & clownflared
    5 months ago
    @Indrit Vaka·Guest
    gitlab web, api is down for some of my projects...
    7 months ago
    @Sorasaki Hina·Guest
    Down
    8 months ago