Artifact upload failures and timeouts

Update timeline

1. investigating Sep 11, 2026, 05:50 AM UTC

   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

2. investigating Sep 11, 2026, 05:50 AM UTC

   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.

3. monitoring Sep 11, 2026, 12:16 PM UTC

   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.

4. monitoring Sep 11, 2026, 12:16 PM UTC

   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.

5. resolved Sep 11, 2026, 07:22 PM UTC

   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.