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.
Caching layer support
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.
Planning a build, upgrade or migration instead? See AceMQ Memcached consulting and services.
Customers




Partners


Incident Triage
Cache trouble rarely announces itself. Each row below begins with a number from stats output, not with a guess about the application.
| Symptom you're seeing | What we check first |
|---|---|
| Hit ratio fell and nobody knows why | We 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 memory | We 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 stampede | When 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 tail | curr_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 values | Items 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 instances | A 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 keyspace | Adding 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 shard | Replacement 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.
Deployment coverage
| Deployment | What AceMQ covers | What the vendor covers | Excluded |
|---|---|---|---|
| Self-managed Memcached (VMs, bare metal, containers, Kubernetes) | Incident response, memory and slab tuning, hashing and client review, security review, upgrades | No vendor; the project offers community channels only (memcached.org, read 17 Nov 2026) | Hardware and OS faults outside the agreed scope |
| Amazon ElastiCache for Memcached | Client behaviour, key design, node count and sizing, parameter groups, cold-start planning | AWS 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 Memcached | The same application-layer scope | Google runs the service | Google platform faults |
| Applications and client libraries | Timeouts, pooling, hashing, serialisation, invalidation patterns | Library maintainers | Rewriting your application |
Support options
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.
What's Included
Daemon settings, slab behavior, client hashing and managed ElastiCache or Memorystore nodes, with the security review included.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
Self-run daemons, mcrouter fleets and the managed Memcached services from AWS and Google Cloud, plus hosts with no outbound access.
Version coverage
| Line | Version listed | Note |
|---|---|---|
| Memcached 1.6 | 1.6.45 (release notes dated 9 July 2026) | Latest release on memcached.org, read 17 Nov 2026 |
| Memcached 1.5 and 1.4 | Any | We support what runs in production and plan the move to 1.6 |
| ElastiCache for Memcached | Engine versions up to 1.6.22 listed by AWS | AWS engine versions page, read 17 Nov 2026 |
Escalation Path
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.
Response depends on plan. A cold ElastiCache shard in the middle of peak traffic is treated differently from a question about -I item size.
Pricing
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
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.
Digital Commerce Platform
Emergency remediation of a Memcached tier evicting hot keys while reporting free memory, traced to slab class allocation.
Digital Media Platform
Ongoing support for a Memcached tier prone to thundering-herd database load after node changes and cache expiry cliffs.
B2B SaaS Platform Provider
Assessment of Memcached sizing, key distribution, and hit rate to determine whether adding capacity would actually help.
Global Payments Processor
Consulting engagement to design multi-region Memcached topology, key namespacing, and invalidation strategy for a latency-sensitive platform.
Support options
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.
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.
We review slabs, clients and exposure
Best for: Teams who only learn about slab calcification or an open port after an incident.
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.
We run the cache tier for you
Best for: Teams that want fast lookups without owning node replacement and capacity planning.
One partner for Memcached
Cache design questions often lead to Redis and Valkey comparisons, capacity planning and the database that sits behind the cache.
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.
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.
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.
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.
Not by itself. Resilience comes from many nodes, consistent hashing, and an application that survives a cold shard. We design and test that behaviour.
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.
Yes: binding, UDP, SASL, TLS, firewall rules and client credentials, with a written finding list.
Hit ratio and eviction trends, slab distribution, connection limits, large-value failures, hashing and client configuration, security exposure, and a ranked list of fixes.
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.
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
Send us the output of stats and stats items from one node. We reply within 1 business hour with what the numbers say.
Production incident right now?Email a Memcached Architect