Create an internal status page, receive real-time notifications, and integrate vendor outages with your existing tools. Keep your team informed and reduce the cost of cloud vendor downtime.
No comments yet
Number of Incidents
0 issues
Last incident
31 days ago
Major Resolved
The Customers Portal (customers.gitlab.com) is in maintenance mode due to a 3rd-party API being down. The billing pages in GitLab.com may be affected.
Major Resolved
GitLab.com is currently experiencing connectivity issues due to a high error rate. Our infrastructure team is investigating. Issue: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/18490
Major Resolved
Some requests are slow or timing out due to DB saturation. We are investigating. Please see [this issue](https://gitlab.com/gitlab-com/gl-infra/production/-/issues/18435) for further details.
IsDown aggregates and normalizes all your vendors' status pages. Create a dashboard & get outages alerts in Slack, PagerDuty, Datadog, and more.
IsDown offers an easy way to monitor GitLab with maximum flexibility
IsDown monitors GitLab Customers Portal for major outages. A major outage is when GitLab Customers Portal experiences a critical issue that severely affects one or more services/regions. When GitLab marks an incident as a major outage, IsDown updates its internal status, the customer status page and dashboard. Depending on the customer settings, IsDown will also send notifications.
IsDown monitors GitLab status page for minor outages. A minor outage is when GitLab Customers Portal experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. When a minor outage occurs, IsDown updates its internal status and shares that information on the customer status page. Depending on the customer settings, IsDown will also send notifications.
IsDown collects all information from the outages published in GitLab status page to provide the most accurate information. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.
IsDown monitors GitLab and all their 17 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages. This way you avoid alert fatigue in your team.
GitLab and other vendors don’t always report outages on time. Our crowdsourced status platform helps you stay ahead of outages. Users report issues and outages, sharing details on what problems they are facing. We use that info to provide early signs of outages. This way, even without an official update, you can stay ahead of possible problems.
GitLab is currently operational. In the last 24 hours, there were 0 outages reported. IsDown continuously monitors the GitLab status page, looking for the latest outages and issues affecting customers. Check all recent outages in the section 'Latest GitLab Customers Portal outages, issues and problems' at the top of the page.
GitLab Customers Portal last outage was on September 04, 2024 with the title "Customers Portal is down (customers.gitlab.com)"
IsDown and DownDetector help users determine if a service is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information. The integration allows us to provide more details about the outage, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.
How much time you'll save your team, by having the outages information close to them?
14-day free trial · No credit card required · Cancel anytime