GitLab incident

Issues with webhook deliveries

Minor Resolved View vendor source →

GitLab experienced a minor incident on August 4, 2026 affecting Website and API and 1 more component, lasting 22h 36m. The incident has been resolved; the full update timeline is below.

Started
Aug 04, 2026, 04:42 PM UTC
Resolved
Aug 05, 2026, 03:19 PM UTC
Duration
22h 36m
Detected by Pingoru
Aug 04, 2026, 04:42 PM UTC

Affected components

WebsiteAPIGitLab agent server for Kubernetes (Google Compute Engine)

Update timeline

  1. investigating Aug 04, 2026, 04:42 PM UTC

    We are investigating reports of webhook deliveries from GitLab.com originating from IP addresses outside our documented ranges. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22637. 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 Aug 04, 2026, 04:42 PM UTC

    We are investigating reports of webhook deliveries from GitLab.com originating from IP addresses outside our documented ranges. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22637.

  3. investigating Aug 04, 2026, 06:49 PM UTC

    Our investigation is ongoing. We will provide another update by 21:00 UTC.

  4. investigating Aug 04, 2026, 06:49 PM UTC

    Our investigation is ongoing. We will provide another update by 21:00 UTC.

  5. identified Aug 04, 2026, 09:07 PM UTC

    We've traced the issue to a recent network change and are preparing a fix. Another update will be provided by 23:00 UTC.

  6. identified Aug 04, 2026, 09:07 PM UTC

    We've traced the issue to a recent network change and are preparing a fix. Another update will be provided by 23:00 UTC.

  7. identified Aug 04, 2026, 11:14 PM UTC

    Deployment of the fix is progressing steadily. Another update will be provided once deployed. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22637.

  8. identified Aug 04, 2026, 11:14 PM UTC

    Deployment of the fix is progressing steadily. Another update will be provided once deployed. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22637.

  9. monitoring Aug 05, 2026, 03:26 AM UTC

    A fix has been deployed and checks have confirmed that unexpected IP addresses are no longer being used.

  10. monitoring Aug 05, 2026, 03:26 AM UTC

    A fix has been deployed and checks have confirmed that unexpected IP addresses are no longer being used.

  11. resolved Aug 05, 2026, 03:19 PM UTC

    Webhook delivery failures have subsided in logs, and customer reports indicate no further errors. This incident is considered resolved.