The Google HTTP test probes the connection to the Google search service. As the google service is generally always available and responds fast it is a good indicator for general issues with the HTTP protocol. It is also a good sign for proxys or other network components that might block the access to the service.
|Number of measurements||10|
Locate the issue
There are different possible causes for Google HTTP issues. Therefore, narrow down where and when issues occur. Use the general troubleshooting guide and try to answer these questions:
- Is it a client-specific, local or global issue?
- Are there other clients with similar issues?
- Are there other possibly related services with issues?
- Are performance issue maybe caused by local connection issues or device performance issues?
- Do other HTTP tests show similar patterns?
- Are there performance changes over time?
- Did the connection look better in the past? Are there any patterns?
If you find other services with issues also look at their test documentations.
Possible causes (status warning/critical):
The HTTP protocol uses TCP packets. If those packets are routed over many network hops (e.g. proxy server), the latency increases. Microsoft recommends to use a local breakout, a proxy bypass and no deep inspection for such packets.
- Check if the packets are routed properly (according to Microsofts recommondations) and adjust the settings on the firewall, proxy, etc.
High bandwidth usage
If the bandwidth usage is high the HTTP tests notice it first. As Google is quite reliable, issues with the performance likely indicate local issues.
- Check if other HTTP tests show similar high latencies. A high bandwidth usage impacts all services that use HTTP.
- Check if other clients at the same location have similar HTTP issues.
- Check if the latency changes over the day.
Although this is unlikely, it is still possible that the Google server in your region are congested.
- Check if you have many clients (maybe even in different locations) with issues reaching Google to verify this.
Possible causes (status error):
A proxy or firewall might block the requests from Rimscout to Google. To test the connection properly, consider unblocking those requests.
- Check the proxy logs or the firewall for packets to
https://www.google.comand consider unblocking them.
If the operating system uses an HTTP proxy, the packets of this test use this proxy as well.