Every cloud fax vendor publishes an uptime guarantee. Ninety-nine point nine percent. Sometimes 99.99. The numbers look reassuring in a sales deck. They feel like a commitment. But uptime figures in SLA documents are not straightforward promises. They are carefully defined terms with exclusions, calculation methodologies, and remedies that vary significantly between vendors, and the gap between what a number implies and what it actually guarantees can be significant enough to affect real operations in ways that matter.
For enterprise organizations that depend on fax for regulated document exchange, time-sensitive workflows, and compliance-critical transmissions, understanding what an SLA actually says is not a procurement formality. It is a risk management exercise. This post breaks down how cloud fax SLAs are structured, what the fine print typically excludes, what remedies are actually worth, and what organizations should demand before signing.
How Uptime Percentages Are Calculated
The first thing to understand about a 99.9% uptime guarantee is the math behind it. Ninety-nine point nine percent uptime across a calendar month allows for approximately 43 minutes of downtime. Ninety-nine point five percent allows for approximately 3.6 hours. These are monthly allowances, not annual ones, which means a vendor can technically meet a 99.9% monthly SLA while delivering meaningful outages every single month as long as each outage stays under the threshold.
The calculation methodology matters as much as the percentage. Key questions that determine what the number actually means include:
- What counts as downtime? Some SLAs define downtime as complete platform unavailability, meaning partial degradation where the system is technically accessible but performing poorly does not count toward the downtime calculation. An organization experiencing two-hour transmission queue backups may not be accumulating SLA credit even though their workflows are materially affected
- How is downtime measured? Vendor-side monitoring that the vendor controls produces different results than independent third-party monitoring. Some SLAs measure availability from the vendor’s infrastructure to the internet, not from the customer’s environment to the vendor’s platform, which means network issues between the customer and the vendor’s edge do not count
- What is the measurement interval? Uptime calculated in five-minute polling intervals can miss shorter outages entirely. A platform that is unreachable for four minutes every hour might never register a downtime event in a system that polls every five minutes
- Are scheduled maintenance windows excluded? Most SLAs exclude planned maintenance from downtime calculations. A vendor that schedules maintenance during business hours, even with advance notice, is not accumulating SLA credits even if those maintenance windows affect live workflows
What SLA Exclusions Typically Cover
The exclusions section of a cloud fax SLA is where the actual risk lives. Common exclusions that organizations should review carefully include:
- Force majeure events: Broad force majeure clauses can exclude outages caused by anything from natural disasters to internet backbone disruptions to upstream telephony carrier failures. For cloud fax specifically, telephony carrier reliability is directly relevant to transmission performance, and a vendor that excludes carrier-related issues from their SLA is passing significant risk back to the customer
- Customer-side issues: Most SLAs exclude downtime attributable to customer network configurations, customer-side connector failures, or customer-initiated actions. This is reasonable in principle but can create disputes when a transmission failure has ambiguous causation
- Third-party service dependencies: Cloud fax platforms depend on underlying infrastructure including cloud hosting providers, telephony carriers, and DNS services. SLAs that exclude failures in these dependencies mean the vendor’s uptime commitment only covers the narrow slice of the stack they directly control
- Issues outside defined support hours: Some SLAs include response time commitments that only apply during defined business hours, which is directly relevant for organizations with 24/7 fax workflows
- Specific connector or integration availability: Platform uptime and connector availability are sometimes covered separately. A vendor whose core platform is available but whose SAP connector is degraded may be meeting their platform SLA while materially affecting the customer’s ERP-integrated fax workflows
What Remedies Are Actually Worth
When an SLA is breached, the standard remedy is service credits, typically calculated as a percentage of the monthly fee for the period in which the breach occurred. The practical value of these credits deserves honest evaluation.
A service credit remedies the cost of the downtime, not the impact of the downtime. For an organization that missed a regulatory filing deadline, failed to deliver a time-sensitive contract document, or experienced a compliance gap because fax infrastructure was unavailable, a credit against next month’s invoice does not compensate for the actual harm. Understanding this distinction is important when evaluating how much weight to place on SLA commitments relative to other vendor reliability indicators.
Questions to ask about SLA remedies include:
- What is the maximum credit available in any given month, and is it capped as a percentage of monthly fees regardless of the duration or severity of the outage?
- Does the customer need to proactively file a credit claim, or does the vendor automatically apply credits when thresholds are breached?
- Are credits the exclusive remedy, or does the SLA allow for termination rights if availability falls below defined thresholds over a sustained period?
- What is the claims process, and what evidence is required to support a claim?
What Enterprise Organizations Should Demand
For organizations evaluating cloud fax platforms for enterprise deployment, the SLA conversation should go beyond comparing uptime percentages. The questions that matter most are:
- How is the platform architected for availability? An SLA is a financial instrument. The architecture is what actually determines whether downtime occurs. Ask about redundancy, failover design, geographic distribution of infrastructure, and how the platform handles telephony carrier failures
- What is the vendor’s actual track record? Uptime guarantees describe what the vendor commits to. Incident history describes what they have actually delivered. Ask for historical uptime data and inquire about significant outages in the past 12 to 24 months
- How does the vendor communicate during incidents? A platform that experiences an outage but does not proactively notify customers leaves organizations discovering problems through failed workflows rather than vendor alerts. Ask about incident notification procedures, communication channels, and typical time to notification
- What monitoring is available to customers? Faxination’s cloud portal provides real-time visibility into transmission status, queue health, and connector performance, giving administrators the ability to detect issues independently rather than depending entirely on vendor-reported status
- What are the support response commitments for different severity levels? An SLA that commits to 99.9% uptime but does not define response times for critical incidents leaves organizations waiting without a defined timeline during the outages that matter most
Faxination’s Approach to Availability
Fenestrae’s approach to platform availability is grounded in architecture rather than just contractual commitment. Faxination’s high-availability design includes redundant components, automatic failover, and load balancing that distributes transmission volume across available resources. This means that individual component failures do not cascade into platform-wide outages, and that peak volume periods do not degrade performance in ways that affect availability metrics.
For organizations subject to compliance frameworks that require documented infrastructure reliability, including HIPAA, PCI DSS, and GDPR, Faxination’s platform provides the combination of architectural reliability and audit documentation that compliance assessments require. The Fenestrae maintenance and support program provides defined response commitments and access to fax infrastructure experts for issue resolution.
The right way to evaluate a cloud fax vendor’s reliability is to ask how the platform is built, not just what the contract says. Contact Fenestrae to discuss platform architecture, availability history, and support commitments, or request a demo to see the monitoring and visibility capabilities that give administrators real-time insight into platform health.
