---
title: "SLA reports (v2)"
canonical: "https://docs.aryaka.com/space/KNOW/1509471/SLA%20reports%20(v2)"
format: markdown
---
Customers who have version 2 (v2) of MyAryaka service level agreements (SLA) can now generate an Uptime SLA report from the SLA Reports page.  The concept of  site pair  reporting originates from the way sites are listed in the SLA Reports page's Uptime SLA table. The table's Sites column lists each site for which you have contracted an SLA. When you click a site name, the other sites paired with it appear nested below the selected site. These are the site pairs for which you have contracted an SLA. To generate an Uptime SLA report Log in to MyAryaka. The Home page appears. Click  Insights  >  Reports  in the left navigation pane. The Reports page appears. Click  Manage  in the SLA Reports tile. The SLA Reports page appears. Click the  Month  field and select the month for which you want to generate a report. By default, the current month is selected. Click  Apply . The selected month's SLA violations are displayed in the table's SLA Violations column for each of the following four categories: Core Uptime, Core Packet Loss, Core Latency, and Core Jitter. The SLA Violations columns display the number of SLA violations and the number of records associated with the violations in the following format: violations/records, for example 5/66. The total number of violations and records appears above the table. Click any site name in the Site column to expand it. The sites listed nested below the selected site are the  site pairs  for which you have contracted an SLA. When expanded, the following previously-empty columns display data: Date—Site pair report data is reported in 24-hour periods. This is the date that data was collected. Core Uptime Downtime SLA—The site pairs' service threshold in minutes. If the monthly outage is equal to or less than this value, the SLA is compliant. If this value is exceeded, it is considered an SLA violation. Total Downtime—Total end-to-end network outage in minutes for the monthly reporting period. Core Packet Loss Threshold—The site pairs' service threshold expressed as a percentage. If the monthly outage is equal to or less than this value, the SLA is compliant. If this value is exceeded, it is considered an SLA violation. Packet Loss—The actual percentage of packets dropped between the site pair in the current reporting period. Core Latency Threshold—The site pairs' service threshold in milliseconds (ms). If the monthly outage is equal to or less than this value, the SLA is compliant. If this value is exceeded, it is considered an SLA violation. Latency—The actual time in milliseconds for the site pairs' packets to reach their destination in the current reporting period. Core Jitter Threshold—The site pairs' service threshold in milliseconds (ms). If the monthly outage is equal to or less than this value, the SLA is compliant. If this value is exceeded, it is considered an SLA violation. Jitter—The actual time in milliseconds that the site pairs' connection experienced jitter in the current reporting period. Report Days—Number of days into the current reporting period. Reporting periods start on the first of the month, so if the current date is the 24th, this column displays 23. (Optional) Do one or more of the following: Click the  Download  icon to download a comma-separated values (CSV) or PDF file with all sites and their site pair SLA data to your computer. Click a  site name , then click the  PDF  icon or  CSV  icon to download the selected site's and its paired sites' SLA data to your computer. Click a  site name , a site pair name, and then click the  PDF  icon or  CSV  icon to download the selected paired site's SLA data to your computer. Related topics SLA reports (v1) SLA reports (v3)