Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Gitlab

    Last checked 28. Okt., 05:07 UTC

    Gitlab status

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

    Experiencing an issue?

    Gitlab logo

    Ist Gitlab down?

    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. Okt., 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. Sept., 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. Sept., 23:25 – 24. Sept., 23:27 · vor 33 Tagen

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

      Major outage

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

      Major outage

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

      Major outage

    United States

    2 reports

    Major outage

    24. Sept., 23:26 – 24. Sept., 23:27 · vor 33 Tagen

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

      Major outage

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

      Major outage

    Denver, United States

    3 reports

    Major outage

    24. Sept., 23:25 – 24. Sept., 23:27 · vor 33 Tagen

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

      Major outage

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

      Major outage

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

      Major outage

    Seattle, United States

    3 reports

    Major outage

    24. Sept., 23:25 – 24. Sept., 23:27 · vor 33 Tagen

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

      Major outage

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

      Major outage

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

      Major outage

    Dallas, United States

    1 report

    Degraded performance

    24. Sept., 23:27 · vor 33 Tagen

    New York, United States

    2 reports

    Degraded performance

    24. Sept., 23:26 – 24. Sept., 23:27 · vor 33 Tagen

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

      Degraded performance

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

      Degraded performance

    Chicago, United States

    2 reports

    Degraded performance

    24. Sept., 23:26 – 24. Sept., 23:27 · vor 33 Tagen

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

      Degraded performance

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

      Degraded performance

    New York, United States

    3 reports

    Major outage

    24. Sept., 23:25 – 24. Sept., 23:27 · vor 33 Tagen

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

      Major outage

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

      Major outage

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

      Major outage

    United States

    2 reports

    Degraded performance

    24. Sept., 23:25 – 24. Sept., 23:26 · vor 33 Tagen

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

      Degraded performance

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

      Degraded performance

    +1

    Chicago, United States

    4 reports

    Major outage

    24. Sept., 23:25 – 24. Sept., 23:26 · vor 33 Tagen

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

      Major outage

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

      Major outage

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

      Major outage

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

      Major outage

    Denver, United States

    1 report

    Degraded performance

    24. Sept., 23:26 · vor 33 Tagen

    Seattle, United States

    2 reports

    Degraded performance

    24. Sept., 23:25 – 24. Sept., 23:26 · vor 33 Tagen

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

      Degraded performance

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

      Degraded performance

    Loudoun County, United States

    1 report

    Degraded performance

    24. Sept., 23:26 · vor 33 Tagen

    Dallas, United States

    1 report

    Major outage

    24. Sept., 23:26 · vor 33 Tagen

    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

    Über die Überwachung von Gitlab auf Uptimus

    Uptimus überwacht Gitlab über die offizielle Statusquelle und normalisiert Vorfälle, Wartungen und Komponenten in einen einheitlichen Status.

    Diese Seite enthält derzeit 24 überwachte Komponenten, 61 Vorfälle, 2 Wartungen und 36 Tage bekannten Verlauf.

    Uptimus ist ein unabhängiger Dienst und nicht mit Gitlab verbunden. Ein gesunder Status garantiert nicht, dass alle Nutzer, Geräte oder Regionen unbeeinträchtigt sind.

    Wie Uptimus Gitlab überwacht

    Erhalte eine Meldung, wenn Gitlab oder eine überwachte Komponente einen schweren Ausfall oder eine kritische Störung meldet. Meldungen können über die im Workspace aktivierten Kanäle zugestellt werden, darunter E-Mail, Push und konfigurierte Integrationen. Der verfügbare Verlauf enthält 61 erfasste Vorfälle und gibt Meldungen Kontext über den aktuellen Status hinaus. Ein kürzlich erfasster Vorfall war „General slowness on Gitlab.com“.

    Erhalte Meldungen zu Leistungseinbußen, teilweisen Auswirkungen und kleineren Vorfällen ohne vollständigen Ausfall. Uptimus überwacht derzeit 24 Gitlab-Komponenten: Website - Google Compute Engine, API - Google Compute Engine, Git Operations - Google Compute Engine, Package Registry - Google Compute Engine. Meldungen können über die im Workspace aktivierten Kanäle zugestellt werden, darunter E-Mail, Push und konfigurierte Integrationen.

    Wartungsbenachrichtigungen

    Benachrichtigung erhalten, wenn sich der Status von Gitlab ändert

    Benachrichtigungen per E-Mail, Push und Webhook.

    Überwachung starten

    Ausfallkarte für Gitlab

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    Vollständige Karte anzeigen

    Ausfallkarte für Gitlab

    Loading report locations…

    Soziale Signale

    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)

    vor 33 Tagen·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

    vor 33 Tagen·View on X
    Hacker News 20
    Hacker News 20@betterhn20
    X

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

    vor 33 Tagen·View on X
    xkhdc
    xkhdc@xkhdc
    X

    @statusisdown gitlab is down

    vor 33 Tagen·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

    vor 63 Tagen·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

    vor 63 Tagen·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. Okt. 202617:04 UTCYesMinor
    Official status·Resolved0m21. Okt. 202601:21 UTCYesMinor
    Official status·Resolved0m20. Okt. 202609:55 UTCYesMinor
    Official status·Resolved0m16. Okt. 202617:24 UTCYesMinor
    Official status·Resolved0m16. Okt. 202613:21 UTCYesMajor
    Official status·Resolved0m15. Okt. 202619:50 UTCYesMinor
    Official status·Resolved0m15. Okt. 202609:02 UTCYesMinor
    Official status·Resolved0m14. Okt. 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. Sept. 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. Aug. 2026, 13:56 UTC · Resolved 17. Aug. 2026, 13:56 UTC

    Erhalte eine Meldung, wenn Gitlab geplante, terminierte oder aktive Wartungen veröffentlicht. Uptimus hat 2 Wartungsfenster aus dem verfügbaren Gitlab-Verlauf erfasst. Meldungen können über die im Workspace aktivierten Kanäle zugestellt werden, darunter E-Mail, Push und konfigurierte Integrationen.
    Wiederherstellungsbenachrichtigungen
    Erfahre, wenn Gitlab oder eine betroffene Komponente nach einer Störung wieder gesund ist. Die Seite enthält 36 Tage bekannten Verlauf; behobene Ereignisse bleiben zur Prüfung verfügbar. Meldungen können über die im Workspace aktivierten Kanäle zugestellt werden, darunter E-Mail, Push und konfigurierte Integrationen.
    Statusmeldungen
    Uptimus speichert die von Gitlab veröffentlichte Überschrift und zeigt sie mit dem normalisierten Status an. Der verfügbare Verlauf enthält 61 erfasste Vorfälle und gibt Meldungen Kontext über den aktuellen Status hinaus. Ein kürzlich erfasster Vorfall war „General slowness on Gitlab.com“.
    Statusdetails
    Aktualisierungen zu Vorfällen und Wartungen bleiben erhalten, damit Untersuchung, Behebung und Wiederherstellung nachvollziehbar sind. Eine von Uptimus gespeicherte offizielle Aktualisierung lautet: „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/…“.
    Komponentenfilter
    Wähle alle Komponenten oder nur die genutzten Gitlab-Produkte. Offizielle Meldungen berücksichtigen diese Auswahl. Uptimus überwacht derzeit 24 Gitlab-Komponenten: Website - Google Compute Engine, API - Google Compute Engine, Git Operations - Google Compute Engine, Package Registry - Google Compute Engine. Der Filter ändert zugestellte offizielle Meldungen, entfernt aber keine Ereignisse aus dem öffentlichen Verlauf.

    Häufig gestellte Fragen

    Benachrichtigung erhalten, wenn sich der Status von Gitlab ändert

    Überwachung starten
    Similar services
    Comparison

    Uptimus vs Downdetector für Gitlab

    Öffentliche Downdetector-Seiten basieren vor allem auf Nutzermeldungen. Uptimus verbindet diese mit offiziellen Vorfällen, Wartungen und Komponentenstatus, sofern der Anbieter sie veröffentlicht.

    Uptimus vs Downdetector für Gitlab
    VergleichskriterienUptimusDowndetector
    Community-Störungsmeldungen zu GitlabEnthaltenEnthalten
    Adaptive Basislinie zur Trennung einzelner Meldungen von größeren StörungenEnthaltenEnthalten
    24-Stunden-Meldeaktivität und regionale StörungskarteEnthaltenEnthalten
    Ein Arbeitsbereich für Websites, Statusanbieter, Steam-Spiele und Android-Apps und -SpieleEnthaltenSeparates Produkt
    E-Mail-, Push- und Webhook-Alarme aus demselben ArbeitsbereichEnthaltenSeparates Produkt
    Offizielle Vorfallmeldungen und Statusverlauf für GitlabEnthaltenMeldungsbasiert
    Komponentenstatus und Wartungsfenster getrennt dargestelltEnthaltenAuf öffentlichen Seiten begrenzt
    EnthaltenMeldungsbasiert · Auf öffentlichen Seiten begrenztSeparates 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. Okt., 05:07 UTC.

    Weitere zu überwachende Dienste

    Entdecken Sie andere beliebte Dienste und ihren aktuellen Status

    Alle Dienste durchsuchen
    TeslaCounter-StrikeMindtickleStellrIngenicoTicketleapCall TowerLifesize CloudMezmoWhatsApp

    Bewerten Sie diesen Dienst

    Wie würden Sie Gitlab im letzten Monat bewerten?

    Noch keine Bewertungen

    (Limit: Eine Bewertung pro Monat)

    Community-Diskussion

    Teilen Sie Ihre Gedanken über 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