Availability of the API | The percentage uptime of the API, calculated as 100% minus the percentage downtime for each day | For every 24 hours (from 00:00:00 to 23:59:59 every day), we calculated 100% minus the total percentage downtime in that period. Downtime MUST be calculated as follows: The total number of concurrent seconds per API calls per 24-hour period, starting and ending at midnight, that any element of the API interface is not available divided by 86,400 (the number of seconds in 24 hours) and expressed as a percentage. The clock for downtime MUST start immediately after the first 'failed' API request or response has been logged and MUST stop once a 'successful' API response has been logged. In addition, any connectivity issues causing the LFI not to be able to receive any API calls MUST also be measured as downtime.
Downtime MUST be measured if: Any LFI authorization and/or resource server is not fully accessible and accepting all valid TPP requests. Any LFI downstream system required to support these API endpoints is also not responding in a way that affects the availability of the LFI authorization and/or resource servers. Any of the LFI screens and/or functionality of the customer authentication flow is unavailable to enable customers to grant TPPs access to their account(s). This MUST include all 5xx errors. Errors based on 4xx HTTP status codes are mainly attributable to TPP or User actions or failures and hence SHOULD NOT be included in the calculation, EXCEPT in the case these errors are generated due to a LFI internal system failure or malfunction. This MUST include both planned and unplanned downtime during each day. Even if this only affects some TPPs and/or customers, downtime MUST still be reported, i.e., partial downtime should still be measured as downtime. This MUST include any vendor/supplier failures if the LFI has contracted the vendor/supplier to deliver a related service, e.g., the LFI's hosting provider or any Certificate Authority (CA) the LFI has selected for their certificates.
However, this SHOULD exclude errors resulting from issues outside the LFI's direct control, such as issues with TPP software, infrastructure, or connectivity. | Uptime of 99.5%. This allows for just under four hours per month of downtime to cover planned releases, updates, and unplanned downtime. |