Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Gitlab

    Last checked 28 oct., 04:19 UTC

    Gitlab status

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

    Experiencing an issue?

    Gitlab logo

    Gitlab est-il en panne?

    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
      28 oct., 04:19 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 · il y a 33 jours

    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 · il y a 33 jours

    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 · il y a 33 jours

    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 · il y a 33 jours

    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 · il y a 33 jours

    New York, United States

    2 reports

    Degraded performance

    24 sept., 23:26 – 24 sept., 23:27 · il y a 33 jours

    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 · il y a 33 jours

    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 · il y a 33 jours

    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 · il y a 33 jours

    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 · il y a 33 jours

    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 · il y a 33 jours

    Seattle, United States

    2 reports

    Degraded performance

    24 sept., 23:25 – 24 sept., 23:26 · il y a 33 jours

    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 · il y a 33 jours

    Dallas, United States

    1 report

    Major outage

    24 sept., 23:26 · il y a 33 jours

    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

    À propos de la surveillance de Gitlab sur Uptimus

    Uptimus surveille Gitlab via sa source officielle et normalise les incidents, maintenances et composants en un état cohérent.

    Cette page comprend actuellement 24 composants surveillés, 61 incidents, 2 maintenances et 36 jours d'historique connu.

    Uptimus est un service indépendant sans affiliation avec Gitlab. Un état normal ne garantit pas que chaque utilisateur, appareil ou région soit épargné.

    Comment Uptimus surveille Gitlab

    Recevez une alerte lorsque Gitlab ou un composant surveillé signale une panne majeure ou une perturbation critique. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées. L’historique disponible contient 61 incidents indexés, donnant à chaque alerte un contexte au-delà de l’état actuel. Un incident récent indexé était « General slowness on Gitlab.com ».

    Recevez des alertes sur les performances dégradées, les impacts partiels et les incidents qui ne constituent pas une panne complète. Uptimus suit actuellement 24 composants Gitlab: Website - Google Compute Engine, API - Google Compute Engine, Git Operations - Google Compute Engine, Package Registry - Google Compute Engine. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées.

    Notifications de maintenance

    Recevez une notification lorsque l’état de Gitlab change

    Notifications par e-mail, push et webhook.

    Commencer la surveillance

    Carte des Pannes

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    Voir la carte complète

    Carte des Pannes

    Loading report locations…

    Signaux sociaux

    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)

    il y a 33 jours·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

    il y a 33 jours·View on X
    Hacker News 20
    Hacker News 20@betterhn20
    X

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

    il y a 33 jours·View on X
    xkhdc
    xkhdc@xkhdc
    X

    @statusisdown gitlab is down

    il y a 33 jours·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

    il y a 63 jours·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

    il y a 63 jours·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 oct. 202617:04 UTCYesMinor
    Official status·Resolved0m21 oct. 202601:21 UTCYesMinor
    Official status·Resolved0m20 oct. 202609:55 UTCYesMinor
    Official status·Resolved0m16 oct. 202617:24 UTCYesMinor
    Official status·Resolved0m16 oct. 202613:21 UTCYesMajor
    Official status·Resolved0m15 oct. 202619:50 UTCYesMinor
    Official status·Resolved0m15 oct. 202609:02 UTCYesMinor
    Official status·Resolved0m14 oct. 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 août 2026, 13:56 UTC · Resolved 17 août 2026, 13:56 UTC

    Recevez une alerte lorsque Gitlab publie une maintenance planifiée, programmée ou active. Uptimus a indexé 2 fenêtres de maintenance dans l’historique Gitlab disponible. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées.
    Notifications de rétablissement
    Soyez informé lorsque Gitlab ou un composant affecté retrouve un fonctionnement normal. La page contient 36 jours d’historique connu et conserve les événements résolus pour consultation. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées.
    Messages d’état
    Uptimus conserve le titre de l’incident publié par Gitlab et l’affiche avec l’état normalisé. L’historique disponible contient 61 incidents indexés, donnant à chaque alerte un contexte au-delà de l’état actuel. Un incident récent indexé était « General slowness on Gitlab.com ».
    Détails de l’état
    Les mises à jour des incidents et maintenances sont conservées pour suivre l’enquête, les mesures et le rétablissement. Une mise à jour officielle récente conservée par Uptimus indique : « 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/… ».
    Filtrage des composants
    Choisissez tous les composants ou uniquement les produits Gitlab utilisés. Les alertes officielles respectent cette sélection. Uptimus suit actuellement 24 composants Gitlab: Website - Google Compute Engine, API - Google Compute Engine, Git Operations - Google Compute Engine, Package Registry - Google Compute Engine. Le filtrage modifie les alertes officielles livrées sans supprimer les événements de l’historique public.

    Questions Fréquemment Posées

    Recevez une notification lorsque l’état de Gitlab change

    Commencer la surveillance
    Similar services
    Comparison

    Uptimus vs Downdetector pour Gitlab

    Les pages publiques de Downdetector s’appuient surtout sur les signalements des utilisateurs. Uptimus les associe aux incidents officiels, maintenances et états des composants lorsque le fournisseur les publie.

    Uptimus vs Downdetector pour Gitlab
    Critères de comparaisonUptimusDowndetector
    Signalements communautaires concernant GitlabInclusInclus
    Référence adaptative distinguant les cas isolés d’une panne étendueInclusInclus
    Activité des signalements sur 24 heures et vue régionaleInclusInclus
    Un espace pour les sites, pages de statut, jeux Steam et apps et jeux AndroidInclusProduit séparé
    Alertes e-mail, push et webhook depuis le même espaceInclusProduit séparé
    Mises à jour officielles et chronologie du statut de GitlabInclusPiloté par les signalements
    État des composants et maintenances affichés séparémentInclusLimité sur les pages publiques
    InclusPiloté par les signalements · Limité sur les pages publiquesProduit séparé

    The official status page for Gitlab reports normal operation. 0 reports were recorded for Gitlab in the last 24 hours. Last official check: 28 oct., 04:19 UTC.

    Évaluez ce service

    Comment évalueriez-vous Gitlab au cours du dernier mois?

    Aucun avis pour le moment

    (Limite d'un avis par mois)

    Plus de services à surveiller

    Découvrez d'autres services populaires et leur état actuel

    Parcourir tous les services
    TeslaCounter-StrikeMindtickleStellrIngenicoTicketleapCall TowerLifesize CloudMezmoWhatsApp

    Discussion Communautaire

    Partagez vos réflexions sur Gitlab

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