You can always check directly within the API itserlf by logging "httpRouting.latency" variable content right after your HTTPS Routing call, which will give you "backend" response time.
What you're saying here is that you get average 7s backend processing time, with a defined read timeout of 30s, which on the configuration part, is correct.
FYI we have some SAP backends which can take up to 40s, depending on what's being done as per defined business process.
Now question being it normal or not, that's up to backend's developpers :)
We had some very bad response times coming from ServiceNow API calls (>120s), but increasing processing power at SNow's end resolved it.
Original Message:
Sent: 01-02-2020 12:07 AM
From: Kim CHEOL SU
Subject: Check for response time
Our client company uses the following settings for route via http(s):
Connection Timeout (in milliseconds) : 10000
Read Timeout (in millionseconds) : 30000
However, when the results of API calls are confirmed by the Dashboard, the maximum response time for the back end is often more than 7 seconds.
I wonder if this is a normal situation.