Hi, @brycewray, we don’t have any visibility into what that test is doing. To troubleshoot the issue, we need some way to identify the problematic responses.
The simplest way for us to track HTTP responses is using the x-nf-request-id header which we send with every response.
There more information about this header here:
If that header isn’t available for any reason, please send the information it replaces (or as many of these details as possible). Those details are:
- the complete URL requested
- the IP address for the system making the request
- the IP address for the CDN node that responded
- the day of the request
- the time of the request
- the timezone the time is in
Once we have more details, we’ll be happy to research the issue. Please let us know if there are any questions and reply anytime.