Follow the recent outages and downtime for GitLab in the table below.
Start Time |
Type |
Length |
Message |
Details |
|||||
---|---|---|---|---|---|---|---|---|---|
April 18, 2024 01:44 UTC |
WARN |
about 1 hour |
500 errors during SAML sign in |
See more
|
|||||
April 18, 2024 00:14 UTC |
WARN |
about 2 hours |
500 errors during SAML sign in |
See more
|
|||||
April 17, 2024 16:59 UTC |
WARN |
about 7 hours |
Dependency Proxy 500 errors |
See more
|
|||||
April 11, 2024 12:05 UTC |
WARN |
about 2 hours |
Runners are not picking up jobs causing 500 errors |
See more
|
|||||
April 08, 2024 13:44 UTC |
DOWN |
about 2 hours |
Degraded performance causing intermittent 500 errors |
See more
|
|||||
2024-04-18 02:55:16 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2024-04-18 02:55:16 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2024-04-18 02:55:16 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2024-04-18 02:55:16 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2024-04-18 02:55:16 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more |
View details of the current GitLab status below.
Name |
Status |
Details |
---|---|---|
CI/CD - GitLab private runners |
UP | See more |
GitLab API |
UP | See more |
GitLab Background Processing |
UP | See more |
GitLab Canary |
UP | See more |
GitLab CI/CD - Hosted runners on Linux |
UP | See more |
GitLab CI/CD - Hosted runners on macOS |
UP | See more |
GitLab CI/CD - Hosted runners on Windows |
UP | See more |
GitLab Container Registry |
UP | See more |
GitLab Customers Portal |
UP | See more |
GitLab docs.gitlab.com |
UP | See more |
GitLab forum.gitlab.com |
UP | See more |
GitLab Git Operations |
UP | See more |
GitLab packages.gitlab.com |
UP | See more |
GitLab Pages |
UP | See more |
GitLab Product Analytics - Background processing (Beta) |
UP | See more |
GitLab Product Analytics - Collector (Beta) |
UP | See more |
GitLab Product Analytics - Configurator (Beta) |
UP | See more |
GitLab Product Analytics - Queries (Beta) |
UP | See more |
GitLab Support Services |
UP | See more |
GitLab version.gitlab.com |
UP | See more |
GitLab Website |
UP | See more |
SAML SSO - GitLab SaaS |
UP | See more |
GitLab status, last 24 hours:
Up: 14 hours
Warn: 10 hours
Down: 0 minutes
Maintenance: 0 minutes
We've been monitoring GitLab outages since December 22, 2016.
Here's the history of service outages we've observed from the GitLab Status Page:
GitLab is a DevOps solution that StatusGator has been monitoring since December 2016. Over the past over 7 years, we have collected data on on more than 2,034 outages that affected GitLab users. When GitLab publishes downtime on their status page, they do so across 23 components and 4 groups using 4 different statuses: up, warn, down, and maintenance which we use to provide granular uptime metrics and notifications.
More than 600 StatusGator users monitor GitLab to get notified when it's down, is under maintenance, or has an outage. This makes it one of the most popular devops services monitored on our platform. We've sent more than 35,500 notifications to our users about GitLab incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.
If GitLab is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.
Warn notifications are used when GitLab is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.
GitLab posts separate notifications for planned maintenance work. StatusGator will notify subscribers when GitLab enters a pre-planned maintenance window, keeping you up to date.
GitLab does not publish a feed of proactive maintenance events on their status page at this time. If they do, be sure to let us know and we'll aggregate GitLab maintenance events into your unified calendar.
When GitLab posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.
When GitLab has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.
Because GitLab has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.
Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!
Are you experiencing issues with GitLab? Sign up to receive notifications when GitLab publishes outages.
GitLab Down or not working? Never be taken by surprise again.
StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,580 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.
Looking for recent downtime and outages of GitLab?
Sign up for StatusGator and see all historical information about GitLab outages and performance issues. Get free, instant notifications when GitLab goes down.