Project File Browser Inaccessible on CanaryOperational

Components

Website, API, Git Operations, Container Registry, GitLab Pages, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, Background Processing, GitLab Customers Portal, Support Services, packages.gitlab.com, version.gitlab.com, forum.gitlab.com

Locations

Google Compute Engine, Azure, Digital Ocean, Zendesk, AWS



May 30, 2020 02:58 UTC
[Resolved] The issue has been resolved and the canary environment is now operational. Full details at gitlab.com/gitlab-org/gitlab/-/issues/219478

May 30, 2020 02:09 UTC
[Monitoring] The fix has been fully deployed and the affected canary environment is now fully operational. We are monitoring at this time to ensure the issue doesn't recur.

May 30, 2020 00:08 UTC
[Identified] The fix is being applied and we have updated gitlab.com/gitlab-org/gitlab/-/issues/219478 with the details. The canary environment should no longer return an error once this is fully deployed.

May 29, 2020 22:24 UTC
[Identified] We've identified the cause of the issue and have a plan to deploy a fix to ensure that production remains unaffected. Details in gitlab.com/gitlab-org/gitlab/-/issues/219478.

May 29, 2020 17:05 UTC
[Investigating] To disable canary on GitLab.com head to next.gitlab.com and toggle the switch to Current. This should mitigate this issue if you're affected while we investigate a fix. More details are available in gitlab.com/gitlab-org/gitlab/-/issues/219478.

May 29, 2020 17:02 UTC
[Investigating] We're investigating an issue on our canary environment causing the file browser of internal and private projects to not load. See status.gitlab.com for steps to disable canary if you're affected.

May 29, 2020 17:00 UTC
[Investigating] GitLab.com is operational, but we're investigating an issue on our canary environment causing the file browser of internal and private projects to not load. Disabling canary mitigates this. See status.gitlab.com for steps to disable it if you're affected.

Back to current status