GitLab incident

Increase of HTTP 50X errors on GitLab.com

Resolved after 1 day 16 hours, affecting Website and API and 1 more, on October 13, 2026.

monitoring Oct 14, 2026, 02:33 AM UTC

Monitoring confirms that GitLab.com services have remained stable. We are continuing to monitor for any recurrence of the issues before marking this incident as resolved.

Started
Oct 13, 2026, 07:10 AM UTC
Resolved
Oct 14, 2026, 11:40 PM UTC
Duration
1d 16h
Detected by Pingoru
Oct 13, 2026, 07:10 AM UTC

Affected components

WebsiteAPIGit OperationsPackage RegistryContainer RegistryGitLab DuoGitLab agent server for Kubernetes (GitLab agent server for Kubernetes — Google Compute Engine)

Update timeline

  1. investigating Oct 13, 2026, 07:10 AM UTC

    We are currently investigating reports of an increase of HTTP 50X errors on GitLab.com 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 Oct 13, 2026, 07:10 AM UTC

    We are currently investigating reports of an increase of HTTP 50X errors on GitLab.com

  3. investigating Oct 13, 2026, 07:30 AM UTC

    We are seeing an improvement in errors rates in our monitoring, starting from 07:14 UTC. We are still identifying the root cause.

  4. investigating Oct 13, 2026, 07:30 AM UTC

    We are seeing an improvement in errors rates in our monitoring, starting from 07:14 UTC. We are still identifying the root cause.

  5. investigating Oct 13, 2026, 07:48 AM UTC

    General GitLab.com service continues to improve. We're now focused on restoring Duo services.

  6. investigating Oct 13, 2026, 07:48 AM UTC

    General GitLab.com service continues to improve. We're now focused on restoring Duo services.

  7. monitoring Oct 13, 2026, 07:59 AM UTC

    We are seeing improvements across all services on GitLab.com. We are resuming our investigation on identifying the root cause.

  8. monitoring Oct 13, 2026, 07:59 AM UTC

    We are seeing improvements across all services on GitLab.com. We are resuming our investigation on identifying the root cause.

  9. monitoring Oct 14, 2026, 02:33 AM UTC

    Monitoring confirms that GitLab.com services have remained stable. We are continuing to monitor for any recurrence of the issues before marking this incident as resolved.

  10. monitoring Oct 14, 2026, 02:33 AM UTC

    Monitoring confirms that GitLab.com services have remained stable. We are continuing to monitor for any recurrence of the issues before marking this incident as resolved.

  11. resolved Oct 14, 2026, 11:40 PM UTC

    We have been monitoring this issue for a few days with no reported occurrences.

Your product runs on more than GitLab

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →