by HonkWatch

Is GitLab down in eSwatini?

GitLab problems reported by people in eSwatini. Check the last 24 hours and tell others what isn't working for you.

Having trouble with GitLab?

Tell others what's happening. No account needed.

What isn't working?

One report per service per hour. Reports are anonymous; your IP address is not stored in the report.

Reports from people in eSwatini

Last 24 hours · eSwatini · times in UTC

0 reports

No community reports in the last 24 hours from eSwatini. This does not prove the service is working. If you have a problem, report it here.

024 18:0000:0006:0012:00

Reports per 15 minutes. A flat chart means no reports, not proof that everything works.

Compare worldwide reports · Other services in eSwatini

Provider updates and website checks — worldwide

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

No. GitLab is working. Updated 5 Nov, 15:38 UTC, just now · Official status page Last problem: 3 Nov, 17:24 UTC, partial outage for 1 h 31 min (1 of 24 parts affected: CI/CD / Google Compute Engine).

Having trouble with GitLab?

  1. Compare reports from eSwatini 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.

Last 9030 days

91.84% 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 86 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,802 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 0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed1% of 105 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed2% of 107 checks failed1% of 106 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 checks failed0% of 102 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 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 98 checks failed0% of 111 checks failed0% of 105 checks failed0% of 105 checks failed0% of 102 checks failed0% of 108 checks failed0% of 105 checks failed0% of 105 checks failed0% of 95 checks failed0% of 115 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 84 checks failed0% of 11 checks failed

Our own checks of gitlab.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Seoul: loaded in 487 ms Melbourne: loaded in 553 ms Johannesburg: loaded in 933 ms Delhi: loaded in 516 ms Singapore: loaded in 440 ms Madrid: loaded in 320 ms Dallas: loaded in 346 ms New York: loaded in 319 ms Doha: loaded in 1194 ms Portsmouth: loaded in 461 ms Frankfurt: loaded in 377 ms Atlanta: loaded in 212 ms London: loaded in 355 ms Tokyo: loaded in 3767 ms Tel Aviv: loaded in 457 ms Hamina: loaded in 414 ms Warsaw: loaded in 354 ms Querétaro: loaded in 289 ms Los Angeles: loaded in 470 ms Sydney: loaded in 460 ms Cape Town: loaded in 457 ms Toronto: loaded in 330 ms St. Louis: loaded in 492 ms Mumbai: loaded in 553 ms Osaka: loaded in 386 ms Port Louis: loaded in 862 ms Hong Kong: loaded in 779 ms Bangalore: loaded in 589 ms New Jersey: loaded in 1096 ms Jakarta: loaded in 448 ms Lauterbourg: loaded in 1269 ms Amsterdam: loaded in 374 ms Seattle: loaded in 318 ms São Paulo: loaded in 546 ms Santiago: loaded in 321 ms
  • SeoulReachable487 ms, just now
  • MelbourneReachable553 ms, just now
  • JohannesburgReachable933 ms, just now
  • DelhiReachable516 ms, just now
  • SingaporeReachable440 ms, just now
  • MadridReachable320 ms, just now
  • DallasReachable346 ms, just now
  • New YorkReachable319 ms, just now
  • DohaReachable1194 ms, 1 min ago
  • PortsmouthReachable461 ms, 1 min ago
  • FrankfurtReachable377 ms, 1 min ago
  • AtlantaReachable212 ms, 1 min ago
  • LondonReachable355 ms, 1 min ago
  • TokyoReachable3767 ms, 2 min ago
  • Tel AvivReachable457 ms, 2 min ago
  • HaminaReachable414 ms, 2 min ago
  • WarsawReachable354 ms, 2 min ago
  • QuerétaroReachable289 ms, 3 min ago
  • Los AngelesReachable470 ms, 3 min ago
  • SydneyReachable460 ms, 3 min ago
  • Cape TownReachable457 ms, 3 min ago
  • TorontoReachable330 ms, 3 min ago
  • St. LouisReachable492 ms, 3 min ago
  • MumbaiReachable553 ms, 4 min ago
  • OsakaReachable386 ms, 4 min ago
  • Port LouisReachable862 ms, 4 min ago
  • Hong KongReachable779 ms, 4 min ago
  • BangaloreReachable589 ms, 5 min ago
  • New JerseyReachable1096 ms, 5 min ago
  • JakartaReachable448 ms, 5 min ago
  • LauterbourgReachable1269 ms, 5 min ago
  • AmsterdamReachable374 ms, 5 min ago
  • SeattleReachable318 ms, 5 min ago
  • São PauloReachable546 ms, 5 min ago
  • SantiagoReachable321 ms, 14 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.

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

Alert me when GitLab is down

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

Start free Log in

More in Developer tools

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.

Official status from the GitLab status page.

← All services