Apigee support

Apigee Support for Apigee X, Hybrid and Edge API Programmes

Last reviewed by Tyler Eastridge

AceMQ supports Apigee 24/7 across Americas, EMEA and APAC on Apigee X, Apigee hybrid and Apigee Edge. Most calls start with one of three problems: proxies that add latency before rejecting a bad request, quota and spike arrest policies applied at a scope that never protects the backend, or TLS and token failures after a certificate rotation.

AceMQ supports the API programme you run on Apigee — proxy revisions that fail validation on deploy, quota and spike arrest applied at a scope that never protects the backend, policy order that spends work before rejecting a bad token, and target server TLS handshakes that break on a certificate rotation. Every ticket reaches a named senior engineer.

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

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

Seven gateway symptoms, each paired with the first place an engineer looks: a Debug session, a policy's scope, a truststore or a KVM.

Common Apigee production problems and how AceMQ resolves them
Symptom you're seeingWhat we check first
A 401 costs as much as a 200Open the Debug session trace and look at policy order in the proxy endpoint pre-flow. Spending a ServiceCallout or JavaScript policy before VerifyAPIKey or OAuthV2 wastes work on every rejected call.
Quota configured, backend still overwhelmedCheck whether Quota is counted per app, per developer or per proxy, whether the identifier is set, and whether SpikeArrest sits ahead of the target. A Quota with no identifier counts everyone together and a spike arrest rate of 10ps is actually enforced as one request every 100 milliseconds.
Target TLS handshake failures after a certificate changeCheck the target server's TLS settings, the truststore and keystore references in the environment and the certificate chain. Mutual TLS adds a client certificate that expires on its own schedule.
A shared flow or KVM lookup fails after a migrationCheck the environment scope of the shared flow, the flow hook binding and the KVM's scope (environment, proxy or organization). A lookup that worked at one scope silently returns empty at another.
Latency after turning on message loggingCheck the MessageLogging policy's synchronous or asynchronous setting and whether the logging endpoint is slow. A slow Syslog or HTTP logging target slows every request.
OAuth tokens rejected intermittentlyCheck token expiry, clock skew between components, the cache policy's TTL and whether tokens were revoked. Cached verification results can outlive a revocation.
Analytics lag or gapsCheck the environment's analytics pipeline status, the proxy's data collectors and the time range in the report.

After a P1 you receive a written analysis naming the policy, scope or certificate at fault and the change that stops a repeat.

Partner calls failing at the gateway right now? Request a quote and an Apigee engineer answers inside the hour.

Contact Us

Deployment coverage

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

DeploymentWhat AceMQ coversWhat Google coversExcluded
Apigee XProxy and policy design, shared flows, quota, security, debuggingGoogle runs the platform under your Google Cloud support packageGoogle's service faults
Apigee hybridThe same, plus Kubernetes runtime behaviour, certificates and connectivity to the management planeGoogle for the control plane and productYour Kubernetes control plane
Apigee Edge (Public and Private Cloud)Proxies, policies, operations and migration planningGoogle per its support terms for EdgeProduct defects
Backend targets on AWS, Azure or on premisesConnectivity, TLS and timeouts as seen from the gatewayNot applicableThe backend application itself

Support options

Google support or independent support?

Apigee support is delivered through Google Cloud Customer Care. Google's Apigee Support Services Guide says Standard, Enhanced and Premium support packages include Apigee as a component of the support fee, and that some Enhanced services, including Assured Support, are not available for Apigee.

Google Cloud Customer Care for Apigee
AceMQ independent support
PlansStandard, Enhanced and Premium packages include Apigee
PlansOne contract, plan set by SLA
ScopeProduct and platform behaviour
ScopeYour proxies, policies, shared flows and design
PricingSet by the Google Cloud package; not Apigee-specific
Pricing$24,000 to $72,000 a year (USD), by SLA, scope and deployment

What's Included

Everything in your Apigee support contract

Proxy bundles, shared flows, target servers and the certificates between them are in scope, whether the runtime is Apigee X, hybrid or Edge.

  • 01

    Emergency Incident Response

    Proxies failing, deploys blocked, backends saturated, or authentication rejecting valid traffic. 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 policy, quota, or deployment change that prevents recurrence. Delivered as standard, not on request.

  • 03

    Policy Design & Latency Tuning

    Reordering flows so cheap rejections run first, replacing service callouts with cached lookups, trimming JavaScript and message payload handling, and cutting the overhead the gateway adds per call.

  • 04

    Traffic Management & Protection

    Quota, spike arrest, and concurrent rate limit applied at scopes that genuinely shield your backends, plus fault handling that returns useful errors instead of leaking internal detail.

  • 05

    Security & Token Handling

    OAuth 2.0 and JWT verification, API key management, mutual TLS to targets, truststore and certificate lifecycle, and threat protection policies configured without breaking legitimate payloads.

  • 06

    Migration & Platform Moves

    Edge to Apigee X or hybrid migration planning and execution — proxy bundle porting, shared flow and KVM re-scoping, target server and TLS rework, and parallel-run validation before cutover.

Why AceMQ

Why API teams keep us beside Google Cloud Customer Care

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your proxy bundles, your shared flows, and your target topology — so a P1 call starts with diagnosis, not twenty minutes of you explaining your API estate.

  • 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 Layers Google Support Won't

    Google operates the Apigee platform. Your proxy bundles, policy design, quota scoping, target configuration, and the backends behind them are yours — and that is where API incidents actually originate.

  • We Follow the Call Into the Backend

    The gateway is where the error appears; the backend is usually where it starts. We diagnose across the target service, its database, and the message broker behind it rather than stopping at the proxy boundary.

  • 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 reviews of proxy latency, policy overhead, quota effectiveness, and certificate expiry — so a truststore rotation is a calendar item rather than a Saturday incident.

Apigee runtimes we work in

Managed Apigee X, hybrid runtimes on your own Kubernetes, older Edge installs, and backends that sit behind private networks or restricted egress.

  • Apigee X
  • Apigee hybrid
  • Apigee Edge (Public & Private Cloud)
  • Google Cloud (GKE) runtime
  • Kubernetes & OpenShift
  • AWS-hosted backend targets
  • Microsoft Azure-hosted backend targets
  • Multi-environment & environment groups
  • Mutual TLS to targets
  • On-premise backend integration
  • Air-gapped / restricted egress backends
  • Hybrid cloud

Version coverage

Apigee platforms we support

Apigee platforms we support
PlatformWhat we do on it
Apigee X24/7 support and new-programme design
Apigee hybrid24/7 support, runtime and certificate operations
Apigee Edge24/7 support and migration planning to Apigee X

Escalation Path

Your first hour of an Apigee outage

Whoever answers has read proxy flows before, so we open with the Debug trace and the deployed revision rather than a questionnaire.

  1. From 15 min (by plan)first responseEmergencyProduction down: every proxy returns errors, a revision will not deploy, or the runtime has lost its connection to the management plane
  2. 1 hourfirst responseCriticalSevere impact: valid tokens rejected, target TLS handshakes failing after a certificate change, the backend flooded despite quota
  3. 4 hoursfirst responseHighLatency added by callouts or synchronous logging, shared flow or KVM lookups returning empty after a move, analytics gaps
  4. Next Dayfirst responseStandardQuestions on policy design, quota scoping, environment groups, Edge to X planning and certificate calendars

A rejected partner token at 2 a.m. and a policy design question on a Tuesday are on different clocks, set by your plan.

Prefer a named engineer who already knows your proxies? Ask for a quote or write to us.

Contact Us

Pricing

What does AceMQ Apigee support cost?

An Apigee support contract usually costs between $24,000 and $72,000 a year. The figure moves with the platform (X, hybrid or Edge), how many environments and proxies carry production traffic, and the response plan.

All prices are in US dollars (USD). Response targets begin at 15 minutes by plan, around the clock, and we answer quote requests within 1 hour. Adding other gateway or messaging tools to the same contract earns a multi-technology discount.

Support In Practice

Gateway faults we have traced to their source

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

All use cases

Support options

Four tiers of Apigee support.

AceMQ offers Apigee support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for the API programme your team runs, proactive monitoring that finds quota, policy and certificate problems first, managed Apigee in your own Google Cloud project, and the pipelines and monitoring around Apigee run on AceMQ infrastructure. X, hybrid and Edge are covered.

  • Tier 1

    Apigee 24/7 Support & Incident Management

    Your team owns proxies, we take hard calls

    Best for: API teams that maintain their own bundles and want a senior engineer for the faults Debug alone does not explain.

  • Tier 2

    Apigee 24/7 Support with Proactive Monitoring

    Scheduled reviews of policy, quota and certificates

    Best for: Programmes where a lapsed target certificate or a mis-scoped Quota should show up on a calendar, not in an incident.

  • Tier 3

    Managed Apigee on Your Infrastructure

    We operate your hybrid runtime and proxy estate

    Best for: Organizations running Apigee hybrid on their own Kubernetes that want day-to-day operation handled by specialists.

  • Tier 4

    Fully Managed Apigee on AceMQ Infrastructure

    We run the gateway layer as a service

    Best for: Teams that want proxies, quotas and certificates kept in order without staffing gateway operations in-house.

FAQ

Apigee support questions

Still have questions about Apigee? Email an Expert

Who provides enterprise support for Apigee?

Google supports the Apigee platform through Cloud Customer Care. AceMQ is the independent option for what you build on top: proxy bundles, policy order, quota scope, shared flows and target configuration, which is where most API incidents start.

Why is the backend still overwhelmed with quota configured?

Quota counts over a period and per identifier, while spike arrest smooths bursts. Without a correct identifier or a spike arrest ahead of the target, the backend sees the burst.

Can you help with an Edge to Apigee X migration?

Yes: inventory proxies and policies, map unsupported features, test in X and cut over in stages with a rollback.

Why did the proxy slow down after enabling message logging?

A synchronous or slow logging target. We switch to asynchronous logging and fix the endpoint.

Do you support Apigee hybrid on our Kubernetes cluster?

Yes, including runtime, certificate and connectivity problems.

How do I debug a proxy that rejects valid tokens?

Use a Debug session, then check token expiry, clock skew and cache TTL.

How fast do you respond to an Apigee outage?

Responses start within 15 minutes on the top plans, at any hour. In a Sev 1 where every call through a production proxy fails with a TLS error after a target certificate change, an engineer joins a bridge, checks the truststore and the Debug session, and writes up the cause. P2 is 1 hour, P3 4 hours, P4 next business day.

Can we start with a single Apigee project instead of a yearly contract?

Yes. Many teams begin with a bounded piece of work, such as an Edge to X migration plan, a quota redesign or a hybrid certificate rotation, and move to an annual agreement with 24/7 cover once they see how the engineers work. Both routes are quoted per scope.

What drives the cost of Apigee support?

Most contracts land between $24,000 and $72,000 a year (USD). Pricing follows the platform you run, the number of environments and environment groups with live traffic, whether hybrid runtime operation is included, and the response plan. Send us the details and a quote comes back within 1 hour.

Let's talk

Every Partner Integration Runs Through Your API Gateway

Tell us your Apigee platform and the proxy that fails. We reply with a quote within 1 hour.

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

Production incident right now?Email an Apigee Architect