Print this checklist and use it to verify that you have provided all required information before submitting your trouble ticket. Please provide the information listed in the Basic Ticket Checklist section and the checklist for the affected service.
Please provide all of the following information for each new ticket.
Checklist | |
---|---|
|
Issue type (i.e., Latency, Availability, Failure To Connect, etc.) |
|
Issue description |
|
Occurred at (Date and Time) |
|
Possible cause |
|
Information on how to reproduce the issue |
|
Number of affected customers (approximately) |
|
Affected geographical area |
|
Sample URLs |
|
Status code(s) associated with the issue (if applicable) |
|
Screenshots |
In addition to the information requested in the Basic Ticket Checklist section above, please provide as much of the following information as possible.
Checklist | |
---|---|
|
Mtr or traceroute information from the computer experiencing the issue to:
Prevent hostnames from being truncated when generating a mtr report by passing the -w or --report-wide flag. Packet Loss Run a mtr with at least 100 pings. Complicated packet loss issues may require 1,000 pings. Example: Use one of the following requests to generate a 100 ping TCP mtr to can.0001.transactcdn.com: mtr --report-wide --show-ips --tcp --report --report-cycles 100 can.0001.transactcdn.com
mtr -wbTr -c 100 can.0001.transactcdn.com
|
|
Request/response headers |
|
DNS-Related Issue: The results of a dig for the hostname associated with the request experiencing issues. This information is also useful when diagnosing an issue with HTTPS data delivery. |
|
Affected region (if known) |
In addition to the above information, please provide as much of the following information as possible when creating a ticket for slow data delivery.
Checklist | |
---|---|
|
Indicate the IP address of the client experiencing suboptimal performance. A computer's IP address can be determined by visiting the following web site: |
|
Perform and provide the results of a speed test
|
|
Duration
|
|
Indicate the number of affected customers |
|
The results of a waterfall (if available) |
|
Indicate how suboptimal performance is being measured. |
In addition to the information requested in the Basic Ticket Checklist section above, please provide as much of the following information as possible when creating a ticket for an issue with log data or a report.
Checklist | |
---|---|
|
The type of data that is missing or malformed |
|
The time period during which the issue was detected |
In addition to the information requested in the Basic Ticket Checklist section above, please provide as much of the following information as possible when creating a ticket for a REST API issue.
Checklist | |
---|---|
|
Describe the request:
|
|
Describe the response:
|
Edgecast CDN