GitLab.com Status
@gitlabstatus
Follow for updates about the status of http://GitLab.com.
Vous pourriez aimer
This incident has been resolved and exact code search is now operational. For more information see gitlab.com/gitlab-com/gl-…. status.gitlab.com
We are in the process of releasing an update that should resolve issues with exact code search. For more information see gitlab.com/gitlab-com/gl-…. status.gitlab.com
This incident has been mitigated. More information can be found in gitlab.com/gitlab-com/gl-…. status.gitlab.com
A recent change has been confirmed as the cause of this issue. Our team is working on reverting the change. More details here: gitlab.com/gitlab-com/gl-… status.gitlab.com
No material updates to report. Our team is still investigating this issue. More details here: gitlab.com/gitlab-com/gl-… status.gitlab.com
Our team is still investigating this issue. More details here: gitlab.com/gitlab-com/gl-… status.gitlab.com
We are currently investigating 500 errors affecting code search functionality on GitLab.com. Users may experience failures when searching code in repositories. status.gitlab.com
Our team has been monitoring and GitLab is now operating normally. This incident is now resolved. status.gitlab.com
The issue is currently mitigated and we're seeing recovery across GitLab. Our team is continuing to monitor. status.gitlab.com
We're currently experiencing 500 errors on GitLab.com. Our team is currently investigating. status.gitlab.com
This issue is now resolved. We experienced unavailability accompanied with 500 errors around 17:15 - 17:30 UTC. This has now returned to normal operations. Our team is continuing to investigate the root cause. status.gitlab.com
We're seeing that behavior is largely normal at this time. Our team is still investigating the root cause. status.gitlab.com
Our team is still investigating . No material updates at this time. status.gitlab.com
Our team is still investigating this issue but error rate is currently improving. status.gitlab.com
Our team is currently investigating 500 errors on GitLab.com. status.gitlab.com
Our team has not seen any additional issues with git operations within the last hour. We are creating follow up items to further investigate resource exhaustion patterns. status.gitlab.com
We are currently investigating issues with git operations. More details about this incident can be found in gitlab.com/gitlab-com/gl-…. status.gitlab.com
This incident has been resolved is now operational. status.gitlab.com
This incident only impacts the gitlab-org/gitlab project and it's forks. Other projects are not affected by this incident. More details can be found in gitlab.com/gitlab-com/gl-…. status.gitlab.com
United States Tendances
- 1. Bills 132K posts
- 2. Falcons 45K posts
- 3. Snell 17.6K posts
- 4. Josh Allen 22.7K posts
- 5. Bears 71.7K posts
- 6. #Dodgers 12.8K posts
- 7. Caleb 39.9K posts
- 8. Bijan 27.9K posts
- 9. Turang 3,281 posts
- 10. Jake Moody 7,677 posts
- 11. #NLCS 11.3K posts
- 12. phil 146K posts
- 13. Roki 5,423 posts
- 14. AFC East 7,684 posts
- 15. Jayden Daniels 8,421 posts
- 16. Brewers 42.4K posts
- 17. Joe Brady 4,289 posts
- 18. Swift 284K posts
- 19. Commanders 43.9K posts
- 20. McDermott 6,514 posts
Vous pourriez aimer
-
🦊 GitLab
@gitlab -
GitHub Status
@githubstatus -
GitHub
@github -
React
@reactjs -
Docker
@Docker -
The Linux Foundation
@linuxfoundation -
Grafana
@grafana -
Visual Studio Code
@code -
Node.js
@nodejs -
Raspberry Pi
@Raspberry_Pi -
Kubernetes
@kubernetesio -
Vue
@vuejs -
HashiCorp
@HashiCorp -
Red Hat
@RedHat -
Red Hat OpenShift
@openshift
Something went wrong.
Something went wrong.