Skip to content
PulseWatchOUTAGE.INTEL
GitLab logo

Productivity

Is GitLab down right now?

NormalOfficial status last polled Oct 8, 2026 12:55 UTCgitlab.comOfficial status page

DevOps platform for the full software lifecycle.

Are you on the GitLab team and see something inaccurate? Report it to us. We respond within one business day.

Is GitLab down right now?

No. GitLab has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 8, 2026 13:01 UTC

Normal

GitLab is operating normally

As of Oct 8, 2026 13:01 UTC

No elevated reports in the last 15 minutes. Baseline 4 reports/hour.

Reports 24h

0

Last incident

Oct 7, 2026 19:05 UTC

Trend

0/15m

Baseline

4/hr

Observed health

100/100

1 of 1 assessed samples succeeded within their latency target.

4/4 responses validated in the last 15 minutes. 3 successful samples have no qualified latency target.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for GitLab.

10

Incident days

20

No recorded incident

79h 50m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for GitLab. Hover a day for detail.

Sep 9Sep 14Sep 19Sep 24Sep 29Oct 401234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

10

Days with incidents

2 incidents

Busiest day

79h 50m

Recorded duration

Report volume

0 reports in last 24H

01:00 PM04:30 PM08:00 PM11:30 PM03:00 AM06:30 AM10:00 AM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

GitLab: vendor-reported incident on October 7 (tracked 2h 6m)

Oct 7, 04:59 PM → Oct 7, 07:05 PM · 2h 6m · medium

GitLab reported an incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked this incident for 2 hours and 6 minutes, closing it on 2026-10-07T19:05:51.937Z.

Duration
2h 6m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, and therefore cannot describe what users experienced. The incident is known from GitLab's own status page.

Incident timeline

  1. Oct 7, 04:59 PM

    The vendor reported an incident on its own status page; PulseWatch began tracking it

  2. Oct 7, 04:59 PM

    Status updated: possible issue

  3. Oct 7, 07:05 PM

    PulseWatch closed the incident

Official updates

  1. Oct 7, 04:59 PM

    GitLab reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.

Reliability

Detected by PulseWatch

30-day uptime

88.9%

90-day uptime

96.0%

Calculated from GitLab's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other productivity services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedMedium

GitLab: the vendor reports degraded performance on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/7/2026, 4:59:38 PM · 2h 6m

04:59 PM07:05 PM
Detection10/7/2026, 4:59:38 PM · 20h ago

Detected — medium severity

GitLab: the vendor reports degraded performance on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

GitLab: the vendor reports degraded performance on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/1/2026, 6:35:52 PM · 4h 19m

06:35 PM10:55 PM
Detection10/1/2026, 6:35:52 PM · 6d ago

Detected — medium severity

GitLab: the vendor reports degraded performance on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

GitLab: the vendor reports a partial outage on its own status page. Single origin, not independently confirmed. Users who watch GitLab or have an alert rule on it can be alerted, labelled vendor-reported.

10/1/2026, 12:45:31 AM · 11h 40m

12:45 AM12:25 PM
Detection10/1/2026, 12:45:31 AM · 7d ago

Detected — medium severity

GitLab: the vendor reports a partial outage on its own status page. Single origin, not independently confirmed. Users who watch GitLab or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedMedium

GitLab: the vendor reports degraded performance on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/29/2026, 8:46:50 PM · 15h 54m

08:46 PM12:41 PM
Detection9/29/2026, 8:46:50 PM · 8d ago

Detected — medium severity

GitLab: the vendor reports degraded performance on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

GitLab: the vendor reports a partial outage on its own status page. Single origin, not independently confirmed. Users who watch GitLab or have an alert rule on it can be alerted, labelled vendor-reported.

9/25/2026, 6:55:46 PM · 5h 25m

06:55 PM12:21 AM
Detection9/25/2026, 6:55:46 PM · 12d ago

Detected — medium severity

GitLab: the vendor reports a partial outage on its own status page. Single origin, not independently confirmed. Users who watch GitLab or have an alert rule on it can be alerted, labelled vendor-reported.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment GitLab enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
4
Open threshold
3x

Official site

gitlab.com