Istio support, 24/7

Istio Support for Sidecar, Ambient and Gateway Meshes

AceMQ provides Istio support and Istio enterprise support 24/7 for sidecar, ambient and gateway meshes, beside a vendor subscription or on its own. Typical Istio incidents are intermittent 503s after a DestinationRule or PeerAuthentication change, sidecars that never re-injected after an upgrade, and ambient namespaces where a policy needs a waypoint.

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
enterprise customers
160+
Sev 1 incidents handled a year
40+

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

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

Istio incidents we triage, and the first thing we check

Eight Istio problems, from a DestinationRule that sends plain HTTP into a STRICT mesh to a ztunnel path with no waypoint, each paired with the istioctl command or Envoy response flag read first.

Common Istio production problems and how AceMQ resolves them
Symptom you're seeingWhat we check firstTypical resolution
503 errors begin right after a DestinationRule is applied and stop when it is revertedThe Envoy response flag in the istio-proxy access log (kubectl logs <pod> -c istio-proxy; flags sit after the response code, UF means the upstream connection failed); the DestinationRule's trafficPolicy.tls.mode against the mesh-wide mTLS setting, because an unset mode defaults to DISABLE and the client sidecar sends plain HTTP to a server that expects TLS.Set trafficPolicy.tls.mode to ISTIO_MUTUAL wherever mTLS is on, or scope the rule to the workloads it was written for, and add the change to a pre-merge istioctl analyze run.
503 UC when a client reaches StatefulSet pods by pod IP under STRICT mTLSWhether the Service is headless (clusterIP: None), the port name (http-web against tcp-web) and the Host header the client sends; the sidecar on the server side finds no route entry for a request that arrived through the passthrough cluster.Send the right Host header, address pods by their stable DNS names, or name the port tcp-<name> so only the TCP proxy filter is used.
New pods fail to start with a failed calling admission webhook error from sidecar-injector.istio.io, or start without a sidecarThe caBundle of the MutatingWebhookConfiguration against the root certificate mounted in the istiod pod (x509: certificate signed by unknown authority points to an empty or stale one); the webhook's namespaceSelector; whether the namespace carries both istio-injection and istio.io/rev, since istio-injection wins.Repair the caBundle, relabel the namespace to one label, remove a leftover injector webhook from the old control plane, and restart the workloads to re-inject.
A route or policy change is not taking effect on some workloadsistioctl proxy-status for SYNCED, NOT SENT and STALE per proxy (STALE means istiod sent an update and got no acknowledgement); istioctl proxy-config listeners, routes, clusters and endpoints on the pod that misbehaves; istioctl analyze --all-namespaces for the resource.Fix the connection or resource that keeps the proxy out of sync, then confirm the proxy-config output matches the intended route before closing.
Ingress gateway returns 404, or health checks pass while real traffic failsGateway tls.mode (SIMPLE or PASSTHROUGH) against whether the VirtualService uses http or tls routing, via istioctl proxy-config routes and listeners; two Gateways sharing one wildcard certificate, which makes HTTP/2 browsers reuse a connection and receive 404; a cloud load balancer that terminates TLS without forwarding SNI.Match the routing type to the Gateway's TLS mode, merge to a single wildcard Gateway, or pass TLS through or set hosts to * where SNI is lost.
Requests denied or allowed that should not be after an AuthorizationPolicy changeistioctl x authz check <pod>.<namespace>, then istioctl proxy-config log deploy/<name> --level rbac:debug to read the rules the proxy evaluated; a stray list item that created a second, broader rule; HTTP-only fields such as host or path on a TCP port, which make the policy match nothing or deny everything.Correct the rule structure, name the Service port with its protocol, test against a canary workload and keep the previous policy as the way back.
An EnvoyFilter that worked stopped applying after an Istio upgradeWhether it uses INSERT_BEFORE or INSERT_AFTER relative to a built-in filter such as istio.stats, which is ignored with nothing in the log when the target filter is newer; whether its match includes proxyVersion, so the filter it patched was replaced.Use an operation that does not depend on another filter, such as INSERT_FIRST, or set an explicit priority, and keep an inventory of EnvoyFilters before each upgrade.
Ambient namespace: traffic fails between pods after the namespace joined the meshistioctl ztunnel-config workloads and certificates for the ztunnel on each node, ztunnel logs (kubectl -n istio-system logs -l app=ztunnel) for the connection, and whether an L7 AuthorizationPolicy or route is targeting a namespace that has no waypoint.Add a waypoint for the namespace or retarget the policy, confirm the workloads and certificates appear in ztunnel, then re-test the path.

Every P1 comes with a written cause naming the resource, revision or proxy involved.

Traffic denied or 503s across the mesh? Ask for a quote and an Istio engineer replies within the hour.

Contact Us

Deployment coverage

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

DeploymentWhat AceMQ coversWho else covers itExcluded
Sidecar mode on upstream Istio24/7 incident response on istiod, sidecar injection, xDS sync, mTLS, AuthorizationPolicy and traffic rules; revision-based upgrades; written RCA on every P1The Istio community: patch releases and technical assistance for each minor until 6 weeks after the N+2 minor ships (istio.io, read 19 November 2026)Patched or backported Istio builds
Ambient mode (ztunnel and waypoints)Ztunnel and waypoint diagnosis, policy retargeting to waypoints, namespace-by-namespace moves with a way backThe Istio project, which publishes the releases and documentationDefects in features the project has not marked stable; these are reported upstream
Ingress and egress gateways, Gateway and VirtualService routingTLS mode against routing type, SNI and certificate handling, 404 and 503 triage, gateway upgradesYour cloud provider for its load balancerLoad balancer and DNS faults outside the cluster
Multicluster and cross-network meshesCross-cluster endpoint and certificate checks with istioctl, root of trust arrangements, failure drills across clustersYour network and cloud teams for the paths between clustersWAN and VPN faults
Vendor builds: Tetrate, Solo.io, Red Hat OpenShift Service Mesh, Google Cloud Service MeshConfiguration, policy, troubleshooting and upgrade planning beside your subscriptionThe vendor supplies its build, its fixes and its own tooling (vendor pages, read 19 November 2026)Defects in a vendor's own build, which stay with the vendor
Kubernetes and nodes under the meshCluster, CNI, DNS and node problems that surface as mesh errors, when Kubernetes support is in your scopeYour cloud provider or distribution vendor for the platformPlatform faults outside the contract scope

Istio vendors and independent support

Who provides Istio enterprise support? Vendors and independent support compared

Istio is open source, and its community provides patch releases and technical assistance for each minor. The project's own page says third parties and partners may offer longer-term support (istio.io, read 19 November 2026). Several vendors sell Istio enterprise support; independent providers such as AceMQ support Istio operations alongside a subscription or without one.

Istio community and vendors
AceMQ independent support
Who provides itIstio community (open source). Vendors: Tetrate, Solo.io, Red Hat (OpenShift Service Mesh, with OpenShift subscriptions) and Google Cloud (Cloud Service Mesh) (vendor pages, read 19 November 2026)
Who provides itIndependent engineers who work your mesh whichever build it runs. AceMQ ships no Istio distribution
Hours and responseCommunity: no response time stated. Solo.io lists 24/7 support (solo.io, read 19 November 2026). Tetrate lists production support without stating hours (tetrate.io, read 19 November 2026)
Hours and response24/7 across Americas, EMEA and APAC. Response targets from 15 minutes, by plan. Senior engineers assigned to your account
Longer version lifeTetrate lists extended CVE protection, 14 months of version life against 8 for its base. Solo.io lists N-4 long-term support (vendor pages, read 19 November 2026)
Longer version lifeNone. No backports; we plan revision-based upgrades so the mesh stays inside the upstream window
FIPS buildsTetrate lists FIPS-verified Istio and Solo.io lists FIPS certified builds (vendor pages, read 19 November 2026)
FIPS buildsNo builds. We can compare a vendor's FIPS build with an upstream upgrade cadence for your requirement
Product defectsThe vendor ships a fix in its build; upstream fixes arrive in project releases
Product defectsWe reproduce, prepare the case for your vendor or the Istio issue tracker, and apply the fix
Where it runsOpenShift Service Mesh is tied to OpenShift subscriptions; Google's Cloud Service Mesh targets Google Cloud and supported GKE platforms (vendor pages, read 19 November 2026)
Where it runsKubernetes you run or a managed Kubernetes service
PriceNot published on the Tetrate or Solo.io pages read (19 November 2026)
Price$24,000 to $72,000 a year (USD), set by SLA, scope and deployment. Quote reply within 1 hour

Where AceMQ is not the right fit: if the requirement is a FIPS-verified build, a version life longer than upstream's or a backported fix for a minor the project no longer patches, that is a vendor subscription, and AceMQ ships none of them. A team with a subscription can add an independent contract for the gap between a product defect and a configuration problem, such as a DestinationRule that sends plain HTTP into a STRICT mesh.

Why AceMQ

What Istio teams gain from AceMQ

Version coverage

Which Istio versions does AceMQ support?

Upstream Istio supports a minor release until 6 weeks after the minor two releases newer ships. The table follows the project's supported releases page as read on 19 November 2026 (istio.io/latest/docs/releases/supported-releases/). Release dates are left out because the project's own pages have disagreed on them.

Which Istio versions does AceMQ support?
Istio minorProject statusKubernetes and Envoy branchAceMQ scope
Istio 1.32Supported by the projectKubernetes 1.33 to 1.37; Envoy release/v1.4024/7 incident response and upgrade planning
Istio 1.31Supported by the projectKubernetes 1.32 to 1.37; Envoy release/v1.3924/7 incident response and upgrade planning
Istio 1.30Supported by the projectKubernetes 1.32 to 1.36; Envoy release/v1.3824/7 incident response; upgrade is the next planned step
Istio 1.29Not supported; end of life was 15 October 2026Kubernetes 1.31 to 1.35 when it was supportedWe triage incidents and plan the move to a supported minor; no patches
Istio 1.28 and olderNot supported by the projectListed on the project's page as unsupportedWe triage incidents and plan the move to a supported minor; no patches

The project allows the control plane to be one version ahead of the data plane, never behind, and recommends revisions so there is no skew at all. The project's page lists its own expected dates for each minor, which we do not restate here, and AceMQ does not supply fixes for a minor the project has stopped patching.

On the first call

Reading an Istio incident: the four outputs we ask for

On the first call we ask for four outputs because they separate a control plane problem from a proxy problem in minutes.

1. istioctl proxy-status

Every proxy against istiod. SYNCED, NOT SENT and STALE show whether configuration reached the proxy, and the istiod and version columns show which revision each proxy follows and where the mesh is skewed.

2. The istio-proxy access log for the failing path

kubectl logs <pod> -c istio-proxy, with the response code and the Envoy response flag beside it. NR, UO, UF and UC point at routing, circuit breaking, the upstream connection and the listener, so the next command is chosen from evidence.

3. istioctl analyze --all-namespaces and the resources for the host

The DestinationRule, PeerAuthentication and AuthorizationPolicy that apply to the failing host. Istio's own troubleshooting page names a TLS mode that does not match the server as the cause of 503s that start right after a DestinationRule is applied.

4. Namespace labels, webhooks and revision tags

The istio-injection and istio.io/rev labels, kubectl get mutatingwebhookconfigurations and istioctl tag list. These show which revision injects each namespace, which is where version surprises and injection failures start.

Escalation Path

Your first hour of an Istio outage

A mesh that denies traffic mesh-wide stops every service behind it. The engineer on the line starts with istioctl proxy-status and the access log, not with an explanation of what a service mesh is.

  1. From 15 min (by plan)first responseEmergencyProduction outage: mesh-wide 503s or denied traffic, new pods unable to start because injection fails, or a gateway serving the wrong routes
  2. 1 hourfirst responseCriticalSerious degradation: STALE proxies in one namespace, a namespace failing after a revision tag change, a gateway certificate close to expiry
  3. 4 hoursfirst responseHighAn EnvoyFilter that stopped applying after an upgrade, sidecars on an older proxy than the control plane, ambient traffic failing between pods
  4. Next Dayfirst responseStandardRevision and tag layout, policy review, ambient assessments, upgrade runbooks and health check findings

Your plan sets the clock: a mesh denying traffic is treated differently from a question about revision tags.

Want a named Istio engineer who knows your revisions, gateways and policies? Request a quote or contact us.

Contact Us

Pricing

What does AceMQ Istio support cost?

Istio support is usually priced from $24,000 to $72,000 a year. The number of clusters, sidecar or ambient mode, gateways and multicluster scale, 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 Kubernetes or your brokers earns a discount.

Typical engagements

Typical Istio engagements, described as scope

These are typical Istio engagements described as scope: what the work covers and what it delivers, not results for a named customer.

  • Support

    Istio Intermittent 503 Incident Triage

    Platform Engineering Team

    A typical 24/7 incident engagement for intermittent 503 or upstream connect errors between meshed workloads: Envoy response flags from the access logs, proxy sync state from istioctl, and the DestinationRule and PeerAuthentication settings checked against each other.

    IstioEnvoyKubernetes
  • Consulting

    Istio Revision-Based Canary Upgrade Planning

    Platform Engineering Team

    A typical engagement for a platform team that runs Istio sidecars across many namespaces and needs a canary upgrade plan: a pre-upgrade check, a new control plane revision beside the old one, namespace-by-namespace moves and a rollback written before the first change.

    IstioKubernetesEnvoy
  • Assessment

    Istio Sidecar to Ambient Migration Assessment

    Platform Engineering Team

    A typical engagement for a platform team that runs Istio with sidecars and is weighing ambient mode: a namespace-by-namespace verdict on what can move, what needs a waypoint and what blocks the move.

    IstioKubernetesEnvoyGateway API
All use cases

Support options

Four tiers of Istio support.

AceMQ offers Istio support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for a mesh your platform team runs, proactive reviews that catch proxy version skew, STALE proxies and policy drift first, and managed Istio, where AceMQ operates the mesh day to day and quotes the scope per estate. Vendor builds, FIPS builds and backported fixes stay with the vendor in every tier.

  • Tier 1

    Istio 24/7 Support & Incident Management

    Your platform team runs Istio, we assist

    Best for: Teams operating a mesh who want an engineer reachable for 503s, injection failures and denied traffic.

  • Tier 2

    Istio 24/7 Support with Proactive Monitoring

    Planned reviews of revisions, proxies and policy

    Best for: Teams that want proxy version skew, STALE proxies and policy changes examined before an upgrade or an incident.

  • Tier 3

    Managed Istio on Your Infrastructure

    We operate Istio on your clusters

    Best for: Enterprises that keep clusters in their own accounts or sites and want AceMQ running the mesh day to day.

  • Tier 4

    Fully Managed Istio on AceMQ Infrastructure

    AceMQ runs the mesh for you

    Best for: Teams that need a working mesh without staffing a specialist team for the control plane.

FAQ

Istio support questions

Still have questions about Istio? Email an Expert

Who provides enterprise support for Istio?

Istio is open source: its community provides patch releases and technical assistance for each minor until 6 weeks after the N+2 minor ships (istio.io, read 19 November 2026). Vendors sell subscriptions, among them Tetrate, Solo.io, Red Hat for OpenShift Service Mesh and Google Cloud for Cloud Service Mesh. Independent providers such as AceMQ offer Istio enterprise support beside a subscription or on its own, 24/7, with response targets from 15 minutes, by plan.

Why am I getting intermittent 503 errors between services in my Istio mesh?

Start with the Envoy response flag in the istio-proxy access log. UF means the upstream connection failed, NR means no route, UO means circuit breaking. A 503 that begins when a DestinationRule is applied points to a TLS mode that does not match the mesh's mTLS setting, because an unset mode defaults to DISABLE. We read the log, then istioctl proxy-status and the rule, and fix the mismatch.

Which Istio versions does AceMQ support?

We support operations on minors inside the project's window. On 19 November 2026 the Istio page marked 1.32, 1.31 and 1.30 as supported and 1.29 as not (istio.io, read 19 November 2026). Older meshes are triaged and kept running while we plan the move to a supported minor. We cannot supply fixes the project no longer releases.

Can AceMQ support our Tetrate, Solo.io or Red Hat service mesh, or do we have to switch to upstream?

No switch is needed. The vendor supplies its build, fixes and any FIPS or long-term-support features. We handle why traffic failed, how policies, gateways and revisions should be configured and what the upgrade order is. AceMQ is independent of these vendors and does not resell or certify their products.

Does AceMQ provide FIPS builds or backport fixes for Istio versions the project no longer patches?

No. AceMQ ships no Istio distribution, no FIPS builds and no backports. Where a compliance rule needs a FIPS-verified build or a longer version life, a vendor subscription supplies it, and we can compare it with an upstream cadence of revision-based upgrades before you buy.

Can we use AceMQ for Istio without an annual contract or leaving our vendor subscription?

Yes. Keep a Tetrate, Solo.io, Red Hat or Google subscription and add AceMQ for the gaps, such as diagnosis at odd hours or upgrade planning. You can also hire us for one project, like an Istio health check, with no annual commitment.

What drives the price of Istio support?

Annual contracts typically run $24,000 to $72,000 (USD). Inputs are the number of clusters and namespaces in the mesh, sidecar or ambient mode, gateways, multicluster layout and your response plan. Describe the mesh in a quote request and we respond within 1 hour.

Let's talk

Send Us the Output of istioctl proxy-status

Tell us the Istio versions, whether you run sidecar or ambient mode and how many clusters carry the mesh. We reply to quote requests within 1 hour.

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

Production incident right now?Email an Istio Architect