Undocumented Reduction in CF Org Quota Route Limits

[bmcdonn2]

Hello All,

I wanted to see if anyone has noticed or could provide insight into what I believe was a recent reduction to the default route limits for CF Orgs for Pay Per Use accounts.

Here's the situation, our main production org originally used 125 routes and we've never had any trouble adding new ones. We recently tried to add a new route and received an error stating we had exceeded the space route quota. I ran a quick check using the CF CLI and saw that sure enough, our org quota was 100. This struck me as a little strange as we were already 25 routes above that limit. To test whether we actually had an undocumented limit of 125 I removed one route and tried to re-add it. What I found was that I was again unable to add a route, leaving us now with 124 routes. This is when I first started thinking that there had been an undocumented reduction in the limit.

Pursuing this theory further, I tracked down a screenshot I took in February 2020 that seems to indicate a previous route limit of 500:

Adding to the problem, the route portion of the space tile was removed at some point between then and now. Here's what it looks like now.

Obviously, the quota information is available elsewhere, but having the route information present on the tile would have made it much more obvious that a change had taken place.

In terms of when I think this change may have occurred, the most recent time we successfully added a route (#125) was on October 6th and we first experienced this problem on October 16th so it must have been somewhere in that date range. I've consulted the change history (What's New in SAP Cloud Platform) and there doesn't seem to be any relevant entry for route limits there.

Support resources for this are fairly sparse, at least from a technical perspective. There are two notes which have some relation to this:

• 2659925 - Space quota issue in SAP Cloud platform - This note is more related to missing entitlements being assigned to a subaccount. Given that routes are not part of entitlements it is not relevant in our case.
• 2943576 - SAP Cloud Foundry deployment error: You have exceeded the instance limit for your organiza... - This note is a little closer to our problem as we use the Pay Per Use plan but it is mainly concerned about the standard 50 GB memory limit.

The resolution offered in the second note is to open an incident, which we have done.

Still, I wanted to reach out to the community on this because if the route quota was indeed reduced at the global level (as I believe it was), I think a discussion around this could be useful to others that might experience the same problem. Along similar lines, all previous discussions of this concerned trial accounts where this is concerned with productive, pay per use accounts.

I appreciate any comments!

Thanks,

Brian

[vbalko-claimate]

Hello Brian,

I didnt ran into that quota limit on our account, but it really interests me, so please share your findings and the result of ticket you opened. It is pretty important information to know and I (same as you) would expect to see that information somewhere easily accessible.

[bmcdonn2]

Update: The incident we filed did eventually help us solve this issue as SAP assigned a new org quota to our CF org with a higher route limit. We still do not have an explanation as to why the route limit was reduced in the first place but as of now it's a moot point.

[former_member194549]

Hi brian.mcdonnell,

have you been able to increase the quota of routes via ticket. We are currently facing the same problem and have also opened a ticket. So far we have only been told that we need to buy more runtime to get more routes.

Regards
Simon

[bmcdonn2]

Simon,

The same thing happened to us.

When we originally filed the incident, the initial response told us to reach out to our account executives to help resolve the incident. Those account executives then told us to increase our runtime purchase which didn't make any sense because we were on a pay as you go plan and used variable amounts of runtime as the apps scale-up and down. Anyway, I eventually convinced these account executives that this was a technical issue as, at the time, there was no line item on our bill that covers available routes.

Whether those account executives intervened or not, I don't know but we then received another response on the incident stating that the route limit was increased.

I believe what happened behind the scenes is that somebody with technical knowledge became involved with our incident, created a new quota with a higher route limit and assigned it to our org. My main evidence of this is that the quota assigned to our org has it's own custom ID rather than the standard PPU_QUOTA. Beyond that, everything is speculation.

I wish I could have offered a more direct way to resolve this but it seems that SAP has not improved their handling of this particular issue, despite receiving an assurance from our account executives at the time that they'd take my suggestions into consideration so that future requests like yours could be resolved much more expediently.

Thanks,

Brian

[gregorw]

Hello,

please check also this related post:

Operating a multi-tenant solution on BTP CF - 1 GB Runtime = 10 Routes

CU
Gregor

[Marco_Dorn · Accepted solution]

Dear brian.mcdonnell,

I was just made aware about your question and we discussed this in the product team for SAP BTP, Cloud Foundry runtime. The out-of-the-box limits were introduced as they typically are sufficient in customer use cases and they prevent mis-use like DDoS attacks. Nevertheless (to quote the second last bullet point of the SAP Help Portal😞 "This is a technical limit only, not a business limit. If you need to increase this limit, report an incident to SAP support for component BC-NEO-CIS."

Therefore, it's possible to get this limit increased.

Best regards,
Marco Dorn
SAP BTP Runtimes & Core

[bmcdonn2 · Accepted solution]

marco.dorn,

Thank you for responding to this question, despite it originally being posted in October 2020.

As you hopefully gathered from this title of the post, the original question was whether or not there was some undocumented change to the default route quota in the Cloud Foundry environment for individual CF orgs. The evidence I produced appeared to confirm that this was the case at some point in 2020. To this day more than 17 months later, I've never received any confirmation that the default route quotas were reduced from the originally observed 500 to the insufficient 100 as reported.

Despite these observations, I did follow the suggested procedure to file an incident and was able to eventually get the route quota increased but the ordeal involved an unnecessary detour through our account executives. The initial processor of our incident stated that only an account executive could assist with this issue which meant many days of us trying to explain the issue to a sales team that had little understanding of the actual issue where their eventual suggestion was to reach out to a more technical resource, which of course was what we initially wanted when opening the incident.

The main reason this issue has recently risen from the dead is because sperstorfer had the exact same issue and was given the exact same runaround through his account executives. I found this incredibly disappointing as one of my parting comments to our account executives back in 2020 was that they review their process for increasing route quotas because the process for us was incredibly stressful and I did not want anyone else to experience it. I was given an assurance that they would look into it. It seems that was not the case.

In either case, it seems that there is finally some visibility into this issue and it is my hope that further situations where a route quota increase is needed will not be met with a similar inconsistent and frustrating process involving both technical and account executive teams.

Thanks,

Brian

[former_member38684]

Hello,

we have also faced the issue with reaching the routes quota limit.

The solution which actually proposed with rasing the ticket either to entitle the Runtime Memory, in our opinion is not the most convenient way to handle it. Org Routes quota should be simply higher than it is now(100).

Therefor we create the Customer Influence for this topic: https://influence.sap.com/sap/ino/#/idea/288295

Feel free to vote or comment.

Regards

Grzegorz