Three nines over 30 days
99.9% availability across a 30-day period allows 43 minutes 12 seconds of downtime. The same percentage across a different period gives a different allowance.
Turn a percentage such as 99.9% into a useful downtime allowance, or calculate availability from an outage total. Choose the measurement period explicitly so monthly and yearly assumptions stay visible.
Allowed downtime
43m 12s
2,592 seconds of downtime over 30 days
All days are exactly 24 hours. Calendar months use their actual day count, including February in leap years. No local daylight saving adjustment is applied. Availability = (period − downtime) ÷ period × 100.
This is a time-based estimate. Contractual SLAs can exclude maintenance, use request success rates, or measure separate services. Read your provider’s definition before treating the result as an SLA allowance.
Calculations run locally and do not contact your services.
Choose whether to calculate allowed downtime or availability from actual downtime.
Enter the percentage or downtime, then select a period. Use a specific calendar month to account for its real number of days.
Read the result in days, hours, minutes, and seconds, and copy or download the calculation with its assumptions.
99.9% availability across a 30-day period allows 43 minutes 12 seconds of downtime. The same percentage across a different period gives a different allowance.
If a service is unavailable for 30 minutes during a 30-day measurement period, availability is about 99.930556%. Add separate outages before entering the total, and avoid counting overlapping incidents twice.
Time-based availability equals (measurement time minus downtime) divided by measurement time, multiplied by 100. The downtime allowance equals measurement time multiplied by (100 minus the target percentage), divided by 100. The calculation accepts 0% through 100%, including fractional percentages; it rounds duration displays to milliseconds.
A default month is exactly 30 days. A specific calendar month uses its actual number of days, including February 29 in a leap year. You can select 365-day or 366-day years, a 7-day week, or a custom period. Every day is modeled as 24 hours, so local daylight saving changes do not shorten or lengthen a day here.
A service contract may measure successful requests instead of elapsed time, exclude scheduled maintenance, define a minimum outage length, or use a different reporting window. A downtime budget is therefore only meaningful alongside the service’s own measurement rules. This calculator does not monitor a service or determine service credits.
For exactly 30 days, 99.99% availability allows 4 minutes 19.2 seconds of downtime. Select a calendar month if your reporting month has a different length.
No. Here 100% is a mathematical target that allows zero counted downtime within the chosen period. It is not a prediction or a reliability guarantee.
Yes. Add non-overlapping downtime intervals in a common unit and enter the total in reverse mode. The total must be between zero and the full period.