Network & DNS

Uptime SLA Calculation & DNS Monitoring

Uptime is the measure of time a website or service is operational and accessible to users. In the digital economy, downtime translates directly into lost revenue, wasted marketing spend, and damaged brand reputation.

Maintaining high uptime requires establishing Service Level Agreements (SLAs) and monitoring critical infrastructure layers, starting with the Domain Name System (DNS).

sequenceDiagram
    participant B as User Browser
    participant R as DNS Resolver
    participant N as DNS Nameserver
    participant W as Web Server

    Note over B,W: Standard Request Flow
    B->>R: 1. Request IP for example.com
    R->>N: 2. Query Authoritative DNS
    N-->>R: 3. Return IP (e.g. 192.0.2.1)
    R-->>B: 4. Deliver IP Address
    B->>W: 5. HTTP GET /
    W-->>B: 6. 200 OK (Website Loads)

    Note over B,W: Silent Outage Scenario (DNS Down)
    B->>R: 1. Request IP for example.com
    R->>xN: 2. Query Authoritative DNS (Fails)
    R-->>B: 3. DNS_PROBE_FINISHED_NXDOMAIN
    Note over B,W: User cannot reach the functional Web Server!

1. What is an Uptime SLA?

A Service Level Agreement (SLA) is a commitment between a service provider and a client specifying the service’s expected availability. Uptime SLAs are usually represented as a percentage of a given time period (such as a month or a year).

Calculating Uptime

The formula to calculate the actual uptime percentage is:

Uptime % = ((Total Time - Downtime) / Total Time) * 100

The “Nines” of Uptime

Even a small fraction of a percent of downtime can translate into hours of service unavailability over the course of a year:

Availability SLA	Monthly Downtime	Annual Downtime	Business Impact
99.0% (“Two Nines”)	7 hours, 18 minutes	3 days, 15 hours	High impact; unacceptable for modern SaaS.
99.9% (“Three Nines”)	43 minutes, 49 seconds	8 hours, 45 minutes	Industry standard for standard web apps.
99.99% (“Four Nines”)	4 minutes, 23 seconds	52 minutes, 35 seconds	High availability; requires redundant clusters.
99.999% (“Five Nines”)	26 seconds	5 minutes, 15 seconds	Enterprise grade; requires multi-region failover.

2. DNS Monitoring: Preventing Silent Outages

Before a browser can request a web page, it must resolve the website’s domain name (e.g. example.com) to an IP address using the Domain Name System (DNS).

If your DNS nameservers are down, misconfigured, or slow, users cannot access your site - even if your web servers are fully functional. This is a Silent Outage because standard server-side monitoring tools might show the server is healthy.

Common DNS Issues

DNS Resolver Failures: Your domain registrar’s nameservers go offline due to a DDoS attack or network routing issues.
Incorrect/Expired Records: A developer modifies a DNS record (like an A record or CNAME record) and inputs the wrong IP address or points it to an expired server.
Domain Expiration: The registrar suspends resolution because the domain’s auto-renewal card failed.

How to Monitor DNS

Query nameservers directly: Don’t just ping your server. Ensure your monitoring tool queries your primary DNS nameservers for correct records.
Monitor Domain Registration: Check WHOIS records regularly for expiration dates.

Sources & Standards

IETF RFC 1034: Domain Names - Concepts and Facilities - The foundational internet standard describing DNS database structures and query resolutions.
Uptime SLA Math: SLA Violations & High Availability - Detailed documentation of uptime calculation, MTBF, and service credit formulas.
ICANN: Domain Lifecycle & Expiration Guidelines - The global registrar framework governing domain renewals, grace periods, and redemption statuses.

How Vioro monitors this

Planned

Vioro checks your website's availability at regular intervals and queries your DNS nameservers, alerting you instantly to failed responses, resolution errors, or impending domain name expirations.