Caching layer support

Memcached Support for ElastiCache, Memorystore and Self-Managed Fleets

Last reviewed by Tyler Eastridge

AceMQ supports Memcached 24/7 across Americas, EMEA and APAC: self-managed fleets on virtual machines and Kubernetes, Amazon ElastiCache for Memcached and Google Cloud Memorystore for Memcached. Most calls start with one of three problems: evictions while memory shows free, a database overload seconds after a cache node drops, or a hit ratio that collapsed overnight.

24/7 Memcached support with response targets from 15 minutes, by plan. Quote replies within 1 hour.

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

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

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

Problems we fix every week

Cache trouble rarely announces itself. Each row below begins with a number from stats output, not with a guess about the application.

Common Memcached production problems and how AceMQ resolves them
Symptom you're seeingWhat we check first
Hit ratio fell and nobody knows whyWe compute it from stats: get_hits / (get_hits + get_misses). Then we read stats items for evictions, reclaimed, expired_unfetched and evicted_unfetched. High evicted_unfetched means items are being written and pushed out without a single read, which is a caching design problem, not a memory problem. uptime and total_items on each node show whether a restart emptied the cache.
Evictions with free memoryWe compare stats slabs per slab class with the item size distribution. Memcached assigns memory to slab classes by chunk size, and automatic slab rebalancing (slab_reassign, slab_automove) may be disabled or too slow. watch evictions over a telnet or nc session shows what is being evicted live; -m is the cache size, not the process size, so we also compare it with resident memory.
Cache stampedeWhen a hot key expires, hundreds of requests hit the database together. Remedies, in order of effort: add jitter to TTLs, use a lock key with add, or use the meta protocol: mg with the vivify (N) and recache (R) flags returns one client a "win" token to rebuild the value while others get the stale copy. We test the pattern against your client library, since not every client speaks the meta commands.
Connections refused or latency at the tailcurr_connections against -c, listen_disabled_num (any non-zero value means the daemon refused a connection), conn_yields and the thread count (-t, default 4) against core count. Large multigets spread across many nodes make p99 the slowest node's p99.
Writes silently fail on large valuesItems over the maximum item size (-I, default 1 MB) are rejected, and many clients swallow the error. We read stats settings for item_size_max, find the failing keys from logs, and decide between compression, splitting and moving the value elsewhere.
Exposed instancesA Memcached bound to all interfaces without authentication is an open data store. We check -l binding, UDP (-U 0), SASL and TLS settings (-S, -Z), and security group and firewall rules, then record the result for the audit trail.
Fleet changes remap the whole keyspaceAdding or removing a node with modulo hashing sends most keys to a new node at once. We check that clients use consistent hashing (ketama) with the same node list and weights everywhere, including every language in the estate.
ElastiCache node replacement empties a shardReplacement or restart loses all data because Memcached has no persistence. We read the ElastiCache event log, CloudWatch CurrItems, Evictions and SwapUsage, and plan for a cold shard: pre-warming, request coalescing, and database protection.

A written root-cause note follows each incident, with the stats counters and client settings that explain what happened.

Hit ratio collapsed and the database is taking the load? Request a quote and we reply within one hour.

Contact Us

Deployment coverage

Which Memcached deployments does AceMQ support, and who covers what?

DeploymentWhat AceMQ coversWhat the vendor coversExcluded
Self-managed Memcached (VMs, bare metal, containers, Kubernetes)Incident response, memory and slab tuning, hashing and client review, security review, upgradesNo vendor; the project offers community channels only (memcached.org, read 17 Nov 2026)Hardware and OS faults outside the agreed scope
Amazon ElastiCache for MemcachedClient behaviour, key design, node count and sizing, parameter groups, cold-start planningAWS runs the service; engine versions it lists include 1.6.22 (ElastiCache engine versions page, read 17 Nov 2026)AWS platform faults; limits set by the service
Google Cloud Memorystore for MemcachedThe same application-layer scopeGoogle runs the serviceGoogle platform faults
Applications and client librariesTimeouts, pooling, hashing, serialisation, invalidation patternsLibrary maintainersRewriting your application

Support options

Who provides enterprise support for Memcached? Project, cloud and independent support compared

Memcached is an open-source project. The project lists documentation, Discord, a mailing list and GitHub issues, and names one company that offers business support. Cloud providers support their managed services. Independent support covers the fleets you run and the application behaviour around any of them.

Memcached project / Commercial and cloud
AceMQ independent support
HelpMemcached project: docs.memcached.org, Discord, the memcached Google Group, GitHub issues (memcached.org, read 17 Nov 2026)Commercial and cloud: The memcached.org site lists Cache Forge as offering business support; AWS and Google support their own services
HelpPhone and email, one contract
Response commitmentMemcached project: NoneCommercial and cloud: Per the vendor's terms
Response commitmentResponse targets from 15 minutes, by plan, 24/7
ScopeMemcached project: The softwareCommercial and cloud: Their product or service
ScopeThe fleet, the clients and the database behind it
PriceMemcached project: Free; the project accepts sponsorshipCommercial and cloud: Per vendor
Price$24,000 to $72,000 a year (USD), set by SLA, scope and deployment

What's Included

Everything in your Memcached support contract

Daemon settings, slab behavior, client hashing and managed ElastiCache or Memorystore nodes, with the security review included.

  • 01

    Emergency Incident Response

    Cache down, evictions running away, or a database melting from a miss storm. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge with access to diagnose — not a ticket acknowledgement.

  • 02

    Root Cause Analysis

    Every P1 closes with a written RCA: what failed, why, the fix applied, and the specific configuration or client-side change that prevents recurrence. Standard, not on request.

  • 03

    Slab & Memory Tuning

    Slab growth factor, chunk size boundaries, LRU crawler and slab automover settings tuned against your real item size distribution — so allocated memory tracks what you actually cache.

  • 04

    Client & Hashing Review

    Consistent hashing configuration, connection pooling, multiget batching, and timeout and retry policy across your client libraries. Most Memcached incidents are client-side and get fixed there.

  • 05

    Security & Exposure Review

    Binding, SASL authentication, UDP disablement, and network policy. Memcached has no authentication by default and has been abused for reflection amplification — we verify the exposure surface.

  • 06

    Capacity & Scaling Reviews

    Quarterly review of hit ratio trends, eviction rates, working set growth, and node sizing so you scale ahead of the miss storm rather than during it.

Why AceMQ

What our Memcached engineers bring

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your key namespaces, item size profile, and client stack — so a P1 call starts with diagnosis, not twenty minutes of you describing your cache tier.

  • No Tier-1 Triage Layer

    You reach a senior engineer directly by phone, email, or Slack. No help desk collecting information to pass along, and no escalation approval standing between you and someone who can actually fix it.

  • We Debug the Database Too

    A Memcached incident usually surfaces as a database incident. We work both sides — cache behaviour and the query load it was shielding — because fixing only one of them leaves the outage half solved.

  • Genuine Follow-the-Sun Coverage

    Round-the-clock coverage for customers in 26+ countries. Your 3am incident is someone's mid-afternoon — no overnight skeleton crew, no waiting for a region to wake up.

  • Proactive, Not Just Reactive

    Quarterly health checks plus shared intelligence across our support base. When a version-specific bug or client library regression surfaces on one cluster, every affected customer hears about it early.

  • Honest About Memcached vs. Redis

    Memcached is the right answer for a pure LRU cache and the wrong one for anything needing persistence, data structures, or replication. We will tell you which side of that line you are on before you spend a quarter migrating.

Cache environments covered

Self-run daemons, mcrouter fleets and the managed Memcached services from AWS and Google Cloud, plus hosts with no outbound access.

  • AWS (EC2, ECS, EKS)
  • Amazon ElastiCache for Memcached
  • Microsoft Azure (AKS)
  • Google Cloud (GKE)
  • Google Cloud Memorystore for Memcached
  • Kubernetes & OpenShift
  • VMware vSphere & Tanzu
  • Bare metal & on-premise
  • Hybrid cloud
  • Air-gapped / no outbound access
  • Memcached 1.5.x and 1.6.x
  • mcrouter-fronted clusters

Version coverage

Versions we support

Versions we support
LineVersion listedNote
Memcached 1.61.6.45 (release notes dated 9 July 2026)Latest release on memcached.org, read 17 Nov 2026
Memcached 1.5 and 1.4AnyWe support what runs in production and plan the move to 1.6
ElastiCache for MemcachedEngine versions up to 1.6.22 listed by AWSAWS engine versions page, read 17 Nov 2026

Escalation Path

Your first hour of a Memcached outage

A collapsed hit ratio usually puts the database under load within minutes, so the first reply is an engineer reading stats, not a case number.

  1. From 15 min (by plan)first responseEmergencyCache tier down or emptied, hit ratio near zero, database overloaded by the miss traffic
  2. 1 hourfirst responseCriticalEvictions while memory shows free, connections refused under load, a stampede on hot keys
  3. 4 hoursfirst responseHighWrites failing on large values, keyspace remapped after a node change, tail latency on large multigets
  4. Next Dayfirst responseStandardQuestions on slab settings, ketama client configuration, binding and SASL, and sizing

Response depends on plan. A cold ElastiCache shard in the middle of peak traffic is treated differently from a question about -I item size.

Looking for a named engineer to own your cache tier? Get a quote or contact the team.

Contact Us

Pricing

What does AceMQ Memcached support cost?

Memcached support is quoted per scope and typically costs $24,000 to $72,000 a year. The drivers are node count, how much of your database load the cache absorbs, and whether you run ElastiCache, mcrouter or bare daemons.

Prices are in USD. Response targets start at 15 minutes depending on plan, 24/7, and quote requests get a reply within 1 hour. Bundling Redis, Valkey or database support brings a multi-technology discount.

Support In Practice

Cache problems measured and fixed

Memcached support and consulting work from AceMQ. Each card links to the full write-up: the cache tier, what AceMQ diagnosed or changed, and the result.

1 / 4 case studies

All use cases

Support options

Four tiers of Memcached support.

AceMQ offers Memcached support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for tiers your team runs, proactive monitoring that catches slab imbalance and hit-ratio drift first, managed Memcached on your own infrastructure, and fully managed Memcached on AceMQ infrastructure. Self-managed nodes and Amazon ElastiCache are covered in all four.

  • Tier 1

    Memcached 24/7 Support & Incident Management

    You run the cache, we answer hard ones

    Best for: Teams that manage Memcached themselves and want an expert when evictions or stampedes show up.

  • Tier 2

    Memcached 24/7 Support with Proactive Monitoring

    We review slabs, clients and exposure

    Best for: Teams who only learn about slab calcification or an open port after an incident.

  • Tier 3

    Managed Memcached on Your Infrastructure

    We operate the Memcached fleet you own

    Best for: Companies keeping caches on their own hosts or accounts, with mcrouter and monitoring maintained for them.

  • Tier 4

    Fully Managed Memcached on AceMQ Infrastructure

    We run the cache tier for you

    Best for: Teams that want fast lookups without owning node replacement and capacity planning.

FAQ

Memcached support questions

Still have questions about Memcached? Email an Expert

Who provides enterprise support for Memcached?

AceMQ does, around the clock. On the top plans a response begins within 15 minutes. Sev 1 example: a flush leaves the hit ratio near zero and the database saturated. We read stats and CurrItems, advise on request coalescing and pre-warming, then write the RCA. P2 1 hour, P3 4 hours, P4 next business day.

How do I calculate the Memcached hit ratio?

get_hits / (get_hits + get_misses) from stats, per node and for the fleet. Read it with evicted_unfetched, which shows whether items are being evicted without being read.

Why do we get evictions when Memcached shows free memory?

Memory is assigned to slab classes by item size. If your item sizes changed, one class can be full while others are empty. Check stats slabs and the automove settings.

What causes a cache stampede, and how do we stop it?

A hot key expires and many requests rebuild it together. Use TTL jitter, a lock key, or the meta protocol's vivify and recache flags so only one client rebuilds.

Does Memcached have high availability?

Not by itself. Resilience comes from many nodes, consistent hashing, and an application that survives a cold shard. We design and test that behaviour.

Is Memcached or Redis right for us?

Memcached suits a simple, multi-threaded cache with no persistence. Choose Redis or Valkey for persistence, replication, data structures or pub/sub. We compare them against your workload, not in general.

Can you review Memcached security?

Yes: binding, UDP, SASL, TLS, firewall rules and client credentials, with a written finding list.

What does a Memcached health check include?

Hit ratio and eviction trends, slab distribution, connection limits, large-value failures, hashing and client configuration, security exposure, and a ranked list of fixes.

Can we start with one cache review?

Yes. A single engagement, for example a hit-ratio investigation, a slab and eviction review or a security check on exposed instances, needs no yearly commitment. If cache incidents recur, the annual plan adds around-the-clock response and engineers who already know your key patterns.

What should we expect to pay for Memcached support?

A year of cover usually costs $24,000 to $72,000 (USD). Scope is set by the number of nodes and clusters, how dependent the database is on cache hits, whether you use managed ElastiCache or Memorystore, and how quickly you need a response. Tell us the setup and we quote within 1 hour.

Let's talk

Your Cache Tier Is Your Database's Last Line of Defence

Send us the output of stats and stats items from one node. We reply within 1 business hour with what the numbers say.

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

Production incident right now?Email a Memcached Architect