gitlabstatus's profile picture. Follow for updates about the status of http://GitLab.com.

GitLab.com Status

@gitlabstatus

Follow for updates about the status of http://GitLab.com.

GitLab.com functionality has returned to normal after Cloudflare applied a fix at 09:12 UTC. For more details, see gitlab.com/gitlab-com/gl-… status.gitlab.com


GitLab.com is becoming available for users. Cloudflare have applied a fix at their side at 09:12 UTC. We will continue to monitor the situation status.gitlab.com


GitLab.com is inaccessible at the moment due to a Cloudflare outage. We are currently investigating the cause. status.gitlab.com


This issue has been resolved and all systems are back to fully operational. Details can be found in gitlab.com/gitlab-com/gl-… status.gitlab.com


We have finished the rollback of the MR to restore full operation. For further details, see gitlab.com/gitlab-com/gl-… status.gitlab.com


We have started the rollback of the MR that is the cause to restore full operation. For further details, see gitlab.com/gitlab-com/gl-… status.gitlab.com


We are seeing a problem with the Merged tab of merge request homepage not loading. The workaround is to use the Search tab instead. We are working on rolling back the relevant MR. Details in gitlab.com/gitlab-com/gl-… status.gitlab.com


The fix has been deployed to production. We are no longer seeing failures for pipelines that use inputs. This is now resolved. More details in: gitlab.com/gitlab-com/gl-… status.gitlab.com


We are currently testing a fix for the pipeline creation issues in our sandbox environment. We estimate that the fix will be deployed to the production environment in approximately three hours. More info: gitlab.com/gitlab-com/gl-… status.gitlab.com


We are in the process of deploying a fix for the pipeline creation issues. Our next update will follow deployment completion as we monitor the resolution. More info: gitlab.com/gitlab-com/gl-… status.gitlab.com


We've identified the root cause of pipeline creation failures affecting pipelines that use inputs since Nov 24, 11:00 UTC. A fix is in the process of being deployed and we're monitoring for resolution. More info here: gitlab.com/gitlab-org/git… status.gitlab.com


We have completed the infrastructure restoration tasks to fix the connectivity issue with the affected Runner. Since 17:51 UTC jobs on this Runner are being processed normally. This is now resolved. status.gitlab.com


We have identified the configuration causing network disruption with the affected Runner and we are working on fixing it. See gitlab.com/gitlab-com/gl-… for details. status.gitlab.com


No material updates to share. We appreciate your patience while we continue investigating this issue, please see gitlab.com/gitlab-com/gl-… for details. status.gitlab.com


We have identified a misconfiguration in our Runner infrastructure's routing policies as the potential cause for this issue. Follow gitlab.com/gitlab-com/gl-… for details. status.gitlab.com


We continue to troubleshoot network connectivity for the affected Runner, no material updates to report. Follow gitlab.com/gitlab-com/gl-… for details. status.gitlab.com


Latest troubleshooting results point a networking issue preventing connectivity with the affected macOS Runner. Investigation continues at gitlab.com/gitlab-com/gl-…. status.gitlab.com


We continue investigating the root cause. See gitlab.com/gitlab-com/gl-… for more details status.gitlab.com


No material updates to report. We continue troubleshooting the runner's unavailability. See gitlab.com/gitlab-com/gl-… for more details status.gitlab.com


Investigation is ongoing, and we're reviewing relevant runbooks for additional troubleshooting steps. See gitlab.com/gitlab-com/gl-… for more details status.gitlab.com


Loading...

Something went wrong.


Something went wrong.