Is GitLab down right now?
Real-time GitLab.com status pulled from status.gitlab.com. Self-managed GitLab instances are not affected by GitLab.com outages — this page tracks the SaaS only. We monitor the web UI, Git operations, CI/CD pipelines, the container registry, and Pages.
Major outage: AWS
GitLab
Unable to verifySource hosting, CI/CD pipelines, registry.
Status from status.gitlab.com · last fetched 4s ago
Developer Platforms
Upstream returned 404
Atlassian source hosting and Pipelines.
Container image registry and Docker Desktop.
Source hosting, Actions, Pages, Packages, Copilot.
macOS / Linux package manager (uses GitHub).
JavaScript registry, install API, web app.
Python Package Index — pip install backend.
AI / ML APIs
Some users unable to sign up with Apple on the Claude iOS app — started 1 day ago
Delayed Costs Data in the Compliance API — started 2 days ago
Upstream returned invalid JSON
Upstream returned invalid JSON
AI code editor — chat, tab, composer.
AI pair programmer — completions, chat, agents.
Gemini API, Vertex AI, AI Studio.
Cloud / Hosting
Service disruption: Increased Error Rates — started 61 days ago
Changes to Cloudflare Workers are not producing Event Subscription events — started 5 days ago
Upstream returned 404
Upstream returned invalid JSON
Droplets, App Platform, managed databases.
Global app servers, Postgres, volumes.
Compute, Storage, BigQuery, Cloud Run.
Azure VMs, App Service, AKS, Azure SQL.
Static + Jamstack hosting, Functions, Forms.
Web services, cron, Postgres, Redis.
Next.js hosting, Edge, Serverless functions.
Databases / Data
Upstream returned 404
Upstream returned invalid JSON
Upstream returned invalid JSON
Impaired Cluster operations in AWS me-central-1 and AWS me-south-1 — started 73 days ago
Serverless MySQL, Vitess-backed.
Postgres, auth, storage, realtime, edge fns.
Payments / Infra
SMS Delivery Receipt Failures from Twilio to Claro Costa Rica — started 3 days ago
SMS Delivery Receipt Failures from Twilio to Claro Costa Rica — started 3 days ago
Upstream returned invalid JSON
Upstream returned 404
Upstream returned 404
Developer-first transactional email API.
Auth / Identity
Communication
Monitoring / Dev Tools
Upstream returned 403
Upstream returned invalid JSON
Upstream returned invalid JSON
Collaborative design, FigJam, Dev Mode.
Feature flags, experiments, releases.
Error monitoring, performance, replays.
DevZone aggregates publicly available status data and refreshes every 30 seconds. Status indicators reflect each provider’s own machine-readable feed; for incident details and authoritative information, always consult the official status page linked on each card.
Quick facts about GitLab
- GitLab publishes status at status.gitlab.com using Atlassian Statuspage.
- Self-hosted (CE/EE) GitLab is unaffected by GitLab.com outages.
- GitLab’s shared CI runners are a frequent source of partial degradation.
- The registry, Pages, and the API are reported as separate components.
Frequently asked questions
Why are my GitLab CI jobs stuck pending?
Most "stuck pending" reports during a GitLab.com outage are runner-availability issues — shared SaaS runners are at capacity or unavailable. The dashboard above shows the CI runner component status. If it’s green and your jobs still hang, check that your `.gitlab-ci.yml` doesn’t have an unmet `tags:` constraint.
Is self-hosted GitLab affected when GitLab.com is down?
No. Self-hosted CE and EE instances run independently. The exception is if you depend on container images pulled from registry.gitlab.com — those would be unreachable during a registry outage.
Where can I report a GitLab.com outage?
Public outages are tracked at status.gitlab.com. Customers on paid plans should use https://about.gitlab.com/support/ for escalation.
Does GitLab have a status API?
Yes — https://status.gitlab.com/api/v2/summary.json. The same Statuspage schema as GitHub, OpenAI, and dozens of others.
How do I switch CI/CD to my own runners during a GitLab.com runner outage?
Register a self-managed runner and tag it (e.g., `tags: ["fallback"]`). Update your pipeline jobs to specify that tag. This gives you a fallback path that doesn’t depend on shared SaaS capacity.