Dec 4, 18:33 UTC
Resolved – This incident has been resolved.
Dec 4, 17:24 UTC
Monitoring – A fix has been implemented and we are monitoring the results.
Dec 4, 16:50 UTC
Investigating – We are currently investigating this issue.
Day: December 4, 2024
GitLab – Fargate runner error – file name too long
December 4, 2024 15:16 UTC
Investigating – We are currently investigating issues with GitLab runners with Fargate driver returning “file name too long” errors. More details about this incident can be found in https://gitlab.com/gitlab-com/gl-infra/production/-/issues/18939
Investigating – We are currently investigating issues with GitLab runners with Fargate driver returning “file name too long” errors. More details about this incident can be found in https://gitlab.com/gitlab-com/gl-infra/production/-/issues/18939
December 4, 2024 15:42 UTC
Identified – We’ve identified cause of the issue and are working on resolving it. More details can be found in https://gitlab.com/gitlab-com/gl-infra/production/-/issues/18939.
December 4, 2024 15:46 UTC
Monitoring – We have disabled the feature flag and are now monitoring the issue for 1 hour before marking as resolved. More details can be found in https://gitlab.com/gitlab-com/gl-infra/production/-/issues/18939.
December 4, 2024 16:50 UTC
Resolved – As no new user reports have been received during our monitoring period we consider this incident resolved. See https://gitlab.com/gitlab-com/gl-infra/production/-/issues/18939 for the full incident history.
Firebase – RESOLVED: High Error rate from Remote Config Fetch Service
Incident began at 2024-12-04 02:00 and ended at 2024-12-04 03:40 (all times are US/Pacific).
This issue is now mitigated for Firebase Fetch Server.
Affected products: Remote Config