ThreatLoops
← All vendors

Is GitLab down?

OperationalNo problems detected · checked 7m ago

No — GitLab is operational right now.

Operational

GitLab's official status page

GitLab uptime, as reported

Last 30 days
92.71%
Last 90 days
95.01%
Incidents (30d)
9
Incidents (90d)
18

Calculated from status changes we recorded on GitLab's own status page. Scheduled maintenance is not counted as downtime.

Recent status changes

  1. OperationalOperational2d ago
  2. DegradedDegraded Performance2d ago
  3. OperationalOperational5d ago
  4. DegradedDegraded Performance6d ago
  5. OperationalOperational13d ago
  6. DegradedPartial Service Disruption13d ago
  7. OperationalOperational14d ago
  8. DegradedDegraded Performance14d ago

Vulnerabilities affecting GitLab

  • CVE-2026-75871MediumCVSS 8.227d ago

    GitLab has remediated a vulnerability in the GitLab AI Gateway component affecting all versions of the AI Gateway from 18.10 to 19.0.12, 19.1 to 19.1.7, and 19.2 to 19.2.2 that could have allowed an authenticated user with Duo Agent Platform access to redirect outbound model requests to an externally-controlled endpoint via a crafted inline flow configuration that overrides the HTTP Host header, resulting in disclosure of Google Cloud Vertex cloud service credentials and private signing keys.

  • CVE-2026-7487LowCVSS 3.528d ago

    GitLab has remediated an issue in GitLab EE affecting all versions from 13.1 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with reporter-role permissions who authored a merge request could have reset merge request approval rules due to improper authorization checks.

  • CVE-2026-77801LowCVSS 6.528d ago

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.8 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, could have allowed an authenticated user to cause a denial of service affecting background job processing, due to missing object count limits.

  • CVE-2026-3035LowCVSS 5.528d ago

    GitLab has remediated an issue in GitLab EE affecting all versions from 11.3 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with project Maintainer permissions could have accessed the terminal of a protected environment they were not authorized to use due to improper authorization checks.

  • CVE-2026-18252MediumCVSS 7.328d ago

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.9 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with developer-role permissions could have executed arbitrary commands in a CI context, due to the Claude agent processing configuration from a user-controlled source.

Stop checking status pages one at a time

ThreatLoops watches GitLab and the rest of your stack, and pushes outages and exploited vulnerabilities to Slack, Teams or a webhook — one short list a day instead of twenty browser tabs.

Other Developer tools tools

Is Postman down?Is Docker Hub down?Is Tableau Cloud down?Is Vercel down?Is PagerDuty down?Is Supabase down?Is New Relic down?Is GitHub down?

GitLab status questions

Is GitLab down right now?
No — GitLab is operational right now. We last checked 7m ago against GitLab's official status page.
Is it GitLab or is it just me?
If this page says operational and you still can't connect, the problem is usually local — DNS, a proxy, SSO, or a single region. GitLab recorded 9 status events in the last 30 days.
How do I get alerted when GitLab goes down?
Add GitLab to your stack in ThreatLoops and outages are pushed to Slack, Microsoft Teams or a webhook — alongside vulnerabilities affecting the same vendor.