Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteSLA uptime percentages define how much service availability a provider commits to delivering over a specific measurement period. A figure like 99.9% sounds extremely reliable, but it still allows measurable downtime: minutes per day, tens of minutes per month, and several hours per year depending on how the SLA is calculated.
Understanding these numbers helps teams compare providers, set realistic reliability targets, and estimate the business impact of outages. A small difference between 99%, 99.9%, and 99.99% uptime can translate into a major difference in customer disruption, support load, revenue risk, and infrastructure cost.
As an Amazon Associate I earn from qualifying purchases.
An SLA uptime calculator converts an availability percentage into allowed downtime for a day, week, month, quarter, or year. To use it accurately, you need to know the measurement period, whether planned maintenance is excluded, and how the provider defines downtime for partial outages, degraded performance, and regional failures.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →What 99.9% Uptime Means in an SLA
In an SLA, 99.9% uptime means the service is expected to be available for 99.9% of the agreed measurement period. The remaining 0.1% is the maximum downtime allowed before the provider may be considered out of compliance with the service commitment. In plain terms, a 99.9% SLA allows about 1 minute and 26 seconds of downtime per day, 10 minutes and 5 seconds per week, 43 minutes and 50 seconds per 30-day month, or 8 hours, 45 minutes, and 36 seconds per year.
#1 Best Overall
- Profitability calculations; cash flow function Calculates NPV and IRR for uneven cash flows
- Time-value-of-money and Amortization keys solve problems including: pension calculations, loans, mortgages, etc.
- Ideal calculator for students, managers and statisticians
- Built-in functionality : List-based one- and two-variable statistics with four regression options: linear, logarithmic, exponential and power
- The BA II Plus calculator is approved for use on the following professional exams: Chartered Financial Analyst exam. GARP Financial Risk Manager (FRM) exam. Certified Management Accountants exam
This level is often called “three nines” availability. It sounds very high, and for many websites, internal systems, and SaaS products it can be a reasonable target. Still, 99.9% is not the same as continuous availability. A single outage lasting one hour can exceed the monthly downtime allowance for a 30-day SLA period. If the SLA is measured annually, that same one-hour incident may still fit within the yearly allowance, which is the measurement window matters as much as the percentage itself.
What counts as downtime
The exact meaning of downtime depends on the SLA wording. Some agreements define downtime as the service being completely unreachable. Others include severe degradation, failed API requests above a threshold, database unavailability, or regional service failures. For example, an API SLA might count downtime only when more than 5% of requests fail over a rolling five-minute period, while a hosting SLA might count any period when the primary website cannot be reached from mulle monitoring locations.
Most SLAs also define what is excluded from the uptime calculation. Scheduled maintenance, customer-caused configuration issues, third-party network failures, force majeure events, and misuse of the service may be excluded. These exclusions can significantly change the practical value of a 99.9% promise. Two providers may both advertise 99.9% uptime, but one may include planned maintenance in the calculation while another excludes it entirely.
How to interpret a 99.9% commitment
- It is a minimum service target: The provider is committing to keep downtime below the allowed threshold for the defined period.
- It is not a guarantee of no outages: Short interruptions, failed deployments, network incidents, and degraded performance can still occur.
- It depends on measurement rules: Monitoring method, sampling interval, regions tested, and exclusions all affect whether downtime is counted.
- It usually ties to remedies: If the provider misses the SLA, the customer may receive service credits or another contractual remedy, not automatic compensation for business loss.
For business planning, 99.9% uptime should be treated as a reliability benchmark rather than a marketing phrase. It gives teams a concrete downtime budget to compare against operational risk. If an application supports casual browsing, a few minutes of downtime may be acceptable. If it processes payments, supports emergency workflows, or runs production infrastructure for customers, the same downtime allowance may be too generous. Understanding what 99.9% actually permits is the first step toward choosing an SLA target that matches the cost of interruption.
How to Calculate Allowed Downtime from Uptime Percentage
Allowed downtime is the amount of time a service can be unavailable during a defined measurement period while still meeting its SLA. The calculation starts with the uptime percentage, then converts the remaining percentage into time. For example, 99.9% uptime means the service is allowed to be down for 0.1% of the measured period, because 100% minus 99.9% equals 0.1%.
The basic formula is simple: allowed downtime = total time in period × downtime percentage. The downtime percentage is the unavailable portion of the SLA, expressed as a decimal. For a 99.9% SLA, the downtime percentage is 0.1%, or 0.001 as a decimal. If the measurement period is 30 days, the total time is 43,200 minutes. Mullying 43,200 by 0.001 gives 43.2 minutes of allowed downtime for that 30-day period.
Step-by-step calculation
- Choose the measurement period. This could be a day, week, calendar month, rolling 30-day window, quarter, or year.
- Convert the period into minutes or seconds. Minutes are usually easiest for business reporting; seconds are better for high-availability systems.
- Find the downtime percentage. Subtract the uptime SLA from 100%. For 99.9%, the downtime allowance is 0.1%.
- Convert the percentage to a decimal. Divide by 100. So 0.1% becomes 0.001.
- Multiply total time by the decimal. The result is the maximum downtime allowed under the SLA.
Here is the same method using a monthly SLA example. A 31-day month has 44,640 minutes. With a 99.9% uptime target, the allowed downtime is 44,640 × 0.001, which equals 44.64 minutes. A 28-day February has 40,320 minutes, so the allowance is 40.32 minutes. This is monthly downtime numbers can vary unless the SLA defines a fixed 30-day billing month.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- PROFESSIONAL FINANCIAL CALCULATOR : Built-in TVM, IRR, NPV. Engineered for business analysts, real estate investors, accountants, and finance students.
- ADVANCED CASH FLOW & AMORTIZATION : Execute time value of money, break-even analysis, depreciation schedules, and bond pricing. Trusted for professional exam prep", MBA coursework, and banking certifications.
- CATIGA CF-300 : Flip-open hard case with a snap-close design for a secure fit. Compact and portable: designed for daily professional use in office, classroom, or on-site.
- ALL-IN-ONE FOR PROFESSIONALS : From NPV/IRR for real estate analysis to statistical calculations for business analysts. Handles probability, linear regression, and complex financial formulas.
- MORTGAGE, LOAN & INVESTMENT CALCULATOR : Covers bond pricing, loan amortization, investment analysis, and exam-level computations. Your go-to accounting calculator, business calculator, and real estate calculator in one device.
| Input | Example for 99.9% Monthly SLA |
|---|---|
| Measurement period | 30 days |
| Total minutes | 43,200 minutes |
| Uptime target | 99.9% |
| Downtime percentage | 0.1% or 0.001 |
| Allowed downtime | 43.2 minutes |
For accurate results, use the same time unit throughout the calculation and match the SLA’s stated measurement period. A yearly 99.9% SLA does not behave the same as a monthly 99.9% SLA from an enforcement perspective. Under a yearly period, downtime can accumulate across the full year before the SLA is evaluated. Under a monthly period, each month is judged separately, so a single long outage may breach one month even if the annual average still looks acceptable.
It also matters whether the SLA measures total outage time, failed requests, regional availability, or customer-specific availability. For web applications, downtime may be counted only when external monitoring checks fail from mulle locations. For APIs, availability may be based on successful responses below a defined error-rate threshold. The percentage calculation is the starting point, but the contract language determines what actually counts against the downtime allowance.
99.9% Uptime Downtime by Day, Week, Month, and Year
At 99.9% uptime, the service is allowed to be unavailable for 0.1% of the measurement period. That sounds tiny, but the actual downtime budget changes depending on whether the SLA is measured daily, weekly, monthly, or annually. The same percentage can mean less than a minute per day, several minutes per week, or almost nine hours per year.
The basic formula is: allowed downtime = total time in period × 0.001. For example, one day has 1,440 minutes, and 0.1% of 1,440 is 1.44 minutes. That means a service with a daily 99.9% uptime commitment can be down for about 1 minute and 26 seconds before breaching that daily target.
| Measurement period | Total time in period | Allowed downtime at 99.9% uptime |
|---|---|---|
| Day | 24 hours | 1 minute 26 seconds |
| Week | 7 days | 10 minutes 5 seconds |
| 30-day month | 720 hours | 43 minutes 12 seconds |
| Calendar year | 365 days | 8 hours 45 minutes 36 seconds |
These figures are often rounded in SLA discussions, so you may see 99.9% described as allowing about 43 minutes per month or about 8.76 hours per year. Both are accurate enough for planning, but contract terms should be more precise. A “monthly” SLA may use a calendar month, a fixed 30-day month, or a billing cycle. February, a 31-day month, and a leap year all produce slightly different downtime allowances.
The measurement window also changes how forgiving the SLA feels in practice. If 99.9% is measured daily, a single 5-minute outage would breach the daily target. If the same service is measured monthly, that 5-minute outage would consume only part of the monthly downtime budget. For operations teams, this distinction affects alerting thresholds, incident response goals, and how aggressively short outages need to be prevented or remediated.
For customer-facing services, the timing of downtime can matter as much as the total duration. Ten minutes of downtime during peak checkout traffic, payroll processing, or a product launch can be far more damaging than the same ten minutes overnight. The SLA percentage tells you the permitted duration, but it does not fully describe business risk, user frustration, lost revenue, or reputational damage.
Rank #3
- HP 10BII+ FOR STUDENTS & PROFESSIONALS – This HP calculator is built for business, finance, accounting, and statistics courses. Perfect for learners and professionals who need to solve common financial problems quickly without memorizing formulas or relying on spreadsheets.
- 100+ FUNCTIONS FOR REAL WORLD MATH – Quickly solve time value of money, interest rates, loan payments, NPV, IRR, cash flows, and more. The 10bII+ also includes probability distributions for statistics courses—a feature not often found in financial calculators.
- ALGORITHMIC INPUT WITH DEDICATED KEYS – This high-school/college calculator uses algebraic and chain logic with minimal keystrokes. Layout appears the same as standard calculators for easy learning. Dedicated keys give quick access to commonly used financial and statistical functions
- APPROVED FOR MAJOR EXAMS – The HP 10bII+ algebra calculator is permitted for use on SAT, PSAT/NMSQT, and AP tests. An ideal statistics calculator and business calculator for school finance and accounting students preparing for class, coursework, or standardized exams.
- INCLUDES TRAVEL CASE, CLEANING CLOTH & BATTERIES– Slim, durable, and easy to keep on hand or store in a backpack or locker. Includes a protective case, cleaning cloth, and batteries so it’s ready out of the box. Large screen with clear contrast (non-backlit) is easy to read during exams or lectures.
Common SLA Uptime Levels Compared
SLA uptime targets are often described by the number of “nines” in the percentage. Each additional nine looks small on paper, but it sharply reduces the amount of downtime allowed. Moving from 99% to 99.9% cuts the downtime budget by a factor of ten; moving from 99.9% to 99.99% cuts it by another factor of ten. This is higher SLA tiers usually require more redundancy, better monitoring, faster incident response, and higher operating cost.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →| Uptime SLA | Common Name | Allowed Downtime per 30-Day Month | Allowed Downtime per Year |
|---|---|---|---|
| 99% | Two nines | 7 hours 12 minutes | 3 days 15 hours 36 minutes |
| 99.5% | Intermediate tier | 3 hours 36 minutes | 1 day 19 hours 48 minutes |
| 99.9% | Three nines | 43 minutes 12 seconds | 8 hours 45 minutes 36 seconds |
| 99.95% | High availability tier | 21 minutes 36 seconds | 4 hours 22 minutes 48 seconds |
| 99.99% | Four nines | 4 minutes 19 seconds | 52 minutes 34 seconds |
| 99.999% | Five nines | 25.9 seconds | 5 minutes 15 seconds |
For many SaaS products, 99.9% uptime is a common baseline because it allows less than 45 minutes of downtime in a typical 30-day month while still being achievable with well-designed infrastructure. It generally fits business tools, internal platforms, content sites, and applications where short interruptions are inconvenient but not catastrophic. A service at this tier still needs load balancing, backups, alerting, incident processes, and clear escalation paths, but it may not require full active-active architecture across mulle regions.
99.99% uptime is a much stricter commitment. With only about four minutes of downtime available per month, routine failures must be absorbed automatically. Manual recovery is often too slow. This tier is more appropriate for payment systems, authentication services, customer-facing APIs, commerce platforms during peak sales periods, and operational systems where downtime directly affects revenue or customer trust. Achieving it usually means eliminating single points of failure, testing failover regularly, and designing deployments so that releases do not interrupt service.
99.999% uptime, often called five nines, leaves only a few minutes of downtime per year. This level is associated with mission-critical environments such as telecom networks, emergency systems, financial trading infrastructure, and core cloud platform components. It is expensive because the organization must invest not only in resilient technology but also in around-the-clock operations, strict change control, rapid rollback, capacity planning, dependency management, and mature incident review practices.
The right comparison is not only technical. A higher SLA target should match the cost of downtime for the customer and the cost of reliability for the provider. If an hour of downtime causes minor inconvenience, 99.9% may be sufficient. If five minutes of downtime can stop transactions, breach customer contracts, or create safety concerns, a higher tier may be justified. The SLA percentage should reflect the real business risk, not just a desire to advertise more nines.
Why Maintenance Windows and Measurement Periods Matter
SLA uptime percentages only become meaningful when you know what time is being measured and what downtime is excluded. A promise of 99.9% uptime sounds straightforward, but the real allowance depends on whether the SLA is calculated daily, monthly, quarterly, or annually. It also depends on whether planned maintenance counts against the uptime target. Two providers can both advertise 99.9% uptime while offering very different levels of practical availability.
Maintenance windows are scheduled periods when a service may be unavailable for upgrades, patches, database work, infrastructure changes, or security fixes. Many SLAs exclude approved maintenance from downtime calculations, especially when customers receive advance notice. For example, if a SaaS platform has a four-hour scheduled maintenance window on Sunday and excludes it from the SLA, that outage may not reduce the reported uptime at all. If the same four hours were unscheduled, it would exceed the monthly downtime allowance for a 99.9% SLA, which is about 43 minutes and 50 seconds in a 30.44-day month.
Rank #4
- Solves time-value-of-money calculations such as annuities, mortgages, leases, savings, and more
- Performs cash-flow analysis for up to 32 uneven cash flows with up to 4-digit frequencies
- Calculates various financial functions: Net Future Value Net present Value Modified Internal Rate of Return Internal Rate of Return Modified Duration Payback Discounted Payback
- The Texas Instruments BAII Plus Professional features an Automatic Power Down (APD) function for extended battery life
- Prompted display guides you through financial calculations showing current variable and label. Ten-digit display
What to check in the maintenance policy
- Whether planned maintenance is excluded: Some SLAs count only unplanned outages, while others include all service interruptions.
- Required notice period: A provider may need to announce maintenance 24 hours, 7 days, or 14 days in advance for it to be excluded.
- Approved maintenance hours: Work may need to happen during a defined low-traffic window, such as Sundays from 01:00 to 05:00 UTC.
- Maximum maintenance duration: Some contracts cap excluded maintenance at a fixed number of hours per month or quarter.
- Emergency maintenance rules: Urgent security or stability work may be treated differently from routine planned maintenance.
The measurement period is just as significant. A monthly SLA resets every calendar month, so one bad incident can trigger a service credit quickly. An annual SLA averages performance across the year, which can make the same outage look less severe. At 99.9% uptime, the annual downtime allowance is about 8 hours and 45 minutes. If a service is down for 3 hours in one month, it fails a monthly 99.9% SLA because the monthly allowance is under 44 minutes, but it may still remain within an annual 99.9% target.
| Measurement period | Effect on SLA interpretation |
|---|---|
| Daily | Very strict; 99.9% allows only about 1 minute and 26 seconds of downtime per day. |
| Monthly | Common for cloud and SaaS contracts; outages are evaluated and credited month by month. |
| Quarterly | Smooths out short-term incidents but may delay eligibility for credits or remedies. |
| Annual | Best for long-term reporting, but it can hide concentrated downtime in a single business-critical period. |
For accurate SLA comparisons, use an uptime calculator with the same assumptions found in the contract. Enter the correct measurement period, exclude maintenance only if the SLA says it is excluded, and verify whether uptime is measured at the service edge, application layer, API endpoint, or customer account level. A calculator that shows 99.9% as 8.76 hours of annual downtime is mathematically correct, but it may not reflect your real entitlement if the agreement uses monthly measurement, regional availability, service credits, or excluded maintenance windows.
Recommended Free Tools
How to Use an SLA Uptime Calculator
An SLA uptime calculator converts an availability target, such as 99.9%, into the maximum downtime allowed during a selected measurement period. To use it accurately, enter the uptime percentage, choose the period you want to measure, and confirm whether planned maintenance is included or excluded. The result shows how much outage time can occur before the service falls below the agreed SLA commitment.
Inputs you should define first
- Uptime percentage: Enter the SLA target, for example 99%, 99.9%, 99.95%, or 99.99%.
- Measurement period: Select the period used in the contract, such as daily, weekly, monthly, quarterly, or yearly.
- Service hours: Decide whether the SLA applies 24/7 or only during business hours.
- Maintenance treatment: Check whether scheduled maintenance counts against uptime or is excluded.
- Outage definition: Match the calculator to the SLA wording, such as full service outage, regional outage, degraded performance, or failed health checks.
For a standard 24/7 SLA, the calculator mullies the total time in the period by the allowed downtime percentage. If the uptime commitment is 99.9%, the allowed downtime percentage is 0.1%. In a 30-day month, that means 43 minutes and 12 seconds of downtime. In a 365-day year, it means 8 hours, 45 minutes, and 36 seconds. If the SLA is measured only during support hours, the calculator should use those support hours rather than the full calendar period.
Example: calculating 99.9% for a monthly SLA
- Select the SLA target: 99.9% uptime.
- Select the measurement window: one month.
- Choose the month length: 30 days, 31 days, or an average month, depending on the contract.
- Apply maintenance rules: subtract approved maintenance only if the SLA excludes it.
- Compare actual downtime: if outages exceed the calculated allowance, the SLA has been missed.
Be careful with monthly calculations because different tools may use different month lengths. A 30-day month has 43 minutes and 12 seconds of allowed downtime at 99.9%, while a 31-day month has 44 minutes and 38 seconds. Some calculators use an average month of 30.4375 days, which produces about 43 minutes and 50 seconds. For informal planning, these differences are small. For SLA reporting, credits, and compliance reviews, the contract should specify the exact period.
The most reliable way to use an SLA uptime calculator is to align it with the monitoring system that determines SLA compliance. Use the same timezone, start and end dates, maintenance calendar, and outage criteria. If your monitoring checks run every minute, an outage may be rounded differently than a system using five-minute checks. If the SLA applies per customer, per region, or per endpoint, calculate each scope separately instead of averaging unrelated incidents into one number.
| Calculator setting | What to verify |
|---|---|
| Availability target | Matches the SLA percentage in the contract |
| Measurement period | Uses the same daily, monthly, or annual window as the SLA |
| Maintenance windows | Included or excluded according to the agreement |
| Service scope | Reflects the correct application, region, API, or customer group |
Choosing the Right SLA Target for Your Service
Choosing an SLA target is a business decision as much as a technical one. A 99.9% uptime commitment allows about 43 minutes of downtime in a 30-day month, while 99.99% reduces that allowance to roughly 4 minutes and 19 seconds. That difference may look small on paper, but it usually requires a very different architecture, operating model, and budget. The right target is the one your service can consistently meet while matching the real cost of downtime for your customers.
Best Value
- Brand New in box; The product ships with all relevant accessories
- Dedicated keys allow easy access to common financial and statistics functions
- Easy-to-use design provides business, finance and statistical calculations fast
- Specially designed to meet the mathematical needs
Start by classifying the service by customer impact. A public marketing site, internal reporting dashboard, payment processor, authentication system, and emergency dispatch platform should not all have the same SLA. If downtime blocks revenue, prevents users from logging in, affects regulated operations, or creates safety risk, a higher target is easier to justify. If the service is useful but not time-critical, a lower SLA may be more honest and more cost-effective.
Factors to weigh before setting an uptime target
- User expectations: Enterprise customers may expect 99.9% or higher, while internal tools may tolerate scheduled outages or slower recovery.
- Revenue exposure: Estimate lost sales, refunds, SLA credits, support costs, and churn risk for each hour of downtime.
- Architecture maturity: Higher uptime often requires redundancy across zones or regions, automated failover, tested backups, queueing, load balancing, and strong observability.
- Operational coverage: A 99.99% target is difficult without 24/7 alerting, on-call response, incident playbooks, and fast escalation paths.
- Vendor dependencies: Your SLA cannot realistically exceed the weakest critical dependency unless you have redundancy or a fallback path.
- Maintenance needs: If regular upgrades require downtime, define whether maintenance windows are excluded from the SLA calculation.
A practical approach is to map each service tier to a different commitment. For example, a free or trial plan might offer a best-effort availability statement rather than a formal SLA. A standard paid plan might commit to 99.9%, which is common for SaaS applications and gives teams some operational room. A premium or enterprise plan might offer 99.95% or 99.99%, but only if the platform is engineered and staffed to support that promise. Avoid offering “four nines” simply because it looks competitive; missing an aggressive SLA can damage trust more than publishing a realistic target.
| Service type | Typical SLA target | Operational expectation |
|---|---|---|
| Internal admin tool | 99% to 99.5% | Business-hours support, planned maintenance acceptable |
| Standard SaaS application | 99.9% | Monitoring, backups, incident response, limited monthly downtime |
| Revenue-critical platform | 99.95% to 99.99% | High availability design, rapid failover, 24/7 on-call coverage |
| Mission-critical infrastructure | 99.99% and above | Multi-region resilience, rigorous testing, strict change control |
Before publishing the SLA, compare the target against historical uptime data from your monitoring system. If the service has delivered 99.92% over the last six months, a 99.9% SLA may be reasonable, while 99.99% would require clear investment first. Also define the measurement period, included components, exclusions, credit policy, and how uptime is verified. A good SLA target should be measurable, defensible, and aligned with customer impact rather than chosen as a marketing number.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Frequently Asked Questions
How much downtime does 99.9% uptime allow?
99.9% uptime allows 0.1% downtime during the measurement period. That equals about 1.44 minutes per day, 10.08 minutes per week, 43.2 minutes in a 30-day month, or 8.76 hours per year. The exact number changes if your SLA uses a calendar month, rolling 30 days, or a full year.
How do I calculate SLA downtime from an uptime percentage?
Subtract the uptime percentage from 100% to get the allowed downtime percentage, then mully that by the total time in the period. For example, 100% minus 99.9% equals 0.1%, and 0.1% of a 30-day month is 43.2 minutes. Use the same method for daily, weekly, monthly, quarterly, or annual SLA periods.
Does scheduled maintenance count against SLA uptime?
It depends on the SLA wording. Many providers exclude planned maintenance if it is announced in advance and performed during a defined maintenance window. If maintenance is not excluded, it should be counted as downtime when calculating whether the SLA target was met.
Is 99.9% uptime good enough for a business-critical service?
99.9% uptime may be acceptable for internal tools, content sites, test environments, or services where short outages are tolerable. For payment systems, healthcare platforms, authentication services, or high-traffic SaaS products, 99.95%, 99.99%, or higher may be more appropriate. The right target depends on outage cost, customer expectations, staffing, architecture, and budget.
What is the difference between 99.9%, 99.99%, and 99.999% uptime?
Each extra nine greatly reduces the downtime allowed. In a 30-day month, 99.9% allows about 43.2 minutes of downtime, 99.99% allows about 4.32 minutes, and 99.999% allows about 26 seconds. Higher uptime targets usually require redundancy, failover, monitoring, incident response processes, and more infrastructure investment.
Bottom Line
99.9% uptime sounds high, but it still allows about 1.44 minutes of downtime per day, 10.08 minutes per week, roughly 43.2 minutes per 30-day month, and 8.76 hours per year. Understanding these numbers helps you evaluate whether an SLA truly matches your operational needs, customer expectations, and revenue risk.
Use an SLA uptime calculator to compare tiers, confirm the measurement period, and account for exclusions like scheduled maintenance. Before signing or renewing an agreement, translate the percentage into real downtime and decide whether that level of reliability is acceptable for your business.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
