Follow for updates about the status of GitLab.com.
- Tweets 9,589
- Following 1
- Followers 31,798
- Likes 107
Graphs continue to drop and security report functionality should now be normal. We're resolving this incident. If you have further issues with security reports, please contact support. More info: gitlab.com/gitlab-com/gl-inf… status.gitlab.com
887
The fix has been deployed and we're seeing our graphs return to normal. Users should no longer be seeing missing security reports. We'll continue to monitor for now. More info: gitlab.com/gitlab-com/gl-inf… status.gitlab.com
956
The team continues to work on mitigating the underlying cause of the issue. More info: gitlab.com/gitlab-com/gl-inf… status.gitlab.com
798
The fix is still being implemented and progress is being made on resolving the problem. More info: gitlab.com/gitlab-com/gl-inf… status.gitlab.com
796
The team is still working on the fix.
More info: gitlab.com/gitlab-com/gl-inf… status.gitlab.com
911
The changes we've tried have so far been ineffective. The fix is still in progress. More info: gitlab.com/gitlab-com/gl-inf… status.gitlab.com
796
A fix is being implemented and we will update here once it's complete. More info: gitlab.com/gitlab-com/gl-inf… status.gitlab.com
868
The team is still working on the fix. More info: gitlab.com/gitlab-com/gl-inf… status.gitlab.com
738
No material updates at this time. Mitigation efforts are ongoing. More info: gitlab.com/gitlab-com/gl-inf… status.gitlab.com
681
Some users are not able to generate security reports in pipelines. We've indetified the cause and are working on mitigation. More info: gitlab.com/gitlab-com/gl-inf… status.gitlab.com
709
This incident has been resolved. GitLab.com is operating normally, and we are continuing to monitor the service. status.gitlab.com
849
GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window. status.gitlab.com
951
GitLab services are now operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window. status.gitlab.com
1
958
GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts. status.gitlab.com
1
958
Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon. status.gitlab.com
1
958
Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly. status.gitlab.com
957
We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. status.gitlab.com
1
959
We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly. status.gitlab.com
1
866
We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We will update with more details shortly. status.gitlab.com
2
2
1
967
We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. status.gitlab.com
3
1
947