The User Diagnostic Data tool enables you to gather diagnostic data from users experiencing similar issues with specific URLs or IP acceleration hostnames.

The tool generates a link for you to share with the users. After they click the link, the tool gathers the necessary data for users to submit. All submitted IP details of client and edge servers are stored in the application.

Also, User Diagnostic Data runs further diagnostics for the collected data using the Test Network Connectivity (MTR), Request Content (CURL), and Get Domain Details (DIG) tools.

Generate a diagnostic link

Learn how to create a diagnostic link in the User Diagnostic Data tool.

Go to ☰ > SUPPORT > Edge Diagnostics.
In the side menu, select > User Diagnostic Data.
In the URL field, enter a URL or IP acceleration hostname with issues.
Optional: Enter a Note about the entered URL and issues experienced by its users.
Click Generate.
The tool generates a diagnostic link.

Next steps
Copy the generated link and send it to users who are experiencing issues with the URL. Once they click the link, the tool will gather all necessary diagnostic data and ask the users to submit them. When submitted, you can check the collected data in the application by clicking the URL's row in the Recent requests table.

Recent requests table

The Recent requests table contains all URLs for which users of your account wanted to gather the data. Click in the table's corner to filter your requests.

Link status

In the Link status column you can check the status of the link:

Active. Users can submit their data. To send the link to more users, click and paste it in the communication with them.
Used. Fifty users submitted their data. You can’t gather more data for this URL.
Expired. The link was generated more than 7 days ago.

Results

At the top of the page you have the summary about the generated link.

Collected diagnostic data

This table contains data collected from users of the URL or IPA who submitted the data.
Click in the table's corner to select which data you want to see.

Possible options are:

UID. Unique ID of the user.
UTC timestamp. Date when the data was submitted. Can be used later on to get the logs for this time.
Client IP (Preferred). IP address preferred by the client to connect to the server.
Epoch timestamp.
User agent. Information about the user browser.
Cookie. Whether the user browser allows for storing cookies.
Protocol. The HTTP protocol used to connect the client and the Tier 1 diagnostic site, www.t1info.net.
Connected cipher. The cryptographic algorithm used between the client and the Tier 1 diagnostic site, www.t1info.net.
Client DNS IPv4. IP address of the DNS server used to serve edge IPv4 addresses.
Client DNS IPv6. IP address of the DNS server used to serve edge IPv6 addresses.
Client IPv4. Client’s IPv4 address used to connect to the edge server.
Client IPv6. Client’s IPv6 address used to connect to the edge server.
Edge IPs. IP addresses of edge servers serving the traffic between the client and the user.

Additional data for IPs

If the User Diagnostic Data tool was able to collect a DNS IP, and therefore an edge server IP, then the tool runs also Request Content (CURL), Get Domain Details (DIG), and Test Network Connectivity (MTR) tools for the IP. To check this data, in the Additional data for IPs (CURL, DIG, MTR), click View, next to an IP address.

View data screen

The results shown are for the requests with default data. If you want to edit the request data, click , edit the data, and click Submit.

To learn more about the results check Request Content (CURL) results, Get Domain Details (DIG) results, and Test Network Connectivity (MTR) results.

If the User Diagnostic Data tool was unable to determine the edge IP of the collected data, you'll see the message: Edge IP is not shown either because of a system error or the client DNS has an EDNS Client Subnet (ECS).