outages.live
Live

GitLab

GitLab is operational

Checked 58 s ago Operational

History

90 days agoToday

Incidents in 90 days

0

Days with an incident

0

Median duration

No data

Longest incident

No data

Components

23
Website Operational
90 days agoNo incidentsToday
API Operational
90 days agoNo incidentsToday
Git Operations Operational
90 days agoNo incidentsToday
Package Registry Operational
90 days agoNo incidentsToday
Container Registry Operational
90 days agoNo incidentsToday
GitLab Pages Operational
90 days agoNo incidentsToday
CI/CD Operational
90 days agoNo incidentsToday
CI/CD - Hosted runners on Linux Operational
90 days agoNo incidentsToday
CI/CD - Hosted runners on Windows Operational
90 days agoNo incidentsToday
CI/CD - Hosted runners on macOS Operational
90 days agoNo incidentsToday
CI/CD - Hosted runners for GitLab community contributions Operational
90 days agoNo incidentsToday
CI/CD - Self-managed runners Operational
90 days agoNo incidentsToday
SAML SSO - GitLab SaaS Operational
90 days agoNo incidentsToday
Background Processing Operational
90 days agoNo incidentsToday
GitLab Customers Portal Operational
90 days agoNo incidentsToday
Support Services Operational
90 days agoNo incidentsToday
packages.gitlab.com Operational
90 days agoNo incidentsToday
version.gitlab.com Operational
90 days agoNo incidentsToday
forum.gitlab.com Operational
90 days agoNo incidentsToday
docs.gitlab.com Operational
90 days agoNo incidentsToday
Canary Operational
90 days agoNo incidentsToday
GitLab Duo Operational
90 days agoNo incidentsToday
GitLab agent server for Kubernetes Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

Follow GitLab

Your coding agent knows when GitLab is down, and tells you when a failure is theirs, not yours. You can also get GitLab incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "gitlab" and tell me if GitLab has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=gitlab
Slack
/feed subscribe https://outages.live/feed.xml?providers=gitlab

Go from tracking outages to fixing production issues with Polylane.

Try Polylane