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.