by HonkWatch

Is GitLab down in Namibia?

No problems reported with GitLab right now

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

Reports from people in Namibia

Last 24 hours · Namibia · times in UTC

0 reports

No community reports in the last 24 hours from Namibia. 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:17 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 Namibia

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 Namibia. The report chart above is filtered to Namibia.

Our own checks of gitlab.com

Every 5 minutes, from our probes

Our checks from 34 cities: all fine.

Cape Town: loaded in 538 ms Dallas: loaded in 346 ms New Jersey: loaded in 3217 ms Madrid: loaded in 328 ms Singapore: loaded in 510 ms St. Louis: loaded in 530 ms Querétaro: loaded in 250 ms Tokyo: loaded in 1495 ms Warsaw: loaded in 333 ms São Paulo: loaded in 340 ms Portsmouth: loaded in 415 ms Doha: loaded in 950 ms Seoul: loaded in 469 ms Port Louis: loaded in 526 ms Frankfurt: loaded in 370 ms Toronto: loaded in 330 ms Lauterbourg: loaded in 445 ms Amsterdam: loaded in 380 ms Delhi: loaded in 491 ms Hamina: loaded in 681 ms Osaka: loaded in 364 ms Bangalore: loaded in 597 ms Mumbai: loaded in 532 ms Atlanta: loaded in 250 ms Santiago: loaded in 320 ms Los Angeles: loaded in 424 ms Johannesburg: loaded in 453 ms Tel Aviv: loaded in 374 ms Melbourne: loaded in 538 ms Sydney: loaded in 504 ms New York: loaded in 324 ms Jakarta: loaded in 453 ms London: loaded in 402 ms Hong Kong: loaded in 519 ms
  • Cape TownReachable538 ms, just now
  • DallasReachable346 ms, just now
  • New JerseyReachable3217 ms, just now
  • MadridReachable328 ms, 1 min ago
  • SingaporeReachable510 ms, 1 min ago
  • St. LouisReachable530 ms, 1 min ago
  • QuerétaroReachable250 ms, 1 min ago
  • TokyoReachable1495 ms, 1 min ago
  • WarsawReachable333 ms, 1 min ago
  • São PauloReachable340 ms, 2 min ago
  • PortsmouthReachable415 ms, 2 min ago
  • DohaReachable950 ms, 2 min ago
  • SeoulReachable469 ms, 2 min ago
  • Port LouisReachable526 ms, 2 min ago
  • FrankfurtReachable370 ms, 2 min ago
  • TorontoReachable330 ms, 2 min ago
  • LauterbourgReachable445 ms, 2 min ago
  • AmsterdamReachable380 ms, 2 min ago
  • DelhiReachable491 ms, 2 min ago
  • HaminaReachable681 ms, 3 min ago
  • OsakaReachable364 ms, 3 min ago
  • BangaloreReachable597 ms, 3 min ago
  • MumbaiReachable532 ms, 3 min ago
  • AtlantaReachable250 ms, 3 min ago
  • SantiagoReachable320 ms, 3 min ago
  • Los AngelesReachable424 ms, 3 min ago
  • JohannesburgReachable453 ms, 3 min ago
  • Tel AvivReachable374 ms, 4 min ago
  • MelbourneReachable538 ms, 4 min ago
  • SydneyReachable504 ms, 4 min ago
  • New YorkReachable324 ms, 4 min ago
  • JakartaReachable453 ms, 6 min ago
  • LondonReachable402 ms, 6 min ago
  • Hong KongReachable519 ms, 8 min ago
  • SeattleReachable406 ms, 16 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,596 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 12 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 Namibia 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 Namibia · Find another service