Git support, 24/7

Git Support for Git Servers, Self-Managed GitLab, Gitea and CI Runners

AceMQ provides Git support 24/7 for Git servers, self-managed GitLab, Gitea and the CI runners that clone from them, beside your own platform team. Most calls start with one of three problems: clones and fetches that crawl, a GitLab upgrade that stalled between required stops, or a server that slows down when pipelines start.

24/7 across Americas, EMEA and APAC, with response targets from 15 minutes, by plan, and a written root cause analysis on every P1.

Support quotes answered within 1 hour, by a senior engineer.

min fastest response target, by plan
15
across Americas, EMEA, APAC
24/7
hour quote reply time
1
support tiers, reactive to managed
4

Planning a build, upgrade or migration instead? See AceMQ Git consulting and services.

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

Git problems we fix every week

Clone, upgrade and load problems on Git platforms, each paired with the Git or GitLab output an engineer reads first.

Common Git production problems and how AceMQ resolves them
Symptom you're seeingWhat we check firstTypical resolution
Clones and fetches slow or timing outgit count-objects -vH for loose objects and pack count, GIT_TRACE_PERFORMANCE on the slow command, and whether CI clones the full history; commit-graph and multi-pack-index state on the server copy.Schedule git maintenance, move CI to shallow or partial clones, repack the repository, and size the server for fetch bursts.
A push is rejected for file size or by a hookThe file size and path, the platform's limits for the repository, the server-side hook output, and whether Git LFS is configured for that path.Track the file with Git LFS, or remove it from the commit; plan a history rewrite only if the file is already in history.
A GitLab upgrade stalled or failed between required stopsThe running version against the required stops from GitLab's upgrade path tool, whether background migrations have finished, and the package log for the failing step.Let the migrations finish, retry at the stop, and restore from the backup taken before the stop if it cannot continue.
The server slows when CI pipelines startHow many clone and fetch jobs start together, CPU and memory on the Git storage service (Gitaly on GitLab), and runner concurrency.Move jobs to shallow clones, cap runner concurrency, cache the repository on the runner, and add capacity where the numbers justify it.
Pipelines fail after a Git version changed on a runner imageThe Git version in the runner image against the one the pipeline settings assume, GIT_DEPTH and GIT_STRATEGY, and shallow depths too small for a merge-base or git describe.Align the image and the clone settings, and raise the depth only for the jobs that need history.
Missing objects or a repository that fails git fsckgit fsck output, the last good backup and any mirror, and which refs point at the missing objects.Restore the objects from a mirror or backup, verify with git fsck, and only then prune.
A credential or token was committedWhere it appears (git log -S or a secret scanner), who has cloned since, and what the credential can reach.Rotate it first, then decide with you whether a history rewrite is needed, knowing that other clones keep the old objects.

Every P1 comes with a written cause naming the repository, version or service involved.

Clones crawling or an upgrade stuck between stops? Ask for a quote and a Git engineer replies within the hour.

Contact Us

Deployment coverage

Which Git platforms does AceMQ support, and who covers what?

DeploymentWhat AceMQ coversWhat the vendor or project coversExcluded
Self-managed GitLab (Linux package, containers or Helm chart)24/7 incident response, upgrade routes across required stops, backup and restore rehearsal, storage and load review, written RCA on P1sGitLab supplies releases, patches and defect fixes for its softwareA patched GitLab build
Gitea and other self-managed Git serversOperations, upgrades, backups, repository migration and performanceThe project supplies releases and fixesChanges to the project's code
Plain Git servers over SSH or HTTPRepository maintenance, hooks, permissions, backups and performanceThe Git project supplies releases and fixesDefects in Git itself
CI runners and build imagesGit version alignment, clone and fetch settings, shallow and partial clone, cache behaviorYour CI vendor supports its own runner softwareCI vendor defects
GitLab.com and GitHub.comThe repository, branching and CI settings you control, and large-repository performanceThe provider operates the service and supports it through its own planService-level faults
Repository migrationsInventory, history and LFS preservation, verification, cut-over and rollbackHost-specific import tools are the host'sRewriting each team's CI files unless scoped

Why AceMQ

What platform teams gain from AceMQ

Version coverage

Git and GitLab versions we support

Git and GitLab versions we support
ComponentLatest as read (19 November 2026)What the source saysWhat AceMQ does on it
Git2.56.1, released 26 October 2026git-scm.com lists it as the latest source release24/7 support on the Git versions your servers, runners and developers use
GitLab self-managed, 19.6Newest maintained releaseBug and security fixes (docs.gitlab.com/policy/maintenance)24/7 support
GitLab self-managed, 19.5 and 19.4Security fixes onlyMaintained for security fixes (same page)24/7 support, and planning of the move to the newest stop
GitLab self-managed, older releasesOutside the three maintained releasesSecurity fixes go to the current release and the two before it, with rare exceptions (same page)We support operating the instance and plan the route to a maintained release; fixes come from GitLab
GiteaRelease lines the Gitea project maintainsGoverned by the project24/7 support on the lines the project maintains

On the first call

Reading a Git platform incident: the four outputs we ask for

On the first call we ask for four artefacts because they separate causes in minutes.

1. git version and the clone settings

On the server, a runner and a developer machine. They show whether a feature such as partial clone is available on both sides and which depth the CI jobs use.

2. git count-objects -vH

For the repository behind the symptom. Loose objects, pack count and size separate a repository that needs maintenance from one that is simply large.

3. The platform's own health output

On a GitLab server, the status of its services and the result of its built-in check. They show whether the problem is the Git layer or the application around it.

4. A trace of the slow command

GIT_TRACE_PERFORMANCE and GIT_TRACE on one slow fetch or push. Most calls about slow Git end in the line that shows where the time went.

Escalation Path

Your first hour of a Git outage

A Git server that stops accepting pushes stops every team in minutes. The engineer on the line starts with the trace of the failing command, not with questions about what Git is.

  1. From 15 min (by plan)first responseEmergencyPushes failing for every developer on a production Git server; a GitLab upgrade that left the instance down; a repository with missing objects that blocks a release
  2. 1 hourfirst responseCriticalClones timing out for a CI fleet; a GitLab instance degraded under pipeline load; a credential exposed in history
  3. 4 hoursfirst responseHighSlow fetches on one large repository; runner image Git version mismatch; a failed backup job
  4. Next Dayfirst responseStandardBranching and merge rules, clone settings for a new pipeline, upgrade route questions, migration planning

Your plan sets the clock: pushes failing for every developer are treated differently from a branching-strategy question.

Want a named Git engineer who knows your repositories and runners? Request a quote or contact us.

Contact Us

Pricing

What does AceMQ Git support cost?

Git support is usually priced from $24,000 to $72,000 a year. The number of servers and repositories, the size of the largest repository, whether GitLab or another platform is in scope and your response plan shape where you fall.

Prices are in US dollars (USD). Response targets start at 15 minutes by plan, 24/7, and quote requests are answered within 1 hour. A contract that also covers other platforms earns a discount.

Typical engagements

Git problems we have scoped

Typical Git support engagements, written as scopes: what AceMQ would review, how, and what the engagement delivers. They describe a typical scope, not past work.

  • Assessment

    Self-Managed GitLab Upgrade Path Assessment

    DevOps Platform Team

    A typical engagement for a team running self-managed GitLab several releases behind: work out the required upgrade stops with GitLab's own tool, rehearse them on a restored copy, check runners and integrations, and plan the maintenance windows and a rollback.

    Git (version control)GitLabPostgreSQLJenkins
  • Assessment

    Large Git Repository Clone and Fetch Performance Assessment

    Engineering Productivity Team

    A typical engagement for a team whose main repository has grown until clones take many minutes: find what makes it large, set up partial clone, shallow clones and sparse checkout for CI and developers, schedule git maintenance, and plan any history clean-up.

    Git (version control)GitLabJenkins
  • From our platform practice

    Java Estate Inventory and OpenJDK Distribution Selection

    Mid-Sized Distribution Company

    A typical engagement for a company that wants to leave an Oracle Java SE subscription or avoid one: inventory every Java runtime, compare OpenJDK distributions against the estate, and write the migration plan.

    JavaOpenJDKDockerKubernetes
All use cases

Support options

Four tiers of Git support.

AceMQ offers Git support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for a platform your team runs, proactive monitoring that catches slow clones, storage pressure and upgrade drift first, and managed Git, where AceMQ runs the platform day to day and quotes the scope per estate.

  • Tier 1

    Git 24/7 Support & Incident Management

    Your platform team runs Git, we assist

    Best for: Teams that operate their own Git servers or GitLab and want an expert reachable for clone, upgrade or load problems.

  • Tier 2

    Git 24/7 Support with Proactive Monitoring

    Planned reviews of versions, backups and repository health

    Best for: Teams that want repository growth, storage pressure and upgrade distance examined before they cause an outage.

  • Tier 3

    Managed Git on Your Infrastructure

    We operate your Git platform in your estate

    Best for: Enterprises that keep Git on their own sites and want AceMQ running upgrades, backups and monitoring day to day.

  • Tier 4

    Fully Managed Git on AceMQ Infrastructure

    AceMQ runs the Git platform for you

    Best for: Teams that need a working Git platform without building a specialist team to look after it.

FAQ

Git support questions

Still have questions about Git? Email an Expert

Who provides Git support?

Git is an open-source project and has no vendor support contract. The platforms around it do: GitLab supports its own software, and other servers have their own projects or vendors. AceMQ provides independent Git support for servers, self-managed GitLab, Gitea and CI runners, 24/7, with response targets from 15 minutes, by plan.

Can you support Git alongside our GitLab plan?

Yes, and that is the usual set-up. GitLab handles defects and releases for its software. We handle why clones crawl, how an upgrade route should run, how runners and servers are sized and how repositories are maintained. When a defect is involved we reproduce it and drive the case.

Why are our git clone and git fetch so slow?

Clones crawl when the repository carries large blobs, a big working tree, many refs or unmaintained packs. We time a clone, run git count-objects -vH and trace the slow command, then change settings before history: shallow or partial clones, sparse checkout and scheduled git maintenance.

Why did our GitLab upgrade stop between versions?

GitLab requires each stop to be installed and its background migrations to finish before the next. We check the running version against the stops from GitLab's upgrade path tool, confirm the migrations, then retry or restore from the backup taken before the stop.

Do you support Gitea and plain Git servers as well as GitLab?

Yes: operations, upgrades, backups, migration and performance. Defects in Gitea or in Git itself are fixed by their projects.

Do you also do Git consulting?

Yes. Platform health checks, upgrade routes, large-repository performance, repository migration and branching strategy are on the Git consulting page, led by the same engineers who work the 24/7 rota.

Can we use AceMQ for Git without changing our current platform plan?

Yes. Many teams keep their GitLab plan and add AceMQ for the gaps, such as clone and load diagnosis at odd hours, upgrade routes or advice across several platforms. You can also hire us for one project, like a health check, with no annual commitment.

What drives the price of Git support?

Annual contracts typically run $24,000 to $72,000 (USD). Inputs are the number of servers and repositories, the size of the largest repository, the platform in scope, runner fleet size and your response plan. Describe the estate in a quote request and we respond within 1 hour.

Let's talk

Find What Slows Your Clones Before the Next Pipeline Burst

Send us your Git platform and version, the size of your largest repository and the symptoms you see. We reply to quote requests within 1 hour.

A senior Git engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email a Git Architect