Primo Uptime Report for Primo MT AP01 Instance (APAC) - Q1 2017
Primo Uptime Quarterly Reports are published each quarter to provide a comprehensive view of our uptime performance as measured over the last three (3) months and over the last twelve (12) months. The report measures our performance as defined in the Primo Service Level Agreement.
This document details the uptime report for the Primo MT APAC01 in APAC.
The Primo uptime measured on a rolling 12 month basis April 2016 - March 2017 is 99.814%
The Primo uptime measured on a rolling 3 month basis January 2017 - March 2017 is 99.839%
Please note our System Uptime Status page, which allows our customers to view the current status of their instance/environment at any time, using the following link: http://status.exlibrisgroup.com
Unscheduled downtime incidents in Q1 2017
| Date | Start time [SGT] | End time [SGT] | Duration | Description |
|---|---|---|---|---|
| January 11, 2017 | 3:41:18 PM | 4:16:17 PM | 35 | Ex Libris had identified a defect that is causing the system disruption. The defect is triggered in a specific search criteria. Theses search criteria are causing the Search Engines to stop working |
| March 14, 2017 | 10:44 AM | 12:25:07 AM | 101 | The service interruption was a result of an application defect that is causing a significant impact on the search engines and get them to a state in which they are not able to function, they consume all the available hardware and become unavailable. This defect is becoming evident when there is a significant load one the system, with conjunction to the hotswap. We have also identified that a system configuration is preventing us from restoring the service quickly once a situation as the above occurs. |
| March 22, 2017 | 10:20 AM | 10:32 AM | 12 | |
| March 22, 2017 | 11:06 AM | 11:16 AM | 10 | |
| March 30, 2017 | 6:29 PM | 6:52 PM | 23 | Ex Libris had identified a severe problem on one of the search engines. The specific search engine had stopped responding and caused service disruption to the entire environment. |
Scheduled downtimes during maintenance windows in Q1 2017
| Start Date | Start Time [SGT] | End Time [SGT] | Duration (Minutes) |
|---|---|---|---|
|
|
|
|
|
Total unscheduled downtime minutes during past 12 months
| Quarter | Total unscheduled downtime in Quarter (minutes) |
|---|---|
| Q2 2016 | 260 |
| Q3 2016 | 230 |
| Q4 2016 | 112 |
| Q1 2017 | 181 |
How is Uptime Calculated?
The uptime calculation is based on the following calculation (as defined in the Alma Service Level Agreement):
"Uptime" means the total period in minutes during which the Service is available for access and use during this period.
“Uptime Percentage” means Uptime expressed as a percentage, calculated in accordance with the following formula:
Uptime Percentage = X /(Y–Z) × 100
Where:
X = Uptime
Y = Last 12 months period
Z = The duration (in minutes) of any SLA Exclusions* during these 12 months
*SLA exclusions are defined in the contract SLA (e.g. Scheduled maintenance, etc.)
Further Information
If you have any queries on the information within this report please contact Ex Libris through your usual channel.