Kong Gateway support, 24/7

Kong Support for Gateway OSS, Enterprise, Konnect Data Planes and Kubernetes Ingress

Last reviewed by Tyler Eastridge

AceMQ supports Kong 24/7 for Gateway OSS, Gateway Enterprise, Konnect data planes and Kong Ingress Controller. Most calls start with one of three problems: intermittent 502s to upstreams that are healthy, plugin chains that add latency to every request, or rate limits that allow several times the configured traffic once the gateway scales out.

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.

Planning a build, upgrade or migration instead? See AceMQ Kong 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

Kong problems we fix every week

Gateway faults hide behind generic 502s and 429s. These rows go from the symptom to the Kong target list, plugin phase or sync setting we inspect first.

Common Kong production problems and how AceMQ resolves them
Symptom you're seeingWhat we check firstTypical resolution
Intermittent 502 with a healthy upstreamKong's target list and DNS cache (dns_stale_ttl, dns_valid_ttl) against how fast pod IPs rotate, then the NGINX error log for connect() failedAlign DNS TTL handling with the platform, add active health checks
Targets ejected and never returnWhether only passive health checks exist; passive checks cannot re-probe an ejected targetAdd an active check on an unauthenticated liveness path
Active health check marks every target downThe probe path: a path that returns 401 to an unauthenticated probe makes healthy targets look deadPoint the probe at a real liveness endpoint
p99 latency crept up with no single deployment to blameLatency per plugin and phase; custom Lua doing a blocking call in the access phase; several auth plugins on one routeConsolidate auth, make external lookups asynchronous or cached, set a per-plugin latency budget
Rate limit allows 8x the quotaThe policy setting of the rate-limiting plugin: local counts per node, so eight replicas enforce eight times the limitMove to redis or cluster policy and define Redis timeout and failure behaviour
Route change live on one node, not on anotherControl plane to data plane sync in hybrid mode, or db_update_frequency in database modeFix propagation and confirm the data plane's cached config version
Kong Ingress Controller ignores a new routeController logs, ingressClassName against the controller's watched class, and KongPlugin objects referenced across namespacesCorrect the class or the annotation target
Worker memory climbs until a restartRoute and service count, router rebuild frequency, plugin-held stateReduce config churn, batch declarative updates

Every serious incident is followed by an RCA that names the upstream, plugin or sync setting at fault and the config change applied.

Kong returning 502s on healthy upstreams? Request a quote and a senior engineer answers within one hour.

Contact Us

Deployment coverage

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

AceMQ supports the gateway you run and the platform around it. The table splits the work between us, Kong and your platform vendor.

DeploymentWhat AceMQ coversWhat the vendor coversExcluded
Kong Gateway OSS (database-backed, DB-less)Incident response, plugin chain and upstream design, TLS, rate limiting, upgrades, CVE advice for your versionThe community edition has no support period from Kong; Kong's policy applies to Gateway Enterprise only (developer.konghq.com/gateway/version-support-policy/, read 17 Nov 2026)Features that exist only in Enterprise
Kong Gateway EnterpriseThe same, plus plugin and RBAC configuration, and escalation to Kong with a diagnosed caseKong handles security vulnerabilities, outages and upgrade-blocking bugs on supported versions (same page)A patched Enterprise binary; defects in Kong's own code
Konnect data planesThe gateways you run, their plugins, decK pipelines and the platform under themKonnect has its own version support policy and Kong runs the hosted control plane (same page)The Konnect control plane itself
Hybrid mode (control plane and data plane)Sync health, certificate rotation between planes, data plane placement near workloadsKong supports the product on supported versionsNetwork faults between regions
Kong Ingress Controller on Kubernetes and OpenShiftIngress class, KongPlugin and KongClusterPlugin resources, reconciliation failures, namespace scopingThe Kubernetes distribution vendor supports the platformCluster control-plane faults
Custom Lua plugins and plugin development kit codeProfiling, blocking-call removal, review of phase usageNot covered by Kong supportWriting new plugins as a feature project

Support options

Who provides enterprise support for Kong? Kong and independent support compared

Kong sells support for Kong Gateway Enterprise and Konnect. Kong Gateway OSS has no vendor support period, so enterprise support for it comes from an independent provider or your own team. A Kong subscription and an independent contract answer different questions.

Kong support (Enterprise, Konnect)
AceMQ independent support
What it coversDefects in Kong Gateway Enterprise and Konnect on supported versions
What it coversGateway OSS and Enterprise on any version, plus the plugin chain, upstreams, Kubernetes and network around them
Minor version supportOne year from release for each minor version (Kong version support policy, read 17 Nov 2026)
Minor version supportSupport for the version you run
LTSThree years from release for each LTS; 3.10 and 3.14 are the current LTS lines
LTSSame
After the support periodUp to 12 months of limited help to upgrade, no patches (same page)
After the support periodSupport continues; we plan the upgrade to a Kong-supported line
PriceSet by Kong subscription
Price$24,000 to $72,000 a year (USD), set by SLA, scope and deployment. Quote reply within 1 hour
Product defectsKong can fix and ship its own code
Product defectsWe diagnose, hand Kong a reproduced case and work the escalation
Gateway OSSNot covered
Gateway OSSCovered

Short note: if you pay for Enterprise features such as RBAC or the vendor's defect fixes, keep the subscription. If the incident is in the plugin chain, the upstream or the Kubernetes layer, the vendor's scope ends and ours begins. Many estates hold both.

What's Included

Everything in your Kong support contract

Kong Gateway in database, DB-less or hybrid mode, the Ingress Controller and the plugin chain, all under one agreement.

  • 01

    Emergency Incident Response

    Gateway returning errors, upstreams ejected, config not propagating, or a plugin failing closed on every request. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge with access to diagnose.

  • 02

    Root Cause Analysis

    Every P1 closes with a written RCA: what failed, why, the fix applied, and the plugin, upstream, or cluster configuration change that prevents recurrence. Standard, not on request.

  • 03

    Plugin Chain & Latency Tuning

    Ordering the chain so cheap rejections happen first, caching auth introspection results, and profiling custom Lua plugins — cutting per-request overhead the gateway adds to every call.

  • 04

    Upstream & Health Check Design

    Active and passive health checks, DNS and SRV resolution behaviour, load balancing algorithm selection, retries, and timeouts configured so a slow upstream degrades gracefully instead of cascading.

  • 05

    Auth, TLS & Security

    OIDC and OAuth2 integration, key and JWT authentication, mutual TLS and certificate lifecycle, ACL design, and rate limiting that actually enforces across every node in the cluster.

  • 06

    Upgrades & Deployment Model

    Version upgrades with rolling procedure, migration between traditional database-backed, DB-less declarative, and hybrid control-plane modes, and Kong Ingress Controller adoption in Kubernetes.

Why AceMQ

Why API teams keep us on their gateway

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your route set, your plugin chain, and your deployment mode — so a P1 call starts with diagnosis, not twenty minutes of you explaining your gateway topology.

  • 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 Diagnose Through the Gateway, Not At It

    The gateway is where every problem shows up and rarely where it lives. We follow the request into DNS, the service mesh, the upstream runtime, and the database behind it — because that is where the 502 usually originates.

  • Lua and NGINX Level, Not Just Config

    Kong is OpenResty underneath. When the answer is not in a plugin setting we read the NGINX error log, profile custom Lua, and work at the level the gateway actually runs at.

  • 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 on route count, plugin overhead, upstream health, and version currency — plus alerts on CVEs affecting the exact Kong and OpenResty versions you run.

Kong deployments covered

OSS and Enterprise gateways, control and data planes, Kubernetes clusters and plain VMs, including networks that cannot reach AceMQ.

  • Kong Gateway (OSS)
  • Kong Gateway Enterprise
  • Hybrid mode (control plane / data plane)
  • DB-less declarative configuration
  • PostgreSQL-backed clusters
  • Kong Ingress Controller
  • Kubernetes & OpenShift
  • AWS (EC2, EKS)
  • Microsoft Azure (AKS)
  • Google Cloud (GKE)
  • Bare metal & on-premise
  • Air-gapped / no outbound access

Version coverage

Kong Gateway versions we support

Kong's policy gives each minor version one year of patches and each LTS three years, and AceMQ supports the version you run. The table pairs Kong's listed dates with our cover.

Kong Gateway versions we support
Kong Gateway EnterpriseReleasedKong support ends (deployment targets)AceMQ cover
3.1615 Sep 202615 Sep 202724/7 support
3.152 Jul 20262 Jul 202724/7 support
3.14 LTS7 Apr 20267 Apr 202924/7 support
3.1318 Dec 202518 Dec 202624/7 support
3.10 LTS27 Mar 202531 Mar 202824/7 support
3.12, 3.11, 3.9 and earlierEarlierNot in Kong's current supported list24/7 support and an upgrade plan to a Kong-supported line
Gateway OSS, any releasen/aNo support period from Kong24/7 support

Source: developer.konghq.com/gateway/version-support-policy/, read 17 November 2026. Individual OS targets can differ from the dates above; Kong's page lists them per platform.

In practice

Moving from Kong Gateway 2.8 to 3.x, and between deployment modes

Two changes cause most upgrade incidents. First, from Kong Gateway 3.0 a route path is treated as a regular expression only if it starts with ~; every other path matches as plain text, so regex routes carried over unchanged stop matching. For declarative files, deck file convert adds the prefix. Second, moving from database-backed to DB-less or hybrid mode changes where state lives: DB-less gives up runtime-created consumers and some plugin state, and hybrid keeps the database at the control plane while data planes run from cached config. We run a parallel validation of routes, status codes and latency before any cutover, and keep the old nodes as the rollback.

Consulting

Kong consulting and professional services

AceMQ delivers Kong consulting as named deliverables, each ending in a document or a runbook your team owns.

Kong consulting and professional services
DeliverableWhat you receive
Gateway health checkRoute and plugin inventory, latency attributed per plugin and phase, upstream health-check review, version currency, certificate expiry list
Plugin and latency assessmentControlled comparisons with plugins disabled under production-like load, a rework list for blocking custom Lua, a latency budget per plugin
Architecture designHybrid control plane and data plane topology, one declarative source of truth in version control, a shared plugin baseline for logging, tracing, size limits and rate limiting
Upgrade and migration plan2.8 to 3.x route conversion, mode migration, staged cutover per route group with rollback
Rate limiting and auth redesignCounter store sizing, Redis timeout and failure behaviour, one consumer and credential model
Gateway exit assessmentA complete service, route, plugin and consumer inventory with a mapping to a target gateway, for teams deciding whether to move or stay

Escalation Path

Your first hour of a Kong outage

The engineer on your call reads the NGINX error log and the upstream health state straight away, so the 502 is localized before anyone guesses.

  1. From 15 min (by plan)first responseEmergencyGateway down or returning errors on all routes, data plane nodes unable to load config, API traffic blocked
  2. 1 hourfirst responseCriticalHealthy upstreams marked down, 502s from stale DNS, routes live on some nodes only, rate limits not holding
  3. 4 hoursfirst responseHighp99 drift from plugin chains, Ingress Controller ignoring new routes, worker memory climbing
  4. Next Dayfirst responseStandardQuestions on health check design, hybrid mode, plugin choice and 2.8 to 3.x upgrade planning

Targets follow your plan. A data plane serving stale routes and a question about db_update_frequency do not get the same clock.

Want a named Kong engineer on your gateway estate? Ask for a quote or message the team.

Contact Us

Pricing

What does AceMQ Kong support cost?

Kong support is quoted per scope and usually costs $24,000 to $72,000 a year. The size of the quote follows the number of gateway nodes and environments, mode (database, DB-less or hybrid), plugin load, and response level.

Prices are in USD. Response targets start at 15 minutes depending on plan, 24/7, and quote requests are answered within 1 hour. Covering other gateways or the services behind them in one contract earns a discount.

Support In Practice

Kong faults we have found and fixed

Kong support and remediation work from AceMQ. Each card links to the full write-up: the gateway estate, what AceMQ diagnosed or changed, and the result.

  • Support

    Kong Rate Limiting Consistency Support

    B2B SaaS Provider

    Fixing rate limits that allowed several times the configured quota because the plugin was using the local counter policy across a multi-node gateway.

    KongRedisKubernetesPostgreSQL
  • Assessment

    Kong Plugin and Latency Assessment

    Payments Technology Provider

    Measuring where request latency is actually spent inside the Kong plugin chain, and which plugins are worth their cost.

    KongRedisKubernetesNGINX
All use cases

Support options

Four tiers of Kong support.

AceMQ offers Kong support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for gateways your team runs, proactive monitoring that finds plugin, health check and certificate problems first, managed Kong on your own infrastructure, and fully managed Kong on AceMQ infrastructure. OSS, Enterprise and Konnect data planes are covered in all four.

  • Tier 1

    Kong 24/7 Support & Incident Management

    You run Kong, we answer the hard faults

    Best for: Platform teams that own routes and plugins and want expert help with 502s, ejected targets and sync lag.

  • Tier 2

    Kong 24/7 Support with Proactive Monitoring

    We review plugins, health checks and sync

    Best for: Teams whose latency creeps and whose limits drift, with no clear deployment to blame.

  • Tier 3

    Managed Kong on Your Infrastructure

    We operate Kong nodes in your estate

    Best for: Organizations needing control and data planes kept inside their own clusters or data centers.

  • Tier 4

    Fully Managed Kong on AceMQ Infrastructure

    We run the gateway layer for you

    Best for: Groups that want governed APIs without carrying gateway upgrades and on-call themselves.

FAQ

Kong support questions

Still have questions about Kong? Email an Expert

Who provides enterprise support for Kong?

AceMQ provides it for Kong, 24/7, with response from 15 minutes on the top plans. Sev 1 example: 502 on every route after pods rotate. On a bridge we check dns_stale_ttl and the NGINX error log, then write the RCA. P2 is 1 hour, P3 4 hours, P4 next business day.

Does Kong Gateway OSS have commercial support?

Not from Kong. Kong's version support policy applies to Kong Gateway Enterprise, and the community edition has no support period. AceMQ supports OSS on any release, including the incident work, upgrade planning and CVE advice that a vendor contract would otherwise provide.

Why does Kong return 502 when the upstream is healthy?

The usual causes are DNS caching and health check design. Kong caches resolved addresses for the record TTL, so where pod IPs rotate faster than the TTL it keeps dialling dead addresses while a direct curl succeeds. A passive-only health check never re-probes an ejected target, and an active check on a path that needs authentication ejects healthy ones. All are configuration fixes.

Why is my Kong rate limit not enforced across nodes?

The local policy keeps counters per node, so N replicas enforce N times the limit. The cluster and redis policies share state. Redis is the usual choice at scale, and it needs its own timeout and failure behaviour defined because it adds a network hop to every request.

We have a Kong Enterprise subscription. Why add third-party Kong support?

Kong's support handles defects in its product on supported versions. It does not design your plugin chain, debug the services behind the gateway or fix the Kubernetes and network configuration around it. AceMQ covers that layer, works alongside the subscription, and hands Kong a reproduced case when the fault is in the product.

Do you support Kong Ingress Controller and Konnect?

Yes to both. For Ingress Controller we handle ingress class, KongPlugin resources, namespace scoping and reconciliation failures that look like silent no-ops. For Konnect we cover the data plane gateways, plugins, decK pipelines and platform you run, while Kong runs the hosted control plane.

Can you help us move from database mode to DB-less or hybrid?

Yes, and we say whether you should. DB-less suits GitOps-managed config but gives up runtime-created consumers and some plugin state. Hybrid keeps the database at the control plane and suits multi-region estates. We validate in parallel instead of cutting over on a weekend.

Can you upgrade us from Kong Gateway 2.8 to 3.x?

Yes. The router change is the main risk: from 3.0 a path is a regex only with the ~ prefix. We convert declarative files, review plugin and configuration changes, and run a rolling upgrade with a tested rollback.

What does a Kong health check include?

Route and plugin inventory, latency per plugin and phase, upstream and health-check configuration, rate-limit policy against node count, certificate and SNI mapping, version currency against Kong's published policy, and a ranked fix list. Quotes are answered within 1 hour.

Who offers Kong consulting and professional services?

Kong offers professional services for its own products, and independent firms such as AceMQ consult on Kong without tying the advice to a licence. AceMQ's consultants are the same engineers who work the 24/7 rota, so designs are shaped by what fails in production. See Kong consulting.

Can we hire Kong help without a long contract?

Yes. A single job such as a 502 investigation, a hybrid-mode migration or a version upgrade can be bought alone. If the gateway carries customer traffic, the annual plan adds 24/7 response and named engineers who already know your routes and plugins.

What decides a Kong support price?

Expect $24,000 to $72,000 a year (USD). We weigh how many gateway nodes and environments run production traffic, whether you use database, DB-less or hybrid mode, the Ingress Controller, how heavy the plugin chain is, and the response target. A quote request is answered in 1 hour.

Let's talk

Know Which Layer Owns the 502 Before the Next Deploy

Send us your Kong version, deployment mode and a sample of the gateway error log. We reply to quote requests within 1 hour.

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

Production incident right now?Email a Kong Architect