Is GitLab down?

We’ve detected issues affecting a small subset of users attempting artifact uploads. The team is actively investigating to identify the full scope of the impact, and we’ll provide another update as soon as we have findings to share. Thank you for your patience. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

We’ve detected issues affecting artifact uploads. The team is actively investigating, and we’ll provide another update as soon as we have findings to share. Thank you for your patience.

We are still seeing cases but tat a much less frequent rate. We will continue looking for the root cause and monitor the error rate.

We are still seeing cases but tat a much less frequent rate. We will continue looking for the root cause and monitor the error rate.

We are no longer observing elevated error rates and have identified the root cause. We are marking this incident as resolved while we implement additional fixes behind the scenes.

We are seeing delays in Security Policy Evaluation which are affecting MR approvals. The cause is under investigation. More details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

We are seeing delays in Security Policy Evaluation which are affecting MR approvals. The cause is under investigation. More details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904.

Our product team is still working on finding the cause and potential mitigation steps for this issue. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904.

Our product team is still working on finding the cause and potential mitigation steps for this issue. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904.

We are still investigating this issue. Users may still experience delays in Security Policy Evaluations, impacting MR approvals. Details in: More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904

We are still investigating this issue. Users may still experience delays in Security Policy Evaluations, impacting MR approvals. Details in: More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904

We believe we have identified the underlying problem and are working to implement mitigating changes. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904

We believe we have identified the underlying problem and are working to implement mitigating changes. More info: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904

Policy evaluations and MR approvals are executing normally. We're continuing to monitor the situation while working on improvements to prevent this in the future. More: http://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904

Policy evaluations and MR approvals are executing normally. We're continuing to monitor the situation while working on improvements to prevent this in the future. More: http://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22904

We'll now mark this as resolved while we look at additional changes as preventative measures for the future.

We're observing an increase in CI job queues. Users may see jobs stuck in a pending state for longer than usual. Jobs may not fire their associated webhooks or integrations. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22897 Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

We're observing an increase in CI job queues. Users may see jobs stuck in a pending state for longer than usual. Jobs may not fire their associated webhooks or integrations. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22897

We're still observing elevated CI job queues and are working to address the problem. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22897

We're still observing elevated CI job queues and are working to address the problem. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22897

CI job execution delays have improved significantly, and the backlog of pending jobs is shrinking. We're continuing to monitor the situation.

CI job execution delays have improved significantly, and the backlog of pending jobs is shrinking. We're continuing to monitor the situation.

We are no longer observing delays in CI job execution and the backlog of pending jobs has been worked through. We'll now be marking this as resolved.

Starting a new chat with an agent from the AI catalog does not work, and the websocket connection is immediately dropped. We are reverting the merge request that introduced the failure. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22880. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

Starting a new chat with an agent from the AI catalog does not work, and the websocket connection is immediately dropped. We are reverting the merge request that introduced the failure. The incident is being tracked in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22880.

The merge request that introduced the failure was reverted, and custom/catalog agents are working again. More information is available in gitlab.com/gitlab-com/gl-infra/production/-/work_items/22880.

We are investigating an incident affecting GitLab.com CI/CD jobs using instance runners. Some jobs may remain pending longer than expected or may not be picked up by a runner, which can delay pipelines and deployments. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22845 Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close Follow our status updates on Twitter/X @gitlabstatus Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via iCalendar iCalendar Feed Close

We are investigating an incident affecting GitLab.com CI/CD jobs using instance runners. Some jobs may remain pending longer than expected or may not be picked up by a runner, which can delay pipelines and deployments.

The incident affecting GitLab.com CI/CD jobs using instance runners is now resolved. Some jobs were delayed or remained pending while a manually initiated pg_repack database maintenance operation caused contention on the CI database, affecting runner communication and job pickup. The maintenance operation was terminated and runner metrics recovered. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22845