Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Gitlab

    Last checked 28 de out., 04:19 UTC

    Gitlab status

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

    Experiencing an issue?

    Gitlab logo

    Gitlab está fora do ar?

    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 de out., 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 de set., 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 Gwen., 23:25 – 24 Gwen., 23:27 · 33 deiz zo

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

      Major outage

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

      Major outage

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

      Major outage

    United States

    2 reports

    Major outage

    24 Gwen., 23:26 – 24 Gwen., 23:27 · 33 deiz zo

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

      Major outage

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

      Major outage

    Denver, United States

    3 reports

    Major outage

    24 Gwen., 23:25 – 24 Gwen., 23:27 · 33 deiz zo

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

      Major outage

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

      Major outage

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

      Major outage

    Seattle, United States

    3 reports

    Major outage

    24 Gwen., 23:25 – 24 Gwen., 23:27 · 33 deiz zo

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

      Major outage

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

      Major outage

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

      Major outage

    Dallas, United States

    1 report

    Degraded performance

    24 Gwen., 23:27 · 33 deiz zo

    New York, United States

    2 reports

    Degraded performance

    24 Gwen., 23:26 – 24 Gwen., 23:27 · 33 deiz zo

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

      Degraded performance

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

      Degraded performance

    Chicago, United States

    2 reports

    Degraded performance

    24 Gwen., 23:26 – 24 Gwen., 23:27 · 33 deiz zo

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

      Degraded performance

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

      Degraded performance

    New York, United States

    3 reports

    Major outage

    24 Gwen., 23:25 – 24 Gwen., 23:27 · 33 deiz zo

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

      Major outage

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

      Major outage

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

      Major outage

    United States

    2 reports

    Degraded performance

    24 Gwen., 23:25 – 24 Gwen., 23:26 · 33 deiz zo

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

      Degraded performance

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

      Degraded performance

    +1

    Chicago, United States

    4 reports

    Major outage

    24 Gwen., 23:25 – 24 Gwen., 23:26 · 33 deiz zo

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

      Major outage

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

      Major outage

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

      Major outage

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

      Major outage

    Denver, United States

    1 report

    Degraded performance

    24 Gwen., 23:26 · 33 deiz zo

    Seattle, United States

    2 reports

    Degraded performance

    24 Gwen., 23:25 – 24 Gwen., 23:26 · 33 deiz zo

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

      Degraded performance

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

      Degraded performance

    Loudoun County, United States

    1 report

    Degraded performance

    24 Gwen., 23:26 · 33 deiz zo

    Dallas, United States

    1 report

    Major outage

    24 Gwen., 23:26 · 33 deiz zo

    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

    Sobre o monitoramento de Gitlab no Uptimus

    O Uptimus monitora Gitlab pela fonte oficial e normaliza incidentes, manutenções e componentes em um status consistente.

    Esta página inclui atualmente 24 componentes monitorados, 61 incidentes, 2 manutenções e 36 dias de histórico conhecido.

    O Uptimus é um serviço independente e não é afiliado ao Gitlab. Um status saudável não garante que todos os usuários, dispositivos ou regiões estejam sem problemas.

    Como o Uptimus monitora Gitlab

    Receba alertas quando Gitlab ou um componente monitorado informar uma falha grave ou crítica. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas. O histórico disponível contém 61 incidentes indexados e oferece contexto além do status atual. Um incidente recente indexado foi “General slowness on Gitlab.com”.

    Receba alertas sobre desempenho degradado, impacto parcial e incidentes que não representam uma falha completa. O Uptimus monitora atualmente 24 componentes do Gitlab: Website - Google Compute Engine, API - Google Compute Engine, Git Operations - Google Compute Engine, Package Registry - Google Compute Engine. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas.

    Notificações de manutenção

    Receba notificações quando o status de Gitlab mudar

    Notificações por e-mail, push e webhook.

    Iniciar monitoramento

    Mapa de interrupções do Gitlab

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    Ver mapa completo

    Mapa de interrupções do Gitlab

    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·Resolved0m23 de out. de 202617:04 UTCYesMinor
    Official status·Resolved0m21 de out. de 202601:21 UTCYesMinor
    Official status·Resolved0m20 de out. de 202609:55 UTCYesMinor
    Official status·Resolved0m16 de out. de 202617:24 UTCYesMinor
    Official status·Resolved0m16 de out. de 202613:21 UTCYesMajor
    Official status·Resolved0m15 de out. de 202619:50 UTCYesMinor
    Official status·Resolved0m15 de out. de 202609:02 UTCYesMinor
    Official status·Resolved0m14 de out. de 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 Gwen. 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 Eost 2026, 13:56 UTC · Resolved 17 Eost 2026, 13:56 UTC

    Receba alertas quando Gitlab publicar manutenção planejada, programada ou ativa. O Uptimus indexou 2 janelas de manutenção do histórico disponível do Gitlab. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas.
    Notificações de recuperação
    Saiba quando Gitlab ou um componente afetado voltar ao funcionamento saudável. A página contém 36 dias de histórico conhecido e mantém eventos resolvidos para análise. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas.
    Mensagens de status
    O Uptimus armazena o título do incidente publicado por Gitlab e o mostra com o status normalizado. O histórico disponível contém 61 incidentes indexados e oferece contexto além do status atual. Um incidente recente indexado foi “General slowness on Gitlab.com”.
    Detalhes do status
    As atualizações de incidentes e manutenção são preservadas para acompanhar investigação, mitigação e recuperação. Uma atualização oficial recente preservada pelo Uptimus diz: “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/…”.
    Filtro de componentes
    Escolha todos os componentes ou apenas os produtos Gitlab usados. Os alertas oficiais respeitam essa seleção. O Uptimus monitora atualmente 24 componentes do Gitlab: Website - Google Compute Engine, API - Google Compute Engine, Git Operations - Google Compute Engine, Package Registry - Google Compute Engine. O filtro altera os alertas oficiais entregues, mas não remove eventos do histórico público.

    Perguntas frequentes

    Receba notificações quando o status de Gitlab mudar

    Iniciar monitoramento
    Similar services
    Comparison

    Uptimus vs Downdetector para Gitlab

    As páginas públicas do Downdetector são orientadas por relatos de usuários. O Uptimus combina essa atividade com incidentes oficiais, manutenções e saúde dos componentes quando o provedor publica esses dados.

    Uptimus vs Downdetector para Gitlab
    Critérios de comparaçãoUptimusDowndetector
    Relatos da comunidade sobre GitlabIncluídoIncluído
    Linha de base adaptativa que separa casos isolados de uma interrupção amplaIncluídoIncluído
    Atividade de 24 horas e visualização regional de interrupçõesIncluídoIncluído
    Um espaço para sites, provedores de status, jogos Steam e apps e jogos AndroidIncluídoProduto separado
    Alertas por e-mail, push e webhook no mesmo espaçoIncluídoProduto separado
    Atualizações oficiais de incidentes e linha do tempo de GitlabIncluídoBaseado em relatos
    Saúde dos componentes e manutenções exibidas separadamenteIncluídoLimitado nas páginas públicas
    IncluídoBaseado em relatos · Limitado nas páginas públicasProduto separado

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

    Avalie este serviço

    Como você avaliaria Gitlab no último mês?

    Ainda não há avaliações

    (Limite de uma revisão por mês)

    Discussão da comunidade

    Compartilhe sua opinião sobre 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

    Sinais sociais

    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 deiz zo·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 deiz zo·View on X
    Hacker News 20
    Hacker News 20@betterhn20
    X

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

    33 deiz zo·View on X
    xkhdc
    xkhdc@xkhdc
    X

    @statusisdown gitlab is down

    33 deiz zo·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 deiz zo·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 deiz zo·View on X

    Mais serviços para monitorar

    Descubra outros serviços populares e seu status atual

    Navegue por todos os serviços
    TeslaCounter-StrikeMindtickleStellrIngenicoTicketleapCall TowerLifesize CloudMezmoWhatsApp