Uptime.com Reporting

Reports are accessible at all times from either your Dashboard, or from each check. An Uptime Report is a measure of downtime and associated incidents for a given period of time, for an individual check. 

The Uptime Report differs from Alerts, which focus more on downtime causes, or the Audit Log, which shows major changes to a check or your account.

Table of Contents

Elements of an Uptime.com Report


The Uptime Report has four major areas to be aware of:

We’ll look at each area in detail below.

Selecting Dates for Reporting


By default, the Uptime Report screen displays incident and performance data for the past 24 hours. Users can click the Date field to fill in specific dates, or use one of the presets on the right-hand side.


Uptime Reports provide detailed downtime and alert data and allow you to review past historic data for a period of time you’ve selected. Use this report to compare outages for a given period of time, track improvements, or to view uptime for the month or year.

Performance Graphs


Response time metrics are calculated based on your check configuration:

  1. HTTP Check without a String to Expect:  time to receive 200 OK
  2. HTTP Check with String to Expect: Time to fully load the HTML only (no css, javascript, images, etc. which we don't load at all)
  3. Transaction Check: Time to fully load the page, all images, and run initial javascript, etc. Response time is a measure of all steps. 
  4. API Check: Time to run through all steps within the API check. Steps may include resolving status, making a request or receiving a response.

Response time is heavily dependent on location. For example, a probe server in Australia will typically see a higher response time connecting to a server based in New York than a probe based in the US. 

There are two performance graphs within Uptime Reports. The first visualizes response time as a line graph, which measures average response across all locations (you may also filter by location). 

The second is the Alert Log, a color-coded bar to visualize up and down time. If your bar is grayed out, or not filled in, Uptime.com does not have data for this period.

Important data retention limits to keep aware of include:

  • Metric data is retained in 15-minute intervals after 30 days
  • Hourly data is retained for a maximum of 90 days depending on your account plan
  • Daily aggregated data is retained for a maximum of two years depending on your account plan




Outage Representation on Response Time Graphs

In addition to the color coded Alert Log, outages are also represented by a light red overlay over the response time graph for the period the check was reported down.

The light red overlay will correlate the time and date of the alert, as shown in the alert log. Once the check returns to an UP state, the overlay will still be visible for the downtime period when changing the time frame of the view.

Uptime.com report.png

Color-Coded Graphs

Uptime.com uses three color-coded graph types, found on the Dashboard and Checks screen, to indicate the severity of performance issues. Graphs are based on the calculated Target SLA%, and SLA Response Time Values that have been configured for each check.

  • Blue: the check is below any thresholds that indicate a performance issue



  • Orange: the check performance is above the Blue threshold, which may indicate degraded performance.


  • Red: Response time is considered high for this check type, and performance is above the Orange threshold. We recommend investigating red color coded graphs for performance issues.



A check, check card, or response time graph changes its color coding when the average of these graphs meet the following thresholds:

Target SLA % 

> Above the Target SLA % (Blue)

> Halfway to Target SLA % (Orange)

> Below the Target SLA % (Red)

Example: If the Target SLA% is 90%, the graph will be Blue 100%-95%, Orange 94.99%-90%, and Red at or below 89.99%.

Target Response Time SLA (secs) 

> Below 70% of Target Response Time SLA (Blue)

> 70% - 100% of Target Response Time SLA (Orange)

> Above 100% of Target Response Time SLA (Red)

Example: If the Target Response Time SLA is 10 seconds, graph will be blue 0-7s, Orange 7.01-10s, and Red above 10s.

Alert Log


The Alert Log on the Uptime Report contains information about the previous changes in status to the probe servers associated with your check. Use this space to determine when the probe status shifted from OK to CRITICAL, the reason for downtime and the duration of the downtime with some technical details to help summarize the issue.


Your account type determines how long alert data is retained. Please see the History Retention entry from your Account Usage page to see the specified time for your account type.

Note: Ignored Alerts will still be visible on the Check report’s Alert log section and labelled with an “Alert Ignored” badge. Ignored alerts are not included in downtime calculations.

unnamed (3).png

Please Note: deleted check alert data will be non-recoverable after 30 days.

Summary Sidebar


The sidebar on the right-hand side contains a summary of everything you will see in the Uptime Report. It’s not as detailed, but it provides an at-a-glance summary of what your reporting shows, as well as a link to your real-time analysis for the check.



The components of the sidebar can be broken down as follows:


Displays the current up/down status of the check, how long the check has been in its current state, and the date and time at which the check entered its current state.

In the above screenshot, the check has been in UP status for 2 weeks and 5 days, and its current UP status began on October 8 2021 at 6:04 p.m. BST.


The percentage of time that the check has been in the UP status in the selected date range. Note that this only counts actual monitoring time: if a check is paused or in a maintenance window, that time will not count toward this uptime calculation.


The percentage of time that the check has been in the DOWN status in the selected date range.


The most recent date and time that the check experienced downtime. In the screenshot example, the most recent downtime was on October 8, 2021 at 5:55 p.m. BST, and lasted 9 minutes.


You can install the Uptime.com Widget on your website, which allows your users immediate visibility into your website's uptime statistics.


NTP and Other Kinds of Reporting


NTP Reporting is slightly different from other reporting, in that the graph does not measure performance it measures offset with the network time protocol server. Note in this NTP check example that response time is well below the NTP fail threshold of 1,000 milliseconds:


Information on RUM Reporting can be found here. The RUM report will provide you with real-time data regarding the average page load from sites where a Real User Monitoring check was created.

Information on Status Pages can be found here. Status Pages provide the ability to display your uptime checks in a private status page or on a public URL. Users can also create SLA Reports, which allow organizations to report on specific checks or systems for the purposes of SLA accountability.

For Group Check reporting, see our article on Group Checks.

Share Report


Uptime.com allows you to share a specific check’s report externally. To do so, navigate to the specific check’s Report and select Share Report, then click the Copy Link option. By doing so, you will be able to provide the link to anyone who will be able to review the report only. 


Please Note: to enable this feature, confirm you have selected the checkbox found in Settings > Account Details. 


When viewing Shared Reports, use the Locations drop-down to view Response Time metrics for a single location, or use All Locations to view aggregated metrics:


Downloading Reports


To download any check's report, click Monitoring > Checks, locate the check you wish to download a report of, then click the "three dots" button, then Report. Click the blue Download button, and select between either XLS or PDF. Remember: set the date range accordingly (the default report screen displays activity for the previous 24 hours).


Please note: Check Reports are for individual checks, whereas SLA Reports are for multiple checks grouped together.

Scheduling SLA Reports

To schedule a SLA Report, click Reports > Scheduled Reports. Scheduled reports deliver a PDF or XLS document to either Uptime.com users or email address(es) you select. You may wish to add Uptime.com users specifically for the purpose of receiving this report, but it is also possible to send reports to external email addresses.  

Please note: A scheduled report can be sent to a maximum of 100 recipients (which includes both external email addresses and Uptime.com users within your account).


A weekly report is scheduled for all users for all checks by default. Reports can be scheduled or re-scheduled for delivery at the following recurrences:

  • Daily on the day and time you select.
  • Weekly, delivered at the date and time you select.
  • Monthly, delivered on the first day of the month at the time you select.
  • Quarterly, delivered on the first day of each quarter at the time you select.
  • Yearly on the first of each year, delivered at the time you select.

Final Thoughts


Uptime.com makes communicating monitoring results, metrics, and data easy with Reports. Schedule reports to be sent to key stakeholders at defined intervals, or download any given check's data in your preferred format whenever needed.

If you need any assistance, please reach out to support@uptime.com for help!

Was this article helpful?
5 out of 6 found this helpful



Article is closed for comments.

Have more questions?
Submit a request
Share it, if you like it.