This incident has been resolved. More information can be found in gitlab.com/gitlab-com/gl-. status.gitlab.com
GitLab.com Status’s Tweets
Automated
We have identified the cause, a fix has been applied and we are continuing to monitor as we recover. More details can be found in gitlab.com/gitlab-com/gl-. status.gitlab.com
Automated
We are currently investigating issues with delays in background processing for web and API traffic. More details about this incident can be found in gitlab.com/gitlab-com/gl- status.gitlab.com
2
Automated
The fix has been deployed and we are no longer seeing login issues. We therefore believe that this incident has been resolved. Our team will continue to monitor and update on the incident issue: gitlab.com/gitlab-com/gl- status.gitlab.com
1
1
3
Automated
We've determined that the issue affects GitHub, Bitbucket and Salesforce logins to GitLab. Also, the product team has identified the root cause of the issue and working on the fix. For more details, refer to the issue : gitlab.com/gitlab-com/gl- status.gitlab.com
2
5
Automated
We are investigating an issue where login using GitHub is failing with "too many requests received" error status.gitlab.com
4
Automated
Root cause: An unexpected deployment behaviour affected the Consul cluster that several of our services depend on (eg. Patroni) status.gitlab.com
Automated
2
Automated
3
2
4
Automated
We have detected a problem related to GitLab.com services and are actively investigating.
More details to follow. status.gitlab.com
7
7
11
Automated
This incident has been resolved and Customers Portal is now operational. More information can be found in gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
We have restarted the service and are now monitoring Customers Portal for the next hour before marking the incident as resolved. More details can be found in gitlab.com/gitlab-com/gl- status.gitlab.com
1
3
Automated
We have identified a problem with the GitLab Customers Portal.
More details are available in gitlab.com/gitlab-com/gl-. status.gitlab.com
2
Automated
The scheduled Customers Portal Database Migration has been completed. status.gitlab.com
Automated
The scheduled Customers Portal Database Migration has been completed. status.gitlab.com
Automated
The issue has been mitigated.
All services are operational. status.gitlab.com
2
Automated
A fix was applied and the incident is now mitigated. Our Engineers will continue monitoring the systems. For more details please see: gitlab.com/gitlab-com/gl- status.gitlab.com
1
Automated
Our Engineers are still working on finding the root cause and implementing a fix. For more details please see gitlab.com/gitlab-com/gl- status.gitlab.com
1
Automated
We are seeing an increase in error rate on GitLab.com. Our Engineers are working on identifying the root cause and implementing a fix. For details, please see: gitlab.com/gitlab-com/gl- status.gitlab.com
1
1
Automated
The issue causing the intermittent increases in 520 and 525 errors via Cloudflare on GitLab SaaS has been resolved. For more details visit: gitlab.com/gitlab-com/gl-. status.gitlab.com
1
1
Automated
We've seen an improvement of substantially fewer intermittent 520 and 525 errors via Cloudflare on GitLab SaaS. We're continuing to monitor this progress toward resolution. Details in gitlab.com/gitlab-com/gl-. status.gitlab.com
Automated
Cloudflare has declared an incident and is working on implementing a fix for the intermittent 520 errors via Cloudflare on GitLab SaaS. Details in gitlab.com/gitlab-com/gl-. status.gitlab.com
Automated
Our investigation to find the a solution for the intermittent 520 errors via Cloudflare on GitLab SaaS continues with Cloudflare engineers. Details in gitlab.com/gitlab-com/gl-. status.gitlab.com
Automated
We're still investigating reports of users receiving intermittent 520 errors via Cloudflare on GitLab SaaS with Cloudflare engineers. Details in gitlab.com/gitlab-com/gl-. status.gitlab.com
1
Automated
No material updates to report. We were able to determine the error is occurring within a single edge location of our CDN (SJC).
Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
1
Automated
No material updates to report. We are working with our CDN provider to fully mitigate the issue. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
2
Automated
We've determined that the issue affects only a small percentage of requests and verified that all of GitLab's systems are operational. We're following up with our CDN provider to investigate further and are monitoring to ensure we don't see an increase ... status.gitlab.com
1
Automated
We're currently investigating reports of users receiving intermittent 520 errors via Cloudflare on GitLab SaaS. Details in gitlab.com/gitlab-com/gl-. status.gitlab.com
1
Automated
Since there's no new report of affected user. We're closing this incident for now. Our team will continue to monitor and update on the incident issue: gitlab.com/gitlab-com/gl- status.gitlab.com
1
2
Automated
No material updates to report. We are working with our third party provider to fully mitigate the issue. A small subset of users in the EU/Asia region may still face login issues. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
1
Automated
Moving issue to a monitoring state while we work with our third party provider to fully mitigate the issue. A small subset of users in the EU/Asia region may still face login issues. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
We now believe the issue to be specific to a subset of users in the EU/Asia regions. Our investigation is still ongoing. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
We believe we have implemented a change to alleviate the issue. We are working to confirm this - more details in: gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
We believe this to be related to a third party provider. We are attempting to implement a workaround. Impacted users seem to be specific to the UK region. Details in: gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
No material updates at this time - we are still investigating the issue. This is not impacting all users. More details in: gitlab.com/gitlab-com/gl- status.gitlab.com
Automated
We have received some reports of users being unable to login to GitLab.com. We are currently investigating the issue - details in: gitlab.com/gitlab-com/gl- status.gitlab.com
1
Automated
We have resolved this issue with the change to the feature flag. See the gitlab.com/gitlab-com/gl- issue for details. status.gitlab.com
1
Automated
We believe that this issue impacts people using SSO. With the issue mitigated, see gitlab.com/gitlab-com/gl- for additional information. status.gitlab.com
1
5
Automated
We believe we have identified the cause of the problem and are working to confirm that changing a feature flag has mitigated the problem. status.gitlab.com
1