Log inSign up
GitLab.com Status
9,523 posts
GitLab.com Status profile banner
@gitlabstatus

GitLab.com Status

@gitlabstatus
Follow for updates about the status of GitLab.com.
status.gitlab.com
Joined January 2013
1
Following
31.7K
Followers
RepliesRepliesRepostsRepostsMediaMedia

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
  • @gitlabstatus
    GitLab.com Status
    @gitlabstatus
    Sep 2
    Automated by @gitlab
    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 databa... status.gitlab.com
    Image
    GitLab - Speed with control for agentic software engineering
    From about.gitlab.com
  • @gitlabstatus
    GitLab.com Status
    @gitlabstatus
    Sep 2
    Automated by @gitlab
    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. status.gitlab.com
    Image
    GitLab - Speed with control for agentic software engineering
    From about.gitlab.com
  • @gitlabstatus
    GitLab.com Status
    @gitlabstatus
    Aug 27
    Automated by @gitlab
    Performance remains stable and prevention steps are being implemented. Find more information here: gitlab.com/gitlab-com/gl-… status.gitlab.com
    Image
    gitlab.com
    2026-08-27: patroni-sec CPU saturated (#22807) · Issues · GitLab.com / GitLab Infrastructure Team /...
    patroni-sec CPU saturated (Severity 2) Problem: patroni-sec CPU saturation caused consistent timeouts and elevated HTTP 500 errors on GitLab.com pages. Impact: Customers saw elevated...
  • @gitlabstatus
    GitLab.com Status
    @gitlabstatus
    Aug 27
    Automated by @gitlab
    The issue has been identified and resolved. We are monitoring for changes. More information here: gitlab.com/gitlab-com/gl-… status.gitlab.com
    Image
    gitlab.com
    2026-08-27: patroni-sec CPU saturated (#22807) · Issues · GitLab.com / GitLab Infrastructure Team /...
    patroni-sec CPU saturated (Severity 2) Problem: patroni-sec CPU saturation caused consistent timeouts and elevated HTTP 500 errors on GitLab.com pages. Impact: Customers saw elevated...
  • @gitlabstatus
    GitLab.com Status
    @gitlabstatus
    Aug 27
    Automated by @gitlab
    There are elevated HTTP 500 errors affecting users accessing their Pipelines. Our engineers are actively investigating the issue and working to restore normal service. status.gitlab.com
Advertisement
Advertisement