We have identified the root cause, and are preparing preventative actions. Our services have recovered and we now consider this incident to be resolved. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
GitLab.com Status’s Tweets
Automated
At this time there are no further material updates to provide. We are continuing to monitor the situation. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
We have identified the root cause, and are preparing preventative actions. Our services have recovered and we now consider this incident to be resolved. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
2
Automated
No material updates to provide. We are continuing to monitor. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
1
Automated
Our services have recovered. We are continuing to monitor the application. We have identified the root cause, and are preparing preventative actions. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
Systems have returned to normal and we are continuing to monitor. We plan to share an update in 1 hour. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
1
Automated
Our services are now recovering. We are continuing to monitor and investigate the root cause. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
1
2
Automated
Users may encounter degraded performance or intermittent errors on GitLab.com - specifically with certain CI/CD Pipelines and Merge Requests. We are currently investigating. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
1
1
Automated
Our services have recovered. We are continuing to monitor and investigate the root cause. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
1
1
2
Automated
Users may encounter degraded performance or intermittent errors on GitLab.com. We are currently investigating. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
Users may encounter degraded performance or intermittent errors on GitLab.com. We are currently investigating. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
1
Automated
We have implemented a fix for this problem and monitored the results. We consider this resolved. See gitlab.com/gitlab-com/gl- for details. status.gitlab.com
Automated
We believe we have identified the cause. Systems are returning to normal and we are continuing to monitor. We plan to share an update in 1 hour. More information in gitlab.com/gitlab-com/gl-. status.gitlab.com
1
Automated
We are continuing to investigate. In some cases, a hard refresh improves the behavior. We plan to share an update in two hours. Updates will continue in gitlab.com/gitlab-com/gl-. status.gitlab.com
1
Automated
We are continuing to investigate the cause of this behavior. Please check gitlab.com/gitlab-com/gl- for more information. We plan to share an update in two hours. status.gitlab.com
1
2
Automated
We're currently investigating a degradation of real-time functionality of the application. More information is available in: gitlab.com/gitlab-com/gl-. We plan to share an update in an hour. status.gitlab.com
1
Automated
Job processing is now at normal levels and this incident has now been resolved. We'll continue to work on corrective actions to prevent future occurrences. status.gitlab.com
1
Automated
Job processing is continuing to return to normal. We are planning corrective actions to prevent this particular problem in the future. Additional information in gitlab.com/gitlab-com/gl-. status.gitlab.com
1
Automated
We have identified an increase in jobs as a potential root cause. The recovery is continuing and we are monitoring. status.gitlab.com
3
Automated
We are continuing to investigate. While we have not yet identified a root cause, we are observing a slow recovery that may improve the behavior for some users. We will continue to update gitlab.com/gitlab-com/gl-. status.gitlab.com
1
Automated
We have detected a delay in background job processing and are actively investigating. MRs and pipeline creation may be impacted.
The production issue has more information: gitlab.com/gitlab-com/gl- status.gitlab.com
2
2
4
Automated
The website docs.gitlab.com has been monitored for the last 30 minutes and have returned to operating normally. More details are available in gitlab.com/gitlab-com/gl- status.gitlab.com
2
Automated
The website docs.gitlab.com is accessible again. More details about this incident can be found in gitlab.com/gitlab-com/gl- status.gitlab.com
1
2
Automated
We are still investigating 404 error message on docs.gitlab.com More details about this incident can be found in gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
We are currently investigating 404 error messages from docs.gitlab.com. More details about this incident can be found in gitlab.com/gitlab-com/gl- status.gitlab.com
1
3
Automated
The fix has been deployed and verified on GitLab.com. More information can be found in gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
We are monitoring the status of the merge to fix the issue. We expect the fix to be deployed within six hours.
Logging into the Customers Portal at customers.gitlab.com before attempting to purchase a subscription on Gitlab.com... status.gitlab.com
1
1
Automated
We have identified the merge request that caused this issue; we have reverted that merge request and expect that it will be deployed within eight hours.
Logging into the Customers Portal at customers.gitlab.com before attemptin... status.gitlab.com
1
2
Automated
We believe we have identified a merge request that caused this issue. We are working on deploying a fix. More details are available in gitlab.com/gitlab-com/gl-. status.gitlab.com
Automated
Our engineers have identified the possible root cause, which has been reverted. This incident has been resolved. More information can be found in: gitlab.com/gitlab-com/gl- status.gitlab.com
1
Automated
We are investigating a specific MR as the potential root cause. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
Our services remain in a healthy state. We are continuing to monitor and investigate the root cause. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
Our rollback has completed and we our impacted services have recovered. We will continue to monitor - additional info here: gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
We are beginning a roll-back to revert recently introduced changes. We expect this process to take approximately 1 hour. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
1
1
Automated
No material updates. Investigation ongoing - details in: gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
No material updates to report. Our investigation is still ongoing - details in: gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
Some users may encounter degraded performance or intermittent errors on GitLab.com. We are currently investigating. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
Our Engineers have identified the root cause and implemented a fix. This incident has been resolved. More information can be found in gitlab.com/gitlab-com/gl- status.gitlab.com
1
Automated
Jobs started after 15:20 UTC until 16:07 UTC may error in reporting their status or job trace. Retrying the jobs will succeed. Our engineers will continue to monitor. For more details, please check gitlab.com/gitlab-com/gl- status.gitlab.com
1
Automated
Starting at 15:20 UTC, we started having elevated error rates for runners trying to write to job logs or status. The error rates have since stabilized and our engineers continue to investigate the root cause. For more details, please check https://gitla... status.gitlab.com