500 errors, CI checkout failures and slow page loads

Update timeline

1. investigating Jun 30, 2026, 04:08 PM UTC

   We are investigating the cause, but the symptoms are: 500 errors, CI jobs can't check out repos, slow merge request page loading, slow page loading 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 Jun 30, 2026, 04:08 PM UTC

   We are investigating the cause, but the symptoms are: 500 errors, CI jobs can't check out repos, slow merge request page loading, slow page loading

3. investigating Jun 30, 2026, 04:44 PM UTC

   We are continuing to investigate and look into the increased errors on GitLab.com

4. investigating Jun 30, 2026, 04:44 PM UTC

   We are continuing to investigate and look into the increased errors on GitLab.com

5. identified Jun 30, 2026, 04:52 PM UTC

   We have identified the cause of the increased error rate and are taking corrective action and monitoring the incident.

6. identified Jun 30, 2026, 04:52 PM UTC

   We have identified the cause of the increased error rate and are taking corrective action and monitoring the incident.

7. identified Jun 30, 2026, 05:39 PM UTC

   We are continuing to investigate and work to resolve the degraded performance on GitLab.com

8. identified Jun 30, 2026, 05:39 PM UTC

   We are continuing to investigate and work to resolve the degraded performance on GitLab.com

9. monitoring Jun 30, 2026, 06:26 PM UTC

   We have identified the issue and taken action to correct the matter and are monitoring GitLab.com. We will provide further updates as information is available or when the issue is confirmed resolved.

10. monitoring Jun 30, 2026, 06:26 PM UTC

    We have identified the issue and taken action to correct the matter and are monitoring GitLab.com. We will provide further updates as information is available or when the issue is confirmed resolved.

11. resolved Jun 30, 2026, 07:46 PM UTC

    This issue is resolved and performance on GitLab.com has returned to normal.