InnerWeb
Skip to main content

99.5% availability: how many minutes of downtime per month

99.5% availability per calendar month means the server may be unavailable for 0.5% of the month. In a 30-day month that is 216 minutes, that is 3 hours and 36 minutes. Below are the formula, a table for different month lengths, and how to check the result against the service report.

216 min
permitted downtime in a 30-day month
Source: calculated from the offer card (99.5%)

What exactly is covered by 99.5% availability

Availability of 99.5% covers the server part of the instance and is measured per calendar month. It does not cover plant devices, such as transmitters, kiosks or readers of the access control system, because they have their own parameters and are sometimes beyond the control of the software vendor.

For the administrator this matters when classifying reports. A failed gate or disconnected reader does not enter the server availability calculation, although it may be a service report of another type. Separating the two issues shortens the discussion when going through the report.

Formula and three numerical examples

Permitted downtime in minutes is the number of days in the month multiplied by 24 hours, by 60 minutes, by 0.5%. In a 30-day month this is 43,200 minutes, and 0.5% gives 216 minutes. In February with 28 days we get 40,320 minutes and 201.6 minutes, and in a 31-day month 44,640 minutes and 223.2 minutes.

It is worth rounding the result in the direction safe for the client, that is down, and recording it in the procedure. Then the plant knows that February gives about 201 minutes, not 216. A difference of a dozen or so minutes out of about 3.5 hours hardly changes anything, but a written formula ends disputes over interpretation.

  • 28 days: 40,320 minutes, permitted downtime 201.6 minutes,
  • 30 days: 43,200 minutes, permitted downtime 216 minutes,
  • 31 days: 44,640 minutes, permitted downtime 223.2 minutes.

Permitted downtime at 99.5%

Permitted downtime at 99.5%Bar chart: 201.6, 216 and 223.2 minutes of permitted downtime.050100150200250minutesMonth of 28 days: 201.6 minutes201.6Month of 28 daysMonth of 30 days: 216 minutes216Month of 30 daysMonth of 31 days: 223.2 minutes223.2Month of 31 days
Source: Calculation: days x 24 x 60 x 0.5%

How the administrator checks availability step by step

Step one is to download the report from the service desk system and the list of server interruptions for the month. Step two is to add up the time of events in which the server did not perform its function. Step three is to compare the sum with the permitted downtime from the table for that month length.

If total downtime is 150 minutes in a 30-day month, availability is 99.65% and the limit is not exceeded. If it is 300 minutes, availability is 99.31% and the limit has been exceeded by 84 minutes. The formula for availability is 100% minus total downtime divided by the number of minutes in the month.

Planned work in the update window versus downtime

Software updates are installed in a window agreed with the client, after the new version has been tested on pre-production. It is worth agreeing in writing whether the window time counts toward downtime. Typically it is agreed that work in the agreed window is planned and its maximum duration is set.

A good practice is to plan the window for low-traffic hours and to notify users in advance. The plant administrator records the date, hours and result in the change log, which later serves for audit and for settling the month.

What to do when the limit is exceeded

A server availability overrun must be distinguished from an SLA overrun for a strategic failure. The SLA parameters (availability, response and repair times) are set in the maintenance contract, for example availability of 99.5% per month. The administrator should therefore collect the service report and the report from the service desk system, and describe which events make up the downtime.

Availability itself is a measure of service quality, which is discussed at the service review meeting.

Evidence for audit

Three elements should be added to the plant documentation: a table of permitted downtime for each month length, a monthly report from the service desk system, and a note with the assessment of the result. Such a set provides evidence for the vendor audit and shows that the plant supervises the contract, not just signs it.

Video

Frequently asked questions

How many minutes of downtime does 99.5% allow per month?

In a 30-day month 216 minutes, in a 28-day month 201.6 minutes, and in a 31-day month 223.2 minutes.

Where does the administrator get data on downtime?

From the report in the service desk system and from the list of server interruptions for the calendar month.

Does a card reader failure count toward availability?

No. Availability covers the server part of the instance, and readers belong to the client's access control system.

Are availability and SLA the same thing?

No. Availability measures server operation per month, while SLA sets response and repair times for three incident types.

Let's talk about the terms of cooperation

We will go through the scope, SLA and purchase model with you in one meeting. Pricing is individual, and we explain the terms of the contract using examples from the plant.

Let's talk