Twitter | Search | |
GitLab.com Status
Follow for updates about the status of . Find all other tweets about the project and company .
6,459
Tweets
1
Following
31,620
Followers
Tweets
GitLab.com Status 22h
We've confirmed that this incident is resolved.
Reply Retweet Like
GitLab.com Status 23h
The fix has finished deployment to production at 8:56am UTC.
Reply Retweet Like
GitLab.com Status Aug 6
We've deployed the fixed to GitLab Canary (). We're exploring the options to deploy the fix to the production .
Reply Retweet Like
GitLab.com Status Aug 6
Replying to @losslesscom
If you are concerned you have encountered a bug, please check our issue tracker: . You can also add an issue so that the right team here at GitLab can take a look if your experience doesn't match any existing reported. Thanks!
Reply Retweet Like
GitLab.com Status Aug 6
Gitaly isn’t yet able to handle reference transactions introduced in the recent upgrade to Git 2.28, causing this issue. A revert of the MR that caused it has been merged. We are now exploring options to deploy the fix to production.
Reply Retweet Like
GitLab.com Status Aug 6
A bug on has been identified that is preventing tags and branches from being pushed simultaneously. A fix is currently underway. See for more information.
Reply Retweet Like
GitLab.com Status Jul 27
Replying to @rizwanatta2
Hey there, we're checking in to see if you're still seeing this issue from a few days ago? Let us know!
Reply Retweet Like
GitLab.com Status Jul 27
Replying to @rizwanatta2
It's likely your primary email hasn't been reconfirmed on GitLab, causing this login issue. Can you please request a new confirmation email here and try again?
Reply Retweet Like
GitLab.com Status Jul 24
Can you log in now? If you still can't log in, please either open a support ticket if you are a paid user or open an issue on our forum: Thanks!
Reply Retweet Like
GitLab.com Status Jul 24
Replying to @TzeAiyor
Hey there, if you still have an issue with our container registry - you can either open a support ticket if you are paid user or open a topic on our forum about this issue: Thanks!
Reply Retweet Like
GitLab.com Status Jul 22
Replying to @thomasvodrazka
Thanks for reaching out! This might be a related issue, FYI: If you still get an error, please open an issue for us to track, Thanks!
Reply Retweet Like
GitLab.com Status Jul 22
Replying to @velykov
Can you request it now?
Reply Retweet Like
GitLab.com Status Jul 22
Replying to @bftsystems
Glad to hear that!
Reply Retweet Like
GitLab.com Status Jul 22
Twitter is still investigating a number of account situations including ours. If you are reaching out to for assistance, you may get a response from this handle () or from one of team members' Twitter accounts.
Reply Retweet Like
GitLab.com Status Jul 17
Thanks everyone for their patience. We have seen traffic resume normally. Any review will continue through the incident issue
Reply Retweet Like
GitLab.com Status Jul 17
Some users are still experiencing issues accessing GitLab services especially if they're using 1.1.1.1 Cloudflare's DNS. Cloudflare's status page also suggests some locations are still affected. We recommend using a different DNS resolver at least t...
Reply Retweet Like
GitLab.com Status Jul 17
Cloudflare seems to have resolved their DNS issues, and all services are operational now. We are monitoring for now. An incident issue was created and reviewed in
Reply Retweet Like
GitLab.com Status Jul 17
We have confirmed that the Cloudflare issue has affected all our services including Support's ZenDesk instances and our status page. We will continue to provide updates as we learn more.
Reply Retweet Like
GitLab.com Status Jul 17
is experiencing issues related to DNS with Cloudflare. We are investigating.
Reply Retweet Like
GitLab.com Status Jul 17
After a period of monitoring, we've observed no further errors in our logging related to this issue and have confirmed that the hotpatch has resolved the issue.
Reply Retweet Like