# GitLab: GitLab.com sign in and deployments affected by upstream incident

- Impact (vendor’s label): none
- Status: resolved
- Started: 2025-11-18 12:43 UTC · Resolved: 2025-11-18 19:12 UTC · Duration: 6.5 h
- Updates: 4 · Affected components: Website
- [Vendor status page: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/691c69e0e55a8105f149573c](https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/691c69e0e55a8105f149573c)
- [Company: GitLab](https://rewindex.com/company/gitlab.md)

## Timeline of updates

- **monitoring** 2025-11-18 12:43 UTC: Due to an ongoing Cloudflare service incident, GitLab.com users had experienced intermittent sign-in and deployment issues. While our monitoring shows everything is back to normal, we continue monitoring the situation and will update you once Cloudflare confirms full resolution.
- **monitoring** 2025-11-18 13:52 UTC: Cloudflare has identified the cause of the incident and is implementing a fix. We're monitoring for full resolution and will update as soon as the fix progresses.
- **monitoring** 2025-11-18 16:16 UTC: GitLab services remain fully operational. We will continue to monitor the incident until Cloudflare finishes recovery.
- **resolved** 2025-11-18 19:12 UTC: The Cloudflare service incident affecting GitLab.com has been fully resolved. GitLab.com services are fully operational.


---
Canonical: https://rewindex.com/company/gitlab/incidents/691c69e0e55a8105f149573c · Markdown: https://rewindex.com/company/gitlab/incidents/691c69e0e55a8105f149573c.md · JSON: https://rewindex.com/api/v1/companies/gitlab/incidents/691c69e0e55a8105f149573c · Generated 2026-10-18T10:27:05.526Z