Live / Providers / GitLab
GitLab
gitlab.comNo open incidents
SaaS & business software · SquidGrid tracks GitLab’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.
Public — what GitLab is reporting
Current & recent incidents
ResolvedSecurity Reports not loading for some users
2026-09-25 18:39 UTC
Resolved503s on GitLab.com
2026-09-24 23:02 UTC
Resolved500 errors while accessing projects
2026-09-24 13:48 UTC
Resolved500 errors while accessing projects
2026-09-24 13:43 UTC
ResolvedPerformance degradation in APAC/Singapore
2026-09-21 12:10 UTC
ResolvedErrors Opening Repositories
2026-09-17 20:44 UTC
ResolvedArtifact upload failures and timeouts
2026-09-11 05:50 UTC
ResolvedSecurity Policy Evaluation delays affecting MR approvals
2026-09-10 15:24 UTC
With SquidGrid — where the route changes
Independent path health
A status page tells you what GitLab has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.
GitLab runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of GitLab is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.
🔒 Sign in to see
Incident track record: 90-day trend, median and worst time to fix
What tends to break, from their own incident write-ups
Recent public reports of problems with this service
Included with any paid plan.
See the full report →