Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Gitlab

    Last checked 28 paź, 05:07 UTC

    Gitlab status

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

    Experiencing an issue?

    Gitlab logo

    Czy Gitlab nie działa?

    Status unavailable

    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. Status verification pending

      The latest official observation is not fresh enough to confirm current service health.

      Official provider status
      28 paź, 05:07 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
      2 wrz, 12:43 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

    24 wrz, 23:25 – 24 wrz, 23:27 · 33 dni temu

    View 3 reports
    1. Report 1 · 24 wrz, 23:27:19

      Major outage

    2. Report 2 · 24 wrz, 23:26:57

      Major outage

    3. Report 3 · 24 wrz, 23:25:55

      Major outage

    United States

    2 reports

    Major outage

    24 wrz, 23:26 – 24 wrz, 23:27 · 33 dni temu

    View 2 reports
    1. Report 1 · 24 wrz, 23:27:19

      Major outage

    2. Report 2 · 24 wrz, 23:26:26

      Major outage

    Denver, United States

    3 reports

    Major outage

    24 wrz, 23:25 – 24 wrz, 23:27 · 33 dni temu

    View 3 reports
    1. Report 1 · 24 wrz, 23:27:19

      Major outage

    2. Report 2 · 24 wrz, 23:26:10

      Major outage

    3. Report 3 · 24 wrz, 23:25:29

      Major outage

    Seattle, United States

    3 reports

    Major outage

    24 wrz, 23:25 – 24 wrz, 23:27 · 33 dni temu

    View 3 reports
    1. Report 1 · 24 wrz, 23:27:19

      Major outage

    2. Report 2 · 24 wrz, 23:26:20

      Major outage

    3. Report 3 · 24 wrz, 23:25:33

      Major outage

    Dallas, United States

    1 report

    Degraded performance

    24 wrz, 23:27 · 33 dni temu

    New York, United States

    2 reports

    Degraded performance

    24 wrz, 23:26 – 24 wrz, 23:27 · 33 dni temu

    View 2 reports
    1. Report 1 · 24 wrz, 23:27:19

      Degraded performance

    2. Report 2 · 24 wrz, 23:26:18

      Degraded performance

    Chicago, United States

    2 reports

    Degraded performance

    24 wrz, 23:26 – 24 wrz, 23:27 · 33 dni temu

    View 2 reports
    1. Report 1 · 24 wrz, 23:27:19

      Degraded performance

    2. Report 2 · 24 wrz, 23:26:21

      Degraded performance

    New York, United States

    3 reports

    Major outage

    24 wrz, 23:25 – 24 wrz, 23:27 · 33 dni temu

    View 3 reports
    1. Report 1 · 24 wrz, 23:27:08

      Major outage

    2. Report 2 · 24 wrz, 23:26:43

      Major outage

    3. Report 3 · 24 wrz, 23:25:53

      Major outage

    United States

    2 reports

    Degraded performance

    24 wrz, 23:25 – 24 wrz, 23:26 · 33 dni temu

    View 2 reports
    1. Report 1 · 24 wrz, 23:26:57

      Degraded performance

    2. Report 2 · 24 wrz, 23:25:55

      Degraded performance

    +1

    Chicago, United States

    4 reports

    Major outage

    24 wrz, 23:25 – 24 wrz, 23:26 · 33 dni temu

    View 4 reports
    1. Report 1 · 24 wrz, 23:26:56

      Major outage

    2. Report 2 · 24 wrz, 23:26:31

      Major outage

    3. Report 3 · 24 wrz, 23:25:56

      Major outage

    4. Report 4 · 24 wrz, 23:25:31

      Major outage

    Denver, United States

    1 report

    Degraded performance

    24 wrz, 23:26 · 33 dni temu

    Seattle, United States

    2 reports

    Degraded performance

    24 wrz, 23:25 – 24 wrz, 23:26 · 33 dni temu

    View 2 reports
    1. Report 1 · 24 wrz, 23:26:51

      Degraded performance

    2. Report 2 · 24 wrz, 23:25:49

      Degraded performance

    Loudoun County, United States

    1 report

    Degraded performance

    24 wrz, 23:26 · 33 dni temu

    Dallas, United States

    1 report

    Major outage

    24 wrz, 23:26 · 33 dni temu

    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

    O monitorowaniu Gitlab w Uptimus

    Uptimus monitoruje Gitlab przez oficjalne źródło i normalizuje incydenty, konserwacje oraz komponenty do jednego spójnego statusu.

    Strona zawiera obecnie 24 komponentów, 61 incydentów, 2 konserwacji i 36 dni znanej historii.

    Uptimus jest niezależny i nie jest powiązany z Gitlab. Prawidłowy status nie gwarantuje braku problemów u każdego użytkownika, urządzenia lub regionu.

    Jak Uptimus monitoruje Gitlab

    Otrzymuj alerty, gdy Gitlab lub monitorowany komponent zgłasza poważną albo krytyczną awarię. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje. Dostępna historia zawiera 61 incydentów i zapewnia kontekst wykraczający poza bieżący status. Ostatni zarejestrowany incydent to „General slowness on Gitlab.com”.

    Otrzymuj alerty o obniżonej wydajności, częściowym wpływie i mniejszych incydentach. Uptimus monitoruje obecnie 24 komponentów Gitlab: Website - Google Compute Engine, API - Google Compute Engine, Git Operations - Google Compute Engine, Package Registry - Google Compute Engine. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje.

    Powiadomienia o konserwacji

    Otrzymuj powiadomienia o zmianie statusu Gitlab

    Powiadomienia e-mail, push i webhook.

    Rozpocznij monitorowanie

    Mapa awarii Gitlab

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    Zobacz pełną mapę

    Mapa awarii Gitlab

    Loading report locations…

    Sygnały społecznościowe

    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)

    33 dni temu·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

    33 dni temu·View on X
    Hacker News 20
    Hacker News 20@betterhn20
    X

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

    33 dni temu·View on X
    xkhdc
    xkhdc@xkhdc
    X

    @statusisdown gitlab is down

    33 dni temu·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

    63 dni temu·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

    63 dni temu·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·Resolved0m23 paź 202617:04 UTCYesMinor
    Official status·Resolved0m21 paź 202601:21 UTCYesMinor
    Official status·Resolved0m20 paź 202609:55 UTCYesMinor
    Official status·Resolved0m16 paź 202617:24 UTCYesMinor
    Official status·Resolved0m16 paź 202613:21 UTCYesMajor
    Official status·Resolved0m15 paź 202619:50 UTCYesMinor
    Official status·Resolved0m15 paź 202609:02 UTCYesMinor
    Official status·Resolved0m14 paź 202623:40 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 2 wrz 2026, 12:43 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 17 sie 2026, 13:56 UTC · Resolved 17 sie 2026, 13:56 UTC

    Otrzymuj alerty, gdy Gitlab publikuje planowaną, zaplanowaną lub aktywną konserwację. Uptimus zarejestrował 2 okien konserwacji z dostępnej historii Gitlab. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje.
    Powiadomienia o przywróceniu
    Dowiedz się, kiedy Gitlab lub dotknięty komponent wraca do prawidłowego działania. Strona zawiera 36 dni znanej historii; rozwiązane zdarzenia pozostają dostępne do analizy. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje.
    Komunikaty statusu
    Uptimus przechowuje nagłówek incydentu opublikowany przez Gitlab i pokazuje go ze znormalizowanym statusem. Dostępna historia zawiera 61 incydentów i zapewnia kontekst wykraczający poza bieżący status. Ostatni zarejestrowany incydent to „General slowness on Gitlab.com”.
    Szczegóły statusu
    Aktualizacje incydentów i konserwacji są zachowywane, aby śledzić analizę, łagodzenie i przywracanie. Ostatnia oficjalna aktualizacja zachowana przez Uptimus: „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/…”.
    Filtrowanie komponentów
    Wybierz wszystkie komponenty lub tylko używane produkty Gitlab. Oficjalne alerty uwzględniają wybór. Uptimus monitoruje obecnie 24 komponentów Gitlab: Website - Google Compute Engine, API - Google Compute Engine, Git Operations - Google Compute Engine, Package Registry - Google Compute Engine. Filtrowanie zmienia dostarczane oficjalne alerty, ale nie usuwa zdarzeń z publicznej historii.

    Często zadawane pytania

    Otrzymuj powiadomienia o zmianie statusu Gitlab

    Rozpocznij monitorowanie
    Similar services
    Comparison

    Uptimus vs Downdetector dla Gitlab

    Publiczne strony Downdetector opierają się głównie na zgłoszeniach użytkowników. Uptimus łączy je z oficjalnymi incydentami, pracami serwisowymi i stanem komponentów, gdy dostawca je publikuje.

    Uptimus vs Downdetector dla Gitlab
    Kryteria porównaniaUptimusDowndetector
    Zgłoszenia społeczności dotyczące GitlabDostępneDostępne
    Adaptacyjna baza odróżniająca pojedyncze zgłoszenia od większej awariiDostępneDostępne
    Aktywność z 24 godzin i regionalna mapa awariiDostępneDostępne
    Jeden obszar dla stron, dostawców statusu, gier Steam oraz aplikacji i gier AndroidDostępneOddzielny produkt
    Alerty e-mail, push i webhook z tego samego obszaruDostępneOddzielny produkt
    Oficjalne aktualizacje i historia statusu GitlabDostępneOparte na zgłoszeniach
    Stan komponentów i prace serwisowe pokazane osobnoDostępneOgraniczone publicznie
    DostępneOparte na zgłoszeniach · Ograniczone publicznieOddzielny produkt

    The current official status of Gitlab cannot be verified. The latest stored provider observation indicated normal operation. 0 reports were recorded for Gitlab in the last 24 hours. Last official check: 28 paź, 05:07 UTC.

    Więcej usług do monitorowania

    Odkryj inne popularne usługi i ich aktualny stan

    Przeglądaj wszystkie usługi
    TeslaCounter-StrikeMindtickleStellrIngenicoTicketleapCall TowerLifesize CloudMezmoWhatsApp

    Oceń tę usługę

    Jak oceniłbyś Gitlab w ciągu ostatniego miesiąca?

    Brak recenzji

    (Limit jednej recenzji na miesiąc)

    Dyskusja społeczności

    Podziel się swoimi przemyśleniami na temat 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