The SLA: Where Hours-to-Days Is Actually Your Money
A cloud provider's Service Level Agreement typically guarantees a percentage of uptime �?99.9%, 99.99%, 99.999%. The percentage is marketing. The hours of permitted downtime is the fine print. The arithmetic: 365 days × 24 hours = 8,760 hours per year. Unavailability = (100% �?SLA%) × 8,760. For 99.9%: 0.1% × 8,760 = 8.76 hours/year. For 99.99%: 0.876 hours = 52.6 minutes. For 99.999%: 0.0876 hours = 5.26 minutes = 315 seconds. Convert back to days by dividing by 24: 99.9% allows 0.365 days of downtime �?roughly a third of a calendar day, spread across the entire year. A provider who exceeds 8.76 hours of downtime in a year owes you a service credit �?typically a percentage of your monthly bill, not the actual cost of your downtime. The SLA credit for 9 hours of downtime might be 10% of your monthly invoice: $100 on a $1,000/month contract, for an outage that cost your business $50,000 in lost orders. The hours-to-days conversion is not the problem. The ratio of SLA credit to actual business loss is the problem. Do the division. Read the contract.
Every additional "nine" reduces permitted downtime by a factor of 10. Going from 99.9% to 99.99% costs the provider roughly 10× more in redundant infrastructure �?multiple availability zones, automatic failover, geographically distributed data centers. Going from 99.99% to 99.999% costs roughly another 10×, because now you need redundancy at every layer: power, network, compute, storage, DNS, and the monitoring system that watches all of them, which must itself be redundant or it becomes the single point of failure. The economics of cloud uptime are an hours-to-days conversion multiplied by a stack of redundant systems. The customer pays for the nines. The provider pays for the redundancy. The arithmetic that connects the two is always: 8,760 × (1 �?SLA).
days = hours ÷ 24
The 80-Hour Week: How Hours-to-Days Changed Medical Training
In 1984, an 18-year-old college freshman named Libby Zion was admitted to a New York City hospital with fever and agitation. She died within 24 hours. The investigation revealed that a resident physician, working his 36th consecutive hour, had prescribed a medication that interacted fatally with an antidepressant Libby was taking. The resident's fatigue �?36 hours without sleep �?was identified as a contributing factor. The case led New York State to adopt the first legal limits on resident work hours in 1989: no more than 80 hours per week, no more than 24 consecutive hours on duty. The Accreditation Council for Graduate Medical Education (ACGME) adopted the 80-hour limit nationally in 2003.
Eighty hours per week ÷ 24 hours per day = 3.33 days of continuous work. Spread across 6 days, it's roughly 13.3 hours per day. The math is achievable. The human being working the 13th hour of a shift, after 5 hours of sleep the night before, is not doing math. The hours-to-days conversion is the law. The fatigue behind it is what the law was written to prevent. The resident who made the error in 1984 did not fail at arithmetic. He failed because the human brain, after 24 hours without sleep, performs cognitively at roughly the level of a blood alcohol concentration of 0.10% �?legally intoxicated in every U.S. state. The hours-to-days conversion in medical regulation is a patient safety measure disguised as an arithmetic operation. Divide the total hours by 24. If the result is more than 3.33 for a single week, someone is working too many hours and patients are at risk.
Worked Examples
8 h �?0.3333 days (1/3 day)
The standard American workday. 8 hours of work, 8 hours of sleep, 8 hours of everything else �?the 8-8-8 division that labor unions fought for in the 19th century and that became the Fair Labor Standards Act's implicit assumption about the shape of a working day. 8 ÷ 24 = 1/3. The working third.
24 h �?1 day
The definition. The full rotation. 24 hours of continuous time. In a hospital, a 24-hour shift is the maximum permitted under ACGME rules �?and must be followed by at least 14 hours off. The human body does not do 24-hour shifts willingly. It does them because someone has to, and the regulation ensures there is a recovery period after.
40 h �?1.667 days
The standard work week. 40 hours = 1.667 continuous days. Spread across 5 workdays = 8 hours each. The 40-hour week was codified in the Fair Labor Standards Act of 1938. Before that, a 60-hour week was common, a 72-hour week was legal, and a 100-hour week in a steel mill was not unheard of. The hours-to-days conversion behind labor law: 40 ÷ 24 = 1.667. The remaining 5.333 days of the week are protected by law from employer encroachment �?at least until overtime pay kicks in.
168 h �?7 days
One week. 168 hours. 7 × 24. The week is the only time unit with no astronomical basis �?it's a Babylonian religious convention that became a global civil standard. Every hours-to-days conversion that spans more than a day eventually hits the week boundary: 168 hours = 1 week. The conversion is clean. The origin of the number 7 is a mystery wrapped in a ziggurat.
Common Hours to Days
| Hours | Days | Fraction | Context |
|---|---|---|---|
| 8 h | 0.3333 d | 1/3 | Standard workday. The 8-8-8 day. |
| 12 h | 0.5 d | 1/2 | Half-day shift. Hospital day shift or night shift. |
| 24 h | 1 d | 1 | One full rotation of the Earth. The definition. |
| 40 h | 1.667 d | 1 2/3 | Standard work week. FLSA threshold for overtime. |
| 72 h | 3 d | 3 | 72-hour visa-free transit window. Amazon Prime delivery. |
| 80 h | 3.333 d | 3 1/3 | ACGME resident work week limit. 10 days of PTO. |
| 168 h | 7 d | 7 | One week. The global civil time unit. |
Engineering Context
The hours-to-days conversion (÷24) is the inverse of the days-to-hours multiplication. Both operations are exact in civil timekeeping. The only edge cases are DST transitions (a 23-hour or 25-hour civil day), leap seconds (a day with 86,401 seconds �?but still 24 civil hours), and the calendar boundary (months have variable numbers of days). For software that computes time intervals: always store the base value in seconds or milliseconds, convert to hours or days only for display. The conversion chain downward: hours �?days (÷24), hours �?weeks (÷168), hours �?months (÷730.001 on average �?an approximation, since months vary). For the reverse direction, see days to hours (×24). For sub-day conversions: hours to minutes (×60) and hours to seconds (×3,600). For the full time conversion family, see minutes to hours and seconds to hours �?the upward conversions from smaller units through the same ÷60 and ÷3,600 divisions.
More: days to hours · hours to minutes · hours to seconds · minutes to hours · Time Guide
Related Unit Converters
Frequently Asked Questions
What does 99.99% uptime actually mean in hours per year?
8,760 hours × (100% �?99.99%) = 8,760 × 0.0001 = 0.876 hours = 52.6 minutes of allowable downtime per year. That's roughly one hour-long outage, or four 13-minute outages, or 52 one-minute blips �?however the provider's total outage time accumulates. The SLA does not limit the number of outages, only their total duration. A provider with one 53-minute outage is compliant. A provider with 53 one-minute outages �?a minute of downtime every week �?is also compliant. Both have "four nines" uptime. The customer experience is different. The SLA is indifferent. The hours-to-days conversion beneath the SLA: 0.876 hours ÷ 24 = 0.0365 days of downtime per year. The provider is guaranteeing 364.9635 days of uptime per year. The arithmetic is exact. The customer experience is not.
Why are hospital shifts 12 hours instead of 8?
A 12-hour shift allows two shifts to cover 24 hours with only one handoff between shifts. Handoffs are where medical errors happen �?information is lost, assumptions are made, the departing nurse's mental model of the patient's condition does not transfer perfectly to the arriving nurse. Reducing handoffs from two per day (8-hour shifts) to one per day (12-hour shifts) reduces the error opportunities from the handoff itself. The tradeoff: a nurse at hour 11 of a 12-hour shift is fatigued �?roughly the cognitive equivalent of a 0.05% BAC. The 12-hour shift reduces handoff errors and increases fatigue errors. The medical literature has not reached a consensus on which direction produces fewer total errors. Hospitals choose based on staffing economics (fewer nurses per day, fewer handoffs) and patient acuity (higher-acuity units tend toward 12-hour shifts because the continuous monitoring reduces the information loss at handoff). The hours-to-days conversion (12 ÷ 24 = 0.5) is clean. The clinical decision behind the shift length is not.
How does PTO accrual convert between hours and days?
An employee who accrues 6.67 hours of PTO per biweekly pay period = 173.3 hours per year ÷ 8 = 21.67 working days. The same employee sees "22 days of PTO" on their offer letter and "6.67 hours per pay period" on their pay stub. The discrepancy �?173.3 vs. 176 hours �?comes from rounding. The PTO accrual rate is calculated in hours because payroll systems process hours, not days. The employee sees days because humans think in days for time off. The conversion factor (hours ÷ 8 for an 8-hour workday) is specified in the employee handbook. The employee who reads it knows their actual PTO balance. The employee who doesn't discovers it when their 5-day vacation request for 40 hours is deducted as 40 hours and they have 2.3 hours left �?not enough for the half-day they planned to take next month. The hours-to-days conversion for PTO is ÷8, not ÷24. The discrepancy between work-days and calendar-days is the most common point of confusion in PTO accounting, and the answer is always in the handbook.