Twitter | Search | |
GitLab.com Status
Follow for updates about the status of . Find all other tweets about the project and company .
5,702
Tweets
1
Following
28,214
Followers
Tweets
GitLab.com Status Sep 12
A developer with credentials for the kubernetes cluster running our Docker registry ran a command with the context accidentally set to production, rather than a local test environment. We'll be exploring ways to safeguard Production in an Incident R...
Reply Retweet Like
GitLab.com Status Sep 12
Our Docker image registry became unavailable for ~12 minutes beginning at 15:16 UTC . At which point, all docker commands (e.g. "pull", "push", etc.) would have received a 503 response. The registry is back online. The root cause investigation is ta...
Reply Retweet Like
GitLab.com Status Sep 11
We're no longer observing errors related to the missing database column. For those wondering about the "Support Bot", it's specific to projects with Service Desk integration turned on. We're calling the all-clear! And extending our apologies to an...
Reply Retweet Like
GitLab.com Status Sep 11
We're actively monitoring application health. Engineers are looking to determine whether any additional configuration changes or deployments need to take place to prevent a reoccurrence of the issue.
Reply Retweet Like
GitLab.com Status Sep 11
At 17:52 UTC we completed a deployment that introduced code dependent on a database column that had previously been removed. Users attempting to take actions with the web UI in projects that previously utilized the "Support Bot" were impacted. See h...
Reply Retweet Like
GitLab.com Status Sep 9
Replying to @tueieo
Hello! Sorry for the inconvenience, are you still experiencing this?
Reply Retweet Like
GitLab.com Status Sep 9
Replying to @camflan
Hello! Sorry for the inconvenience, are you still experiencing this?
Reply Retweet Like
GitLab.com Status Aug 29
The partial degradation performance has been resolved. Thank you for your patience!
Reply Retweet Like
GitLab.com Status Aug 29
We have identified the abuse pattern, and we are executing the corrective actions. We are tracking on
Reply Retweet Like
GitLab.com Status Aug 29
We are observing some performance degradation on one storage node, due to possible abuse activity.
Reply Retweet Like
GitLab.com Status Aug 28
GitLab-ce should be working now for push, pull and fetch on .
Reply Retweet Like
GitLab.com Status Aug 28
We have repaired some of the issues on GitLab-CE and you should be able to push and pull. We are continuing to fix issues so that fetch works properly.
Reply Retweet Like
GitLab.com Status Aug 28
For GitLab-CE, We are working on repairing the files that are causing the issues with fetching the project.
Reply Retweet Like
GitLab.com Status Aug 28
We have been alerted that we are seeing errors on push, pull, and fetch with GitLab-CE. We are working on issue .
Reply Retweet Like
GitLab.com Status Aug 22
Replying to @ThisIsMissEm
Hello! We're sorry for the inconvenience, are you still having problems?
Reply Retweet Like
GitLab.com Status Aug 22
Replying to @catgirlsec
Hello! We're sorry for the inconvenience, are you still having problems?
Reply Retweet Like
GitLab.com Status Aug 20
web and API request latencies are back at normal levels.
Reply Retweet Like
GitLab.com Status Aug 20
web and API request latencies are back at normal levels. We'll continue to monitor the health of the requests as the day continues.
Reply Retweet Like
GitLab.com Status Aug 20
requests are still slightly degraded. We are continuing to validate ideas on the one affected read-only database and it's pgbouncer cpu usage.
Reply Retweet Like
GitLab.com Status Aug 20
We are continuing to test ideas to improve performance the 1 readonly DB node that is slowing web and API requests on .
Reply Retweet Like