Ingress-NGINX · #k1
Installs keep serving traffic but stop receiving security fixes
Vendor's words: “no further releases, no bugfixes, and no updates”
↳ Kubernetes blog — Ingress NGINX retirement ↗ · verified 2026-08-28
The gateway failure register
Ten documented ways API gateways fail in production — each one dated, cited to the vendor's own documentation, and stable enough to link. Selected from an internal audited register of 41 rows across five platforms.
How to read a row: the symptom is what operations sees; the quote is the vendor's own words; the capture date is when we last verified the source. If a row stops being true, we retire it — a register you cannot trust is worse than none.
Gateway API migration · #k3
Migration silently loses request-size enforcement
Vendor's words: “proxy-body-size has no Gateway API equivalent”
↳ Kubernetes blog — ingress2gateway 1.0 ↗ · verified 2026-08-28
Gateway API · #k5
“Conformant” does not mean feature-portable between implementations
Vendor's words: “conformance is claimed per Route type and Profile”
↳ Gateway API — Implementations ↗ · verified 2026-08-28
Kong Gateway · #g1
Rate limits silently multiply by node count during a Redis outage
Vendor's words: “the plugin will fall back to local rate limiting”
↳ Kong — Rate Limiting Advanced ↗ · verified 2026-08-28
Kong Gateway · #g2
The cluster strategy cannot be used where teams most expect it
Vendor's words: “Not supported in hybrid mode or Konnect deployments”
↳ Kong — Rate Limiting Advanced ↗ · verified 2026-08-28
Azure API Management · #a1
At capacity the gateway degrades instead of shedding load
Vendor's words: “it will act like an overloaded web server”
↳ Microsoft Learn — APIM capacity ↗ · verified 2026-08-28
Azure API Management · #a2
Capacity dashboards are misread as traffic dashboards
Vendor's words: “not direct measures of the number of requests”
↳ Microsoft Learn — APIM capacity ↗ · verified 2026-08-28
Amazon API Gateway · #w1
Request and response bodies vanish from the audit trail
Vendor's words: “log events larger than 1024 bytes… will be truncated”
↳ AWS — API Gateway important notes ↗ · verified 2026-08-28
Amazon API Gateway · #w3
One noisy API throttles every other API in the account
Vendor's words: “is not a quota that a customer can control”
↳ AWS — API Gateway quotas ↗ · verified 2026-08-28
MuleSoft Anypoint · #m1
The usage-based bill is set by one peak hour, not by average load
Vendor's words: “the highest number of flows that exist in a single given hour”
↳ MuleSoft docs — usage metrics ↗ · verified 2026-08-28
What this register is for
These ten rows are public. The full 41-row register — applied to your estate, with your ceilings measured and a runbook you keep — is the fixed-scope assessment we deliver.
Score your own exposure (free self-assessment) → Fixed-scope assessments →