GitLab
Components.
24 components in 1 group · last 30 days
- WebsiteOperational
- APIOperational
- Git OperationsOperational
- Package RegistryOperational
- Container RegistryOperational
- GitLab PagesOperational
- CI/CDOperational
- CI/CD - Hosted runners on LinuxOperational
- CI/CD - Hosted runners on WindowsOperational
- CI/CD - Hosted runners for GitLab community contributionsOperational
- CI/CD - Self-managed runnersOperational
- SAML SSO - GitLab SaaSOperational
- Background ProcessingOperational
- GitLab Customers PortalOperational
- Support ServicesOperational
- packages.gitlab.comOperational
- version.gitlab.comOperational
- forum.gitlab.comOperational
- docs.gitlab.comOperational
- CanaryOperational
- GitLab DuoOperational
- GitLab agent server for KubernetesOperational
History.
A bar takes the worst status GitLab reported in it
20 incidents in 90 days · tracked since 25 Sept
24 AugNow
OperationalDegraded or partial outageMajor outageMaintenanceShort or regional issueNo reading
Past incidents.
20 in the last 90 days, as GitLab posted them
About this data.
- Source
status.gitlab.com(opens in a new tab), the vendor’s own status page. Every update links back to it.
- How often
Read every few minutes. Last change .
- Without a reading
We show Status unknown and leave the day grey. Never a green guess.
- Same category
Follow just the parts you use.
Pick the GitLab components your product depends on, and hear about incidents that touch them.
Get alertsVendor alerts inform you. They never page anyone.