GitLab.com Status
@gitlabstatus
Followers
32K
Following
107
Media
19
Statuses
9K
Follow for updates about the status of https://t.co/TrHALqsrdZ.
Joined January 2013
No material updates at this time. We're continuing to monitor the situation. Please see here for more information: https://t.co/8aJ3Ki1eVL
gitlab.com
Jobs stuck in pending state with no corresponding entry in ci_pending_builds table (Severity 2)
0
0
0
Our graphs show no new instances of jobs stuck as pending. We're continuing to monitor the situation. Please see here for more information: https://t.co/8aJ3Ki1eVL
gitlab.com
Jobs stuck in pending state with no corresponding entry in ci_pending_builds table (Severity 2)
0
0
0
No material updates to report at this time. We are continuing to monitor recovery. Please see here for more information: https://t.co/8aJ3Ki1eVL
gitlab.com
Jobs stuck in pending state with no corresponding entry in ci_pending_builds table (Severity 2)
0
0
0
No material updates to report at this time. We are continuing to monitor recovery. Please see here for more information: https://t.co/8aJ3Ki1eVL
gitlab.com
Jobs stuck in pending state with no corresponding entry in ci_pending_builds table (Severity 2)
0
0
0
We have rolled out the feature flag for the fix, and will continue to monitor impact. For details: https://t.co/QXnlFRP6aR.
gitlab.com
Jobs stuck in pending state with no corresponding entry in ci_pending_builds table (Severity 2)
0
0
0
No updates at this time. We are continuing to monitor recovery. Please see here for more information: https://t.co/8aJ3Ki1eVL
gitlab.com
Jobs stuck in pending state with no corresponding entry in ci_pending_builds table (Severity 2)
0
0
0
No further updates at this time. We are continuing to monitor recovery. Please see here for more information: https://t.co/8aJ3Ki1eVL
gitlab.com
Jobs stuck in pending state with no corresponding entry in ci_pending_builds table (Severity 2)
0
0
0
We've merged a mitigation to address the issue and are continuing to monitor recovery. Please see here for more information: https://t.co/8aJ3Ki1eVL
gitlab.com
Jobs stuck in pending state with no corresponding entry in ci_pending_builds table (Severity 2)
0
0
0
Duo functionality has returned to normal and this incident is now resolved. For more details, please see: https://t.co/alvp0NVZba
gitlab.com
GitLab Duo ""I'm sorry, I can't generate a response. Please try again. Error code: A1004"" error (Severity 3)
0
1
0
We’ve identified the issue and merged a revert MR to address it. We’re seeing error rates recover and return to normal. For more details, please see: https://t.co/S36SIkafsA
gitlab.com
GitLab Duo ""I'm sorry, I can't generate a response. Please try again. Error code: A1004"" error (Severity 3)
0
0
0
We have identified a recent change that was causing GitLab Duo to fail to respond for some customers. We are working on a fix.
0
0
0
We're still investigating reports of CI/CD jobs stuck in pending status. Our team continues working to identify the root cause. Details: https://t.co/QXnlFRP6aR
gitlab.com
Jobs stuck in pending state with no corresponding entry in ci_pending_builds table (Severity 2)
0
0
0
No updates at this time. The team is still investigating the root cause, and a potential mitigation effort is underway. Please see here for more information: https://t.co/QXnlFRP6aR
gitlab.com
Jobs stuck in pending state with no corresponding entry in ci_pending_builds table (Severity 2)
0
0
0
The team is still investigating the root cause, and a potential mitigation effort is underway. Please see here for more information: https://t.co/QXnlFRP6aR
gitlab.com
Jobs stuck in pending state with no corresponding entry in ci_pending_builds table (Severity 2)
0
0
0
The team is still investigating the root cause. A potential mitigation effort is underway. Please see here for more information: https://t.co/QXnlFRP6aR
gitlab.com
Jobs stuck in pending state with no corresponding entry in ci_pending_builds table (Severity 2)
0
0
0
We're receiving reports that some CI/CD jobs are stuck in pending status. The cause is currently under investigation. Please see here for more information: https://t.co/QXnlFRP6aR
gitlab.com
Jobs stuck in pending state with no corresponding entry in ci_pending_builds table (Severity 2)
0
0
1
The deployment for the fix for SSH signature endpoint errors has completed. Please see https://t.co/61EE8eL6EP for details.
gitlab.com
500 errors from SSH signature endpoints (Severity 3)
0
0
0
Deployment of the fix is ongoing and we estimate it will be ~4 hours until it is fully available. Details on a workaround for projects with SSH-signed commits in https://t.co/61EE8eL6EP.
gitlab.com
500 errors from SSH signature endpoints (Severity 3)
0
0
0
We are in the process of deploying the fix and are expecting this to take 4+ hours to complete. For full details, see https://t.co/61EE8eL6EP
gitlab.com
500 errors from SSH signature endpoints (Severity 3)
0
0
0
We are seeing an increase in 500 errors from the SSH signature endpoints affecting commit-related pages for projects using SSH-signed commits. A possible workaround is to use `git pull` and work locally. Details in https://t.co/61EE8eL6EP
gitlab.com
500 errors from SSH signature endpoints (Severity 3)
0
0
0