Library Open Platform Performance and Uptime Report for EU00 Instance (Europe) - Q3 2025
General
Uptime and Performance Quarterly Reports are published each quarter to provide a comprehensive view of our uptime and system performance.
This document details the uptime and performance report for the Higher-Ed-Platform (Alma, Primo VE, Leganto, Esploro) EU00 in Europe.
Uptime is measured over the last three (3) months and over the last twelve (12) months.The report measures our uptime as defined in the Service Level Agreement.
System Performance is measured over the last three (3) months. The report measures our system performance for various products and in various system online activities such as UI screens and APIs.
Performance Report
The system performance as measured on the server side, on a rolling 3-month basis for July 2025 - September 2025:
| Product | Average (seconds) | 95% of all activity is faster than... (seconds) | What is being measured? |
|---|---|---|---|
 |
0.2 sec |
0.9 sec |
Staff user screens and online transactions |
 |
0.5 sec |
1.4 sec |
Search and full item details transactions |
 |
0.09 sec |
0. 2 sec |
End-user resource list transactions |
|
|
0.07 sec |
0.2 sec |
API transactions for the platform products |
How is the Performance Calculated?
"Transaction Time" means the time a transaction takes place (in milliseconds) from when it is received by the system, until the system processes and returns a response, measured on the server.
The average performance calculation is based on the following calculation
The 95% measure is calculated by aggregating all relevant transactions, ordering them from smallest to largest, and then identifying the time that 95% out of all transactions are faster (less) than this time.
Note that the performance measures are measured across all institutions within the instance.
Examples:
- An API call to Higher-Ed Cloud Platform: from the time a request was received in the system until the full API response (in whatever format chosen) was processed and sent back to the calling application
- The ‘All Titles’ screen in Alma: from the time the search query was received in the system until the full result was processed and the page of actual results was generated and sent back to the browser for rendering.
- The resource list displayed in Leganto: from the time that the system receives a request for a resource list until the list is generated and sent back to the browser for rendering.
- Please Note: Analytics API is excluded from the above calculation.
Uptime Report
The uptime measured on a rolling 12-month basis from October 2024 to September 2025 is 99.97%.
The uptime measured on a rolling 3-month basis from July 2025 - September 2025 is 99.87%.
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 (outside of the MW) incidents in Q3 2025
|
Date |
Start time [CDT] |
End time [CDT] |
Duration |
Description |
|---|---|---|---|---|
|
July 9, 2025 |
07:20 AM |
09:40 AM |
140 |
Following Datacenter facility maintenance activity, a network device lost power. We have received monitoring alerts and acted promptly to work with the vendor in order to reconnect and restart the relevant device. Ex Libris has taken the following action and preventive measures to avoid such an occurrence in future:
|
|
August 3, 2025 |
03:50 AM |
05:35 AM |
105 |
As part of our continuous efforts to ensure the availability, stability, and security of our Private Cloud services, we recently performed an upgrade to our load network infrastructure. During this process, a temporary misconfiguration occurred due to a software bug, resulting in a network disruption. Upon identification, our network engineering team promptly implemented a mitigation strategy provided by our vendor to manually correct the misconfiguration. Normal service has been restored. Ex Libris has taken the following action and preventive measures to avoid such an occurrence in future:
|
|
September 22, 2025 |
11:00 AM |
11:15 AM |
15 |
High CPU usage on one of our Network devices caused disruptions to the services in the Data Center. Our engineers took some re-routing measures to resolve the issue. During this disruption we have experienced a technical issue that prevented posting our updates to you via the Status Page, our live communication tool. We have taken immediate measures to assure its stability onwards and will continue to do so as we value transparency and real time updates. We apologies for this experience. Ex Libris has taken the following action and preventive measures to avoid such an occurrence in future:
|
| September 22, 2025 | 12:01 PM | 12:19 PM | 18 |
Scheduled downtime (during the MW) incidents in Q3 2025
|
Start Date |
Day of Week |
Start Time [CET] |
End Time [CET] |
Duration (Minutes) |
|---|---|---|---|---|
| July 6, 2025 | Sunday | 04:26 | 04:38 | 12 |
| August 3, 2025 | Sunday | 03:05 | 03:18 | 13 |
| August 3, 2025 | Sunday | 06:50 | 08:33 | 103 |
| August 10, 2025 | Sunday | 03:00 | 03:22 | 22 |
| August 10, 2025 | Sunday | 03:34 | 03:44 | 10 |
Total unscheduled downtime minutes during the past 12 months
|
Quarter |
Total unscheduled downtime in Quarter (minutes) |
|---|---|
| Q4 2024 | 0 |
| Q1 2025 | 0 |
| Q2 2025 | 0 |
| Q3 2025 | 173 |
How is Uptime Calculated?
The uptime calculation is based on the following calculation (as defined in the 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.