Unrealistic Inbound API Response time from ServiceNowSummaryLet's say you are making an inbound API request (could be either SOAP or REST) to your ServiceNow instance. Ideally, the response time depends upon many factors as below: - Size of the payload that's been requested with the API - server processing time- network latency - third-party dependencies (like proxies, VPNs in between etc) So, a delay in any one of these factors may cause delays in the overall response time from ServiceNow. A few of our customers reached us regarding a requirement that the response time should be less than 500 milliseconds (ms). This is not a realistic response time. Ideally, even a ping request to the instance (in the cloud) takes 250 - 300 ms. Aiming for such, by excluding various factors causing this response time is not achievable. Reason: Ideally, for an API request to reach the instance, it has to go through multiple layers of security checks in the cloud. Pinging a publicly available website may take 20 - 40 ms. However, cloud-hosted platforms like ServiceNow usually take at least 200 ms. A realistic expectation is to achieve a minimum response time of 2000 ms for an inbound API request, considering additional factors like the SSL checks, table API, BR checks, ACL checks etc. So, expecting <500 ms is unachievable for a ServiceNow inbound REST/SOAP API. Reach ServiceNow Technical Support for any further queries.