by HonkWatch

Is GitLab down in Montserrat?

No problems reported with GitLab right now

Montserrat No reports in the last hour checked 2 min ago
GitLab reports no current incident. Updated 6 Nov, 16:18 UTC, 2 min ago · Official status page
Report a problemFollow community reports
Change country

Reports from people in Montserrat

Last 24 hours · Montserrat · times in UTC

0 reports

No community reports in the last 24 hours from Montserrat. Having trouble? Add your report.

024 18:0000:0006:0012:00

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Report totals as of 6 Nov, 16:21 UTC

Report a problem with GitLab

Having trouble? Tap what isn't working. No account needed.

What isn't working?

Anonymous · one report per service per hour. This adds your experience to the chart, without contacting the provider or subscribing you to alerts.

Compare worldwide reports · Other services in Montserrat

Monitor the provider status with HonkWatch

Get monitoring alerts for GitLab

HonkWatch watches the GitLab status page for you and alerts you by email, Slack, Discord or Telegram when it reports a problem.

Free account required. GitLab is selected on the next page. Review the monitor and choose where alerts go. Community reports do not trigger these monitoring alerts.

Start free Log in

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Montserrat. The report chart above is filtered to Montserrat.

Our own checks of gitlab.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Toronto: loaded in 382 ms Delhi: loaded in 493 ms Doha: loaded in 1167 ms Johannesburg: loaded in 481 ms Los Angeles: loaded in 420 ms New Jersey: loaded in 1348 ms Singapore: loaded in 522 ms Port Louis: loaded in 523 ms Tel Aviv: loaded in 485 ms Santiago: loaded in 382 ms Amsterdam: loaded in 386 ms Portsmouth: loaded in 389 ms Seoul: loaded in 401 ms Frankfurt: loaded in 348 ms Melbourne: loaded in 564 ms Lauterbourg: loaded in 363 ms St. Louis: loaded in 333 ms Dallas: loaded in 355 ms Cape Town: loaded in 430 ms Seattle: loaded in 267 ms Hamina: loaded in 436 ms Madrid: loaded in 348 ms Mumbai: loaded in 556 ms Hong Kong: loaded in 462 ms Osaka: loaded in 372 ms London: loaded in 325 ms Sydney: loaded in 686 ms Jakarta: loaded in 467 ms New York: loaded in 345 ms Atlanta: loaded in 234 ms São Paulo: loaded in 364 ms Tokyo: loaded in 2484 ms Warsaw: loaded in 320 ms Querétaro: loaded in 251 ms Bangalore: loaded in 597 ms
  • TorontoReachable382 ms, just now
  • DelhiReachable493 ms, just now
  • DohaReachable1167 ms, just now
  • JohannesburgReachable481 ms, just now
  • Los AngelesReachable420 ms, 1 min ago
  • New JerseyReachable1348 ms, 1 min ago
  • SingaporeReachable522 ms, 1 min ago
  • Port LouisReachable523 ms, 1 min ago
  • Tel AvivReachable485 ms, 1 min ago
  • SantiagoReachable382 ms, 1 min ago
  • AmsterdamReachable386 ms, 1 min ago
  • PortsmouthReachable389 ms, 1 min ago
  • SeoulReachable401 ms, 1 min ago
  • FrankfurtReachable348 ms, 2 min ago
  • MelbourneReachable564 ms, 2 min ago
  • LauterbourgReachable363 ms, 2 min ago
  • St. LouisReachable333 ms, 2 min ago
  • DallasReachable355 ms, 2 min ago
  • Cape TownReachable430 ms, 2 min ago
  • SeattleReachable267 ms, 2 min ago
  • HaminaReachable436 ms, 2 min ago
  • MadridReachable348 ms, 2 min ago
  • MumbaiReachable556 ms, 2 min ago
  • Hong KongReachable462 ms, 2 min ago
  • OsakaReachable372 ms, 2 min ago
  • LondonReachable325 ms, 2 min ago
  • SydneyReachable686 ms, 2 min ago
  • JakartaReachable467 ms, 2 min ago
  • New YorkReachable345 ms, 2 min ago
  • AtlantaReachable234 ms, 2 min ago
  • São PauloReachable364 ms, 3 min ago
  • TokyoReachable2484 ms, 3 min ago
  • WarsawReachable320 ms, 3 min ago
  • QuerétaroReachable251 ms, 3 min ago
  • BangaloreReachable597 ms, 7 min ago

This is separate from the status page: we request gitlab.com and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of GitLab

Website

  • Google Compute EngineOperational

API

  • Google Compute EngineOperational

Git Operations

  • Google Compute EngineOperational

Package Registry

  • Google Compute EngineOperational

Container Registry

  • Google Compute EngineOperational

GitLab Pages

  • Google Compute EngineOperational

CI/CD

  • Google Compute EngineOperational

CI/CD - Hosted runners on Linux

  • Google Compute EngineOperational

CI/CD - Hosted runners on Windows

  • Google Compute EngineOperational

CI/CD - Hosted runners on macOS

  • Google Compute EngineOperational
  • AWSOperational

CI/CD - Hosted runners for GitLab community contributions

  • Google Compute EngineOperational

CI/CD - Self-managed runners

  • Self-Managed Runner ConnectivityOperational

SAML SSO - GitLab SaaS

  • Google Compute EngineOperational

Background Processing

  • Google Compute EngineOperational

GitLab Customers Portal

  • Google Compute EngineOperational

Support Services

  • ZendeskOperational

packages.gitlab.com

  • AWSOperational

version.gitlab.com

  • AWSOperational

forum.gitlab.com

  • Digital OceanOperational

docs.gitlab.com

  • Google Compute EngineOperational

Canary

  • Google Compute EngineOperational

GitLab Duo

  • Google Compute EngineOperational

GitLab agent server for Kubernetes

  • Google Compute EngineOperational

Incidents and maintenance

No open incidents or planned maintenance.

Outage history

Last problem: 3 Nov, 17:24 UTC, partial outage for 1 h 31 min (1 of 24 parts affected: CI/CD / Google Compute Engine).

Last 9030 days

93.83% of the time without a reported outage, since 2 Nov

Of the last 90 days, 1 had a partial or major outage, 0 had maintenance only and 85 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Last 24 hours

Every 15 minutes, hours in UTC

Bars: the share of our own checks of gitlab.com that failed (9,599 checks). Its status page reported no problem in this time. Community reports appear separately above, alongside our checks and provider updates.

0%5%10% 18:0000:0006:0012:00 1% of 100 checks failed0% of 112 checks failed0% of 102 checks failed0% of 108 checks failed0% of 105 checks failed0% of 105 checks failed0% of 83 checks failed0% of 108 checks failed0% of 112 checks failed0% of 96 checks failed0% of 95 checks failed0% of 93 checks failed0% of 100 checks failed0% of 103 checks failed0% of 95 checks failed0% of 99 checks failed0% of 110 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed1% of 106 checks failed0% of 105 checks failed0% of 105 checks failed0% of 104 checks failed0% of 103 checks failed0% of 106 checks failed0% of 107 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 104 checks failed0% of 106 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 103 checks failed0% of 107 checks failed0% of 105 checks failed1% of 108 checks failed0% of 105 checks failed0% of 105 checks failed0% of 99 checks failed0% of 104 checks failed0% of 92 checks failed0% of 110 checks failed0% of 96 checks failed0% of 105 checks failed0% of 101 checks failed0% of 80 checks failed0% of 95 checks failed0% of 113 checks failed0% of 84 checks failed0% of 114 checks failed0% of 100 checks failed0% of 90 checks failed0% of 79 checks failed0% of 98 checks failed0% of 105 checks failed0% of 99 checks failed0% of 82 checks failed0% of 76 checks failed0% of 98 checks failed0% of 90 checks failed0% of 97 checks failed0% of 73 checks failed0% of 71 checks failed0% of 92 checks failed0% of 72 checks failed0% of 89 checks failed0% of 15 checks failed

Recent problems

3 Nov, 17:24 UTCPartial outage1 h 31 min1 of 24 parts affected: CI/CD / Google Compute Engine
3 Nov, 05:09 UTCPartial outage4 h 43 min1 of 24 parts affected: CI/CD / Google Compute Engine
What can I try?

Having trouble with GitLab?

  1. Compare reports from Montserrat and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is GitLab down, or is it just me?

The GitLab status page reports no problem and our own checks reach gitlab.com. This does not rule out problems with sign-in, payments, an app or a local network. Check the community reports above and report your experience.

How do we know?

We read the official GitLab status page and load gitlab.com from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 2.5 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

More in Developer tools

See the live outage feed for Montserrat · Find another service