Skip to content

Kong Rate Limiting Advanced Not Enforcing Second Limits

DodaTech Updated 2026-06-24 2 min read

You encounter a kong configuration issue that prevents your workflow from completing. This guide walks through the fix step by step.

Wrong ❌

curl -X POST http://localhost:8001/routes/my-route/plugins --data "name=rate-limiting-advanced" --data "config.limit[]=100" --data "config.window_size[]=60" --data "config.sync_rate=-1"

Wrong Output

Rate limiting advanced accepts config but only enforces minute limits. Second-level limits not working.

curl -X POST http://localhost:8001/routes/my-route/plugins --data "name=rate-limiting-advanced" --data "config.limit[]=10" --data "config.limit[]=100" --data "config.window_size[]=1" --data "config.window_size[]=60" --data "config.sync_rate=10" --data "config.namespace=my-namespace" --data "config.strategy=local"

Right Output

Rate limits enforced: 10 req/s, 100 req/min. Sliding window works correctly.

Prevention

  • Use paired limit[] and window_size[] arrays for each window.
  • Set sync_rate to a positive value (10) for counter synchronization.
  • Use a unique namespace to avoid key collisions across services.
  • Choose strategy: local for single-node, redis for cluster.
  • Test with load testing tool to verify both windows.

DodaTech applies similar defensive patterns across Doda Browser, DodaZIP, and Durga Antivirus Pro infrastructure for production reliability.

Common Mistakes with rate limiting advanced

  1. Forgetting deriving (Show, Eq) on custom data types needed for debugging
  2. Placing the wildcard pattern first in case expressions, making all subsequent patterns unreachable
  3. Using head and tail instead of pattern matching, causing runtime errors on empty lists

These mistakes appear frequently in real-world KONG code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

**Q: What is the most common cause of this kong error?**

A: Configuration drift between environments and version mismatches are the top causes. Always verify both before deeper troubleshooting.

Q: Can this error affect production traffic?

A: Yes. Depending on whether it occurs in the control plane or data plane, it can block all traffic or cause silent failures.

Q: How do I monitor for this error in production?

A: Set up log-based alerts for the error signature shown above. Most monitoring platforms support pattern matching on log entries.

Q: Is there a quick rollback procedure?

A: Revert the configuration change and restart the service. For data-plane errors, replay affected records from the source of truth.

This quick fix is part of the DodaTech infrastructure engineering series. Learn more at DodaTech tutorials.

← Previous Kong Proxy Cache Never Caches Next → Kong Request Transformer Not Applied

Built by the developers of DodaTech

Doda Browser, DodaZIP & Durga Antivirus Pro

Home Browse Quick Fix