Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Gitlab

    Last checked 8. sep., 09.24 UTC

    Gitlab status

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

    Experiencing an issue?

    Er Gitlab nede?

    Major outage

    The official status page for Gitlab reports an outage. An unresolved official incident is listed: “Some catalog agents are not working”. 0 reports were recorded for Gitlab in the last 24 hours. Last official check: 8. sep., 09.24 UTC.

    Source: official status page

    Having issues with Gitlab?

    Share your experience to help others stay informed.

    OverviewActivityHistoryCommunityAbout

    Gitlab service health graph

    Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.

    Gitlab activity

    Loading reports… · Last 24 hours

    Download
    by Uptimus
    ————Now
    • No problems detected
    • Possible problems
    • Problems detected
    • Early warning
    • Official incident

    Small green bars: normal status (illustrative). Taller bars: report activity.

    Waiting for data

    Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.

    View chart data
    15-minute report intervals · UTC
    StartEndReportsStatus

    Latest activity

    Last 24 hours
    1. Official status checked

      Gitlab is experiencing an outage

      Official provider status
      8. sep., 09.24 UTC
    2. Official incident active

      Some catalog agents are not working — September 8, 2026 08:54 UTC Identified - Starting a new chat with an agent from the AI catalog does not work, and the websocket connection is immediately dropped. We are reverting the merge request that introduced the failure. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22880.

      Official provider status
      8. sep., 08.54 UTC
    3. 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
      2. sep., 12.43 UTC
    4. Official maintenance active

      Project and Group Deletions Delayed — 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

      Official provider status
      17. aug., 13.56 UTC

    Gitlab outage reports

    0 outage reports in the last 24 hours.

    30 reports loaded

    Archive · older than 24 hours

    San Diego, United States

    3 reports

    Major outage

    21. aug., 16.01 – 21. aug., 16.02 · for 17 dage siden

    View 3 reports
    1. Report 1 · 21. aug., 16.02.29

      Major outage

    2. Report 2 · 21. aug., 16.02.10

      Major outage

    3. Report 3 · 21. aug., 16.01.08

      Major outage

    Flower Mound, United States

    2 reports

    Degraded performance

    21. aug., 16.01 – 21. aug., 16.02 · for 17 dage siden

    View 2 reports
    1. Report 1 · 21. aug., 16.02.29

      Degraded performance

    2. Report 2 · 21. aug., 16.01.23

      Degraded performance

    Washington, United States

    2 reports

    Degraded performance

    21. aug., 16.01 – 21. aug., 16.02 · for 17 dage siden

    View 2 reports
    1. Report 1 · 21. aug., 16.02.29

      Degraded performance

    2. Report 2 · 21. aug., 16.01.19

      Degraded performance

    +2

    New York, United States

    5 reports

    Major outage

    21. aug., 16.01 – 21. aug., 16.02 · for 17 dage siden

    View 5 reports
    1. Report 1 · 21. aug., 16.02.29

      Major outage

    2. Report 2 · 21. aug., 16.02.17

      Major outage

    3. Report 3 · 21. aug., 16.01.41

      Major outage

    4. Report 4 · 21. aug., 16.01.23

      Major outage

    5. Report 5 · 21. aug., 16.01.11

      Major outage

    San Francisco, United States

    3 reports

    Major outage

    21. aug., 16.01 – 21. aug., 16.02 · for 17 dage siden

    View 3 reports
    1. Report 1 · 21. aug., 16.02.29

      Major outage

    2. Report 2 · 21. aug., 16.02.04

      Major outage

    3. Report 3 · 21. aug., 16.01.02

      Major outage

    West Norriton Township, United States

    2 reports

    Degraded performance

    21. aug., 16.01 – 21. aug., 16.02 · for 17 dage siden

    View 2 reports
    1. Report 1 · 21. aug., 16.02.29

      Degraded performance

    2. Report 2 · 21. aug., 16.01.21

      Degraded performance

    United States

    3 reports

    Major outage

    21. aug., 16.01 – 21. aug., 16.02 · for 17 dage siden

    View 3 reports
    1. Report 1 · 21. aug., 16.02.29

      Major outage

    2. Report 2 · 21. aug., 16.02.08

      Major outage

    3. Report 3 · 21. aug., 16.01.06

      Major outage

    West Norriton Township, United States

    3 reports

    Major outage

    21. aug., 16.00 – 21. aug., 16.02 · for 17 dage siden

    View 3 reports
    1. Report 1 · 21. aug., 16.02.11

      Major outage

    2. Report 2 · 21. aug., 16.01.46

      Major outage

    3. Report 3 · 21. aug., 16.00.56

      Major outage

    Washington, United States

    2 reports

    Major outage

    21. aug., 16.01 – 21. aug., 16.02 · for 17 dage siden

    View 2 reports
    1. Report 1 · 21. aug., 16.02.09

      Major outage

    2. Report 2 · 21. aug., 16.01.44

      Major outage

    New York, United States

    1 report

    Degraded performance

    21. aug., 16.01 · for 17 dage siden

    Flower Mound, United States

    1 report

    Major outage

    21. aug., 16.01 · for 17 dage siden

    San Diego, United States

    1 report

    Degraded performance

    21. aug., 16.01 · for 17 dage siden

    United States

    1 report

    Degraded performance

    21. aug., 16.01 · for 17 dage siden

    San Francisco, United States

    1 report

    Degraded performance

    21. aug., 16.01 · for 17 dage siden

    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.

    Last 60 daysDaily history
    Loading history…
    ——
    • I drift
    • Problemer
    • Nedbrud
    • Vedligeholdelse
    • Ingen data

    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

    Fællesskabsdiskussion

    Del dine tanker om Gitlab

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

    Om overvågning af Gitlab på Uptimus

    Uptimus overvåger Gitlab via den officielle statuskilde og normaliserer hændelser, vedligeholdelse og komponenter til én ensartet status.

    Siden indeholder nu 24 komponenter, 35 hændelser, 2 vedligeholdelser og 30 dages kendt historik.

    Uptimus er en uafhængig tjeneste og er ikke tilknyttet Gitlab. En sund status garanterer ikke, at alle brugere, enheder eller områder er upåvirkede.

    Sådan overvåger Uptimus Gitlab

    Få besked, når Gitlab eller en overvåget komponent melder et større eller kritisk nedbrud. Alarmer kan sendes gennem de kanaler, der er aktiveret i workspace, herunder e-mail, push og konfigurerede integrationer. Den tilgængelige historik indeholder 35 hændelser og giver mere kontekst end den aktuelle status. En nylig registreret hændelse var “Some catalog agents are not working”.

    Få besked om nedsat ydelse, delvis påvirkning og mindre hændelser uden et fuldt nedbrud. Uptimus følger nu 24 Gitlab-komponenter: Website - Google Compute Engine, API - Google Compute Engine, Git Operations - Google Compute Engine, Package Registry - Google Compute Engine. Alarmer kan sendes gennem de kanaler, der er aktiveret i workspace, herunder e-mail, push og konfigurerede integrationer.

    Få besked, når status for Gitlab ændres

    Notifikationer via e-mail, push og webhook.

    Start overvågning

    Driftskort for Gitlab

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    Se fuldt kort

    Driftskort for Gitlab

    Loading report locations…

    Sociale signaler

    3 posts from X and Reddit.

    30
    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

    for 13 dage siden·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

    for 13 dage siden·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/LxdjlVmGWV

    for 13 dage siden·View on X

    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·Unresolved32mOngoing8. sep. 202608.54 UTCYesMinor
    Official status·Resolved0m27. aug. 202615.34 UTCYesMinor
    Official status·Resolved0m27. aug. 202609.35 UTCYesMinor
    Official status·Resolved0m26. aug. 202600.12 UTCYesMinor
    Official status·Resolved0m24. aug. 202622.45 UTCYesMinor
    Official status·Resolved0m21. aug. 202616.25 UTCYesMinor
    Official status·Resolved0m18. aug. 202617.30 UTCYesMinor
    Official status·Resolved0m13. aug. 202617.47 UTCYesMajor

    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 2. sep. 2026, 12.43 UTC · Ongoing

    2. ✓

      Project and Group Deletions Delayed

      Maintenance

      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 17. aug. 2026, 13.56 UTC · Ongoing

    Vedligeholdelsesnotifikationer
    Få besked, når Gitlab offentliggør planlagt, tidsbestemt eller aktiv vedligeholdelse. Uptimus har registreret 2 vedligeholdelsesvinduer fra den tilgængelige Gitlab-historik. Alarmer kan sendes gennem de kanaler, der er aktiveret i workspace, herunder e-mail, push og konfigurerede integrationer.
    Gendannelsesnotifikationer
    Få besked, når Gitlab eller en påvirket komponent igen fungerer normalt. Siden indeholder 30 dages kendt historik; løste hændelser bevares til senere gennemgang. Alarmer kan sendes gennem de kanaler, der er aktiveret i workspace, herunder e-mail, push og konfigurerede integrationer.
    Statusmeddelelser
    Uptimus gemmer hændelsesoverskriften fra Gitlab sammen med den normaliserede status. Den tilgængelige historik indeholder 35 hændelser og giver mere kontekst end den aktuelle status. En nylig registreret hændelse var “Some catalog agents are not working”.
    Statusdetaljer
    Opdateringer om hændelser og vedligeholdelse gemmes, så undersøgelse, afhjælpning og gendannelse kan følges. En nylig officiel opdatering gemt af Uptimus lyder: “September 8, 2026 08:54 UTC Identified - Starting a new chat with an agent from the AI catalog does not work, and the websocket connection is immediately dropped. We are reverting the merge request that introduced the failure. The incident is being tracked…”.
    Komponentfiltrering
    Vælg alle komponenter eller kun de Gitlab-produkter, du bruger. Officielle alarmer følger valget. Uptimus følger nu 24 Gitlab-komponenter: Website - Google Compute Engine, API - Google Compute Engine, Git Operations - Google Compute Engine, Package Registry - Google Compute Engine. Filtrering ændrer leverede officielle alarmer, men fjerner ikke hændelser fra den offentlige historik.

    Ofte Stillede Spørgsmål

    Få besked, når status for Gitlab ændres

    Start overvågning
    Similar services
    Comparison

    Uptimus vs Downdetector for Gitlab

    Downdetectors offentlige sider er primært baseret på brugerrapporter. Uptimus kombinerer dem med officielle hændelser, vedligeholdelse og komponentstatus, når udbyderen offentliggør dataene.

    Uptimus vs Downdetector for Gitlab
    JämförelsekriterierUptimusDowndetector
    Rapporter fra fællesskabet om GitlabInkluderetInkluderet
    Adaptiv basislinje, der skelner enkelte rapporter fra større nedbrudInkluderetInkluderet
    Rapportaktivitet over 24 timer og regionalt nedbrudskortInkluderetInkluderet
    Ét arbejdsområde til websites, statusudbydere, Steam-spil og Android-apps og -spilInkluderetSeparat produkt
    E-mail-, push- og webhookalarmer fra samme arbejdsområdeInkluderetSeparat produkt
    Officielle hændelsesopdateringer og statushistorik for GitlabInkluderetRapportbaseret
    Komponentstatus og vedligeholdelse vises separatInkluderetBegrænset på offentlige sider
    InkluderetRapportbaseret · Begrænset på offentlige siderSeparat produkt

    Flere tjenester at overvåge

    Opdag andre populære tjenester og deres nuværende status

    Gennemse alle tjenester
    easyJetWallpaper EngineGoogleGeometry Jump 3D8x8QuickbooksCheck PointConvertkitYellowdigPlanviewFlexfoneClio Eu

    Rate this service

    How would you rate Gitlab over the last month?

    No reviews yet

    (Én anmeldelse pr. måned begrænsning)