Companies / GitLab / incidents

GitLab: Intermittent 400 errors when logging into GitLab.com

Affected components: Website

Timeline of updates

1. investigating2026-03-03 16:46 UTC

   Users are intermittently seeing 400 Bad Request errors when attempting to log into GitLab.com. This does not seem to be affecting all users at the moment and investigation is ongoing. See https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details.

2. investigating2026-03-03 16:56 UTC

   No material updates to report at this time. We continue tracing the errors to determine the root cause. Follow https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details.

3. investigating2026-03-03 17:08 UTC

   We’ve identified a recent deployment that may be contributing to this issue and are preparing a rollback to see if it improves the situation. Keep tuned for more updates on https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436.

4. investigating2026-03-03 17:20 UTC

   Rollback is still in progress. We’ll update this status page as soon as we have new information to share. See https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details.

5. investigating2026-03-03 17:52 UTC

   The rollback has completed, but we are not yet seeing a reduction in the frequency of the error messages. Investigation continues, see https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details.

6. investigating2026-03-03 18:05 UTC

   We are now investigating whether an upstream component could be contributing to the behavior, though this has not yet been confirmed. See https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for updates.

7. investigating2026-03-03 18:39 UTC

   We started reviewing a recent change to our HTTP router as a contributing factor, but have now ruled it out and continue investigating other potential causes. We’ll provide another update once we have new information to share.

8. investigating2026-03-03 19:04 UTC

   We are involving Cloudflare to investigate a potential upstream problem and have reached out for their assistance. Please follow https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details.

9. investigating2026-03-03 20:22 UTC

   We continue working with Cloudflare support to figure out the cause of these errors. We will update this incident as any findings come along. See https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details.

10. investigating2026-03-03 21:50 UTC

    Cloudflare has identified a potential lead on their side and is investigating further. We will update this status page once we have more information to share from their side. Follow https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details.

11. identified2026-03-03 23:01 UTC

    Cloudflare has declared a public incident to investigate this issue on their end. Please follow https://www.cloudflarestatus.com/incidents/t2skq2t69g5s and https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details.

12. monitoring2026-03-04 00:13 UTC

    The upstream Cloudlfare incident has been resolved and now we monitor to confirm the login error is no longer present in our logs before proceeding to resolve this incident. See https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details.

13. resolved2026-03-04 01:40 UTC

    Per further log inspection on our side, we're no longer seeing the problem occurring. The incident is now resolved. Refer to https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details.

Rewindex changes for this incident

• Major incident: Intermittent 400 errors when logging into GitLab.com 2026-03-03 16:46 UTC

Impact, status and times are the vendor’s own, as last archived. View on status.gitlab.com (opens in new tab). GitLab profile · Recent GitLab incidents · Markdown · JSON