GitLab Outage History

25 incidents recorded over the last 365 days, 25 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live GitLab status99.90% uptime history

Every Recorded GitLab Incident

GitLab incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 10, 2026Errors and slow performance on merge requests in the specific groups.We are investigating reports of errors and slow performance on merge request and pipeline pages for projects in the specific groups. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/2315020h 30mResolved
Oct 8, 2026Delayed job completionWe are currently investigating delays in job completion: CI jobs remain running after success, delaying pipeline progression. Details https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/231332h 34mResolved
Oct 7, 2026Job delays on saas-linux-small-amd64 hosted runnersAn incident affecting CI/CD jobs on GitLab.com instance runners has been resolved. Job pickup delays should no longer be occurring and we are continuing to monitor to confirm full recovery. Details in…1h 13mResolved
Oct 1, 2026Job delays on saas-linux-small-amd64 hosted runnersSome CI/CD jobs using saas-linux-small-amd64 hosted runners are experiencing delays before starting. We are restoring affected runner capacity and monitoring recovery. Delays may continue while the backlog clears. The…3h 17mResolved
Oct 1, 2026Delayed email delivery for some email service providersWe’ve detected email delivery delays affecting a small number of email service providers. The team is actively investigating to identify the full scope and impact. The incident is being tracked in…11h 37mResolved
Sep 29, 2026Security Reports not loading for some usersSecurity and vulnerability reports are not loading or being ingested for some users. We are investigating now. For more info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/2302418h 10mResolved
Sep 25, 2026Security Reports not loading for some usersSome users are not able to generate security reports in pipelines. We've indetified the cause and are working on mitigation. More info: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/230245h 16mResolved
Sep 24, 2026503s on GitLab.comWe are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly.5h 36mResolved
Sep 24, 2026500 errors while accessing projectsWe have received reports that some users are unable to access projects and are encountering 500 error messages. Our team is currently investigating the cause. You can follow developments…7h 1mResolved
Sep 24, 2026500 errors while accessing projectsWe have received reports that some users are unable to access projects and are encountering 500 error messages. Our team is currently investigating the cause.6 minResolved
Sep 21, 2026Performance degradation in APAC/SingaporeWe're experiencing degraded package, artifact, and registry download speed in APAC/Singapore region due to elevated CDN/Cloudflare latency. More details in…8h 8mResolved
Sep 17, 2026Errors Opening RepositoriesWe're investigating reports of customers unable to open projects, receiving error 500 instead.17h 1mResolved
Sep 11, 2026Artifact upload failures and timeoutsWe’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…13h 31mResolved
Sep 10, 2026Security Policy Evaluation delays affecting MR approvalsWe 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.4h 44mResolved
Sep 9, 2026Delay in CI job processingWe'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…1h 38mResolved
Sep 8, 2026Some catalog agents are not workingStarting 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…1h 0mResolved
Sep 2, 2026Investigating delayed CI job pickup 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…48 minResolved
Aug 27, 2026HTTP 500 errors affecting GitLab.comThere are elevated HTTP 500 errors affecting users accessing their Pipelines. Our engineers are actively investigating the issue and working to restore normal service.3h 47mResolved
Aug 27, 2026Investigating GitLab.com Access IssuesWe are currently investigating reports of connectivity issues affecting some users accessing GitLab.com.2h 22mResolved
Aug 25, 2026General slowness and intermittent 502s on Gitlab.comWe are currently investigating reports of slowness and 502 errors. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/2278314h 12mResolved
Aug 24, 2026Investigating GitLab Agent for Kubernetes (KAS) Deployment FailuresWe are currently investigating reports of deployment failures affecting GitLab Agent for Kubernetes (KAS). Our team is actively looking into the root cause and will provide updates as the investigation progresses…1h 22mResolved
Aug 21, 2026403 errors across GitLab.comWe're monitoring an incident where 403s were seen across GitLab.com. The fix for this is already in place. More about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/2276226 minResolved
Aug 18, 2026500 errors when fetching commits on GitLab.comWe are investigating an issue causing a subset of requests to GitLab.com receiving 500 errors. We will provide updates as we learn more from our investigation. More information here…3h 11mResolved
Aug 17, 2026Project and Group Deletions DelayedWe are currently investigating an issue affecting project and group deletions on GitLab.com. Immediate and scheduled deletion of projects and groups may not complete as expected. Projects and groups that have been…6h 25mResolved
Aug 13, 2026Elevated queue times on saas-linux-medium-arm64 runnerWe are seeing a growing queue of pending jobs on the saas-linux-medium-arm64 hosted runner on GitLab.com. We are rolling out a mitigation. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/227023h 18mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next GitLab incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This GitLab Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before GitLab acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single GitLab outage in this window ran 20h 30m, against a mean recovery of 6h 17m. If you depend on GitLab in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.