When Uptime.com probe servers change status to either Up or Down, an alert is issued to any contacts that are associated with a check. All down alerts contain technical details about the incident, and root cause analysis (including screenshots) for Transaction and API checks.
Receiving an Alert
When you receive an alert, we recommend you first review it for technical details. Look for the error code and response time, as well as which probe locations are listed as “DOWN”. You will notice a link to the check’s Real-Time Analysis page, which you should also open and review.
Real-Time Analysis provides a chronological timeline of the events and alerts that have been issued to a particular check. It is designed for users with access to learn the state of an outage, and develop a timeline for the outage, with technical details for each step in the process.
Next, we suggest checking from your local terminal to see if the URL is responsive. Compare the error code Uptime.com has provided with the behavior in your browser. Check this document if your check is DOWN and you believe it should be UP. It is also helpful to test from a location outside of your work network if possible.
Tip: Use cURL commands for further analysis.
If your check is a Transaction or API check, we also suggest you review your Browser Console Log. This log is available within the alert, and on the check’s root-cause analysis (accessible from the check’s alert).
Finally, we suggest you review your internal logs for the Uptime.com user agent to see if and when Uptime.com probes were able to make a connection to your website.
If this process leaves any questions unanswered, we then suggest you reach out to firstname.lastname@example.org for further details.
Accessing Alert History
The Alert History page provides a list of the incidents that have occurred for each server and check type you’ve configured within your account. Click Reports>Alerts to reach the Alert History page.
Status of the check in real-time is indicated by a green or red status bar.
Locate the alert in question, then click Actions>View Details to view the full details of each incident.
Alert details contain the IP address of the probe server that encountered the error, as well as the location name. Details provide technical information about the alert, such as status code returned or the lack of an expected string. If response time is available, the alert details will also provide this information along with the size of the request.