Skip to Main Content

This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Workspace DataPower Gateway
Created by Guest
Created on Dec 13, 2022

Improving Rate limit for APIConnect Gateway cluster

Currently the rate limit across the DP GWs in a peering group(3 DPs in a peer group in the same Data Center/Availability zone) for APIConnect GW is working as expected for longer intervals. For example, if the interval is 10 seconds and the ratelimit is 100 then it works with intended accuracy. In case if the interval is very less like 3 seconds and the threshold is 100 transactions, then the rate limiting at APIConnect is not so efficient. Increasing the interval is not going to solve our situation where we want to restrict 100 transactions per 3 seconds.

We had a detailed discussion with IBM representatives about this and understood that the sampling across the peers(Primary and Secondary) should happen twice within the interval to reconcile for the rate limiting to work efficiently.

Now, our suggestion is that the technique or the way the rate limiting is being done currently has to be improved in such a way that it is still able to handle higher TPS for very short intervals. These are very essential for the APIs that are created to cater regulatory and compliance requirements set by the authorities.

CASE - TS009701873, we created this case to debug a different issue but later we also had a discussion about the above mentioned concept and issues as well over a webex call.

Idea priority High
  • Admin
    Ulas Cubuk
    Mar 16, 2023

    Hi Hari,

    Thank you for taking the time to raise this enhancement request. As of, all rate limits are by default scale limits, which should have no problem with 100 transactions / sec in one data center as long as their data center has reasonable latency between nodes. Status of the idea is updated to Delivered but if you observe a problem with 100 transactions / sec in one data center then please feel free to open a support ticket or if you require additional rate limiting enhancement please open a new idea.