How to monitor your ISP SLA and hold internet carriers accountable

By Michael Obraitis, Managing Partner, and Michael Dale, CEO·Published August 12, 2026·Last reviewed August 2026·ADAM Pulse Knowledge Base

Your business pays for a commercial internet connection.

The carrier promises reliable service.

Then the circuit fails.

Or latency increases.

Or packet loss begins.

Or the connection drops repeatedly for several minutes at a time.

You call the provider.

The response is familiar:

“The circuit looks fine now.”

This creates one of the most common problems in carrier management.

How do you determine whether your internet provider is actually delivering the level of service your business is paying for?

The answer begins with objective measurement.

An ISP Service Level Agreement can define performance commitments between a service provider and customer.

But an SLA is useful only if you understand:

What the provider committed to

How that commitment is measured

What happened during an incident

Whether the problem is recurring

What evidence you can provide

This guide explains how businesses can monitor internet circuit performance, document outages, track SLA related metrics, and improve carrier escalation using historical network data.

What Is an ISP SLA?

SLA stands for Service Level Agreement.

An SLA is an agreement defining expected service performance between a provider and customer.

Cisco describes an SLA as a written agreement between provider and customer based on meaningful and measurable performance metrics.

Depending on the provider and service, an SLA may address:

• Availability
• Uptime
• Latency
• Packet loss
• Jitter
• Response time
• Restoration time

Not every internet service includes the same SLA.

The actual contract controls.

Does Every Business Internet Connection Have an SLA?

No.

Different service types can have very different commitments.

For example:

Business broadband may have different service expectations from:

Dedicated Internet Access.

A cellular backup connection may have different commitments again.

Always review the actual provider agreement.

Do not assume that a metric is contractually guaranteed simply because you monitor it.

What Is ISP SLA Monitoring?

ISP SLA monitoring means measuring network performance over time and comparing those measurements with the relevant service expectations.

Monitoring may include:

• Circuit availability
• Outage duration
• Outage frequency
• Latency
• Packet loss
• Jitter
• Gateway availability
• Historical incidents

The objective is to maintain an independent record of network performance.

Why Should Businesses Independently Monitor Their ISP?

Because the provider and customer view the network from different perspectives.

The carrier sees its infrastructure.

The customer experiences the service.

Independent monitoring gives the customer its own historical record.

That record can be useful during:

• Troubleshooting
• Carrier escalation
• Service reviews
• Contract renewal
• Circuit replacement decisions

What Metrics Should You Track for an ISP Circuit?

Important measurements include:

Availability

Was the circuit reachable?

Outage Duration

How long did the outage last?

Outage Frequency

How often has the circuit failed?

Latency

How much delay exists?

Packet Loss

Are packets being lost?

Jitter

Is packet timing inconsistent?

Gateway Availability

Can the provider handoff be reached?

Historical Performance

Has the same problem occurred before?

Why Is Availability Alone Not Enough?

Consider two circuits.

Circuit A

99.9 percent availability

One significant outage

Circuit B

99.9 percent availability

Dozens of short disruptions

The uptime percentage may look similar.

The user experience may be very different.

Repeated short outages can disrupt:

• Zoom
• VoIP
• VPN
• Cloud applications
• Point of sale
• Remote desktop

Track both total downtime and outage frequency.

Why Should You Track Latency?

A connection can remain online while becoming difficult to use.

Suppose:

Normal latency: 22 ms

Incident latency: 190 ms

Circuit status: UP

An uptime monitor alone might report no problem.

Users may still experience poor application performance.

Cisco IP SLA technology specifically measures delay, jitter, packet loss, connectivity, and other performance indicators because availability alone does not describe service quality.

Why Should You Track Packet Loss?

Packet loss can significantly affect:

• Voice
• Video
• Zoom
• VPN
• Cloud applications
• Interactive services

A circuit may remain reachable while losing packets.

If users report freezing, robotic audio, or application instability, packet loss should be investigated.

Why Should You Track Jitter?

Jitter matters particularly for real time communications.

Cisco specifically measures directional jitter because variation in packet timing can negatively affect voice and video applications.

This makes jitter useful when evaluating circuits that support:

• Zoom
• VoIP
• Contact centers
• Video conferencing

What Is an ISP Uptime Monitor?

An uptime monitor continuously checks whether an internet connection or external destination remains reachable.

It can identify:

• Outage start
• Outage end
• Total downtime
• Repeated failures

But uptime monitoring alone does not necessarily identify:

Why the outage occurred

or:

Whether the ISP was responsible

That requires additional fault isolation.

How Do You Determine Whether an Outage Was Actually the ISP?

Separate the network into logical test points.

For example:

Local Gateway

Firewall

Carrier Gateway

External Internet

Suppose:

Local gateway: healthy

Firewall: healthy

Carrier gateway: unavailable

External connectivity: unavailable

That provides much stronger evidence of an upstream problem than simply reporting:

“The internet went down.”

What Is Gateway First SLA Monitoring?

Gateway first monitoring evaluates the local and upstream network boundaries independently.

The goal is to determine whether the problem begins:

Inside the LAN

At the firewall

At the carrier handoff

or:

Farther upstream

This protects both the customer and the carrier from premature conclusions.

Why Are Exact Outage Timestamps Important?

A precise incident window helps a carrier investigate its own telemetry.

Compare:

Internet failed sometime yesterday afternoon.

with:

External connectivity failed at 2:14 PM Central and recovered at 2:27 PM Central.

The second is far more actionable.

It gives the provider a specific period to examine.

What Information Should You Record During an ISP Outage?

Record:

• Location
• Circuit ID
• Carrier
• Incident start
• Incident end
• Business impact
• Gateway status
• Firewall status
• Carrier gateway status
• External connectivity
• Packet loss
• Latency
• Jitter where applicable
• Route information
• Related incidents

How Do You Calculate Internet Availability?

A simplified availability calculation is:

Availability = Total Service Time Minus Downtime, divided by Total Service Time

Then convert the result to a percentage.

But contractual SLA calculations may use specific definitions, exclusions, measurement points, or maintenance windows.

Always use the provider contract when determining formal SLA compliance.

What Does 99.9 Percent Uptime Actually Mean?

Availability percentages can sound nearly identical while representing significantly different downtime allowances.

The important lesson is not simply memorizing an uptime chart.

It is understanding:

What availability level did your carrier actually commit to?

and:

How does the contract define downtime?

Your independent monitoring history can then be compared with those terms.

Does Planned Maintenance Count as Downtime?

It depends on the contract.

Some agreements exclude:

• Planned maintenance
• Customer caused events
• Force majeure events
• Certain upstream failures
• Other defined conditions

Do not assume every outage qualifies as an SLA violation.

Review the agreement.

Does Monitoring Data Automatically Qualify You for an SLA Credit?

No.

Monitoring data can provide useful evidence.

The contract determines:

• Eligibility
• Measurement method
• Claim procedure
• Claim deadline
• Exclusions
• Credit amount

ADAM Pulse monitoring should therefore be positioned as independent operational evidence, not as automatic proof of contractual entitlement.

How Can You Use Monitoring Data During Carrier Escalation?

Provide a structured incident record.

For example:

Location: Dallas Branch

Circuit: Primary Fiber

Carrier: Example ISP

Incident Start: 2:14 PM Central

Incident End: 2:27 PM Central

Local Gateway: Available

Firewall: Available

Carrier Gateway: Intermittent

External Packet Loss: 8 percent

Normal Latency: 23 ms

Incident Latency: 174 ms

Previous Related Events: Three during the previous week

Now carrier support has something specific to investigate.

Why Does the ISP Say It Cannot Find the Problem?

Often because the problem has disappeared.

Example:

1:05 PM

Circuit begins degrading.

1:12 PM

Users report problems.

1:23 PM

Circuit recovers.

1:35 PM

IT calls carrier.

1:52 PM

Carrier performs test.

Current result:

Healthy.

That does not mean the earlier event was imaginary.

Historical monitoring preserves what happened during the missing window.

How Does Historical Monitoring Improve SLA Management?

Historical monitoring allows you to examine:

• Monthly availability
• Repeated outages
• Latency trends
• Packet loss events
• Recurring instability
• Regional carrier patterns

This moves carrier management from anecdotes to measurable performance.

What Is an SLA Performance Report?

A useful internal report might show:

Carrier

Circuit

Location

Availability

Outage count

Total downtime

Average latency

Packet loss events

Major incidents

Recurring problems

This can be reviewed monthly, quarterly, or before contract renewal.

Why Compare Carriers?

If your organization uses multiple providers, historical performance allows objective comparison.

For example:

Carrier A:

High availability

Few incidents

Stable latency

Carrier B:

Frequent short outages

Higher latency

Repeated packet loss

That information can influence future purchasing decisions.

How Can SLA Monitoring Help During Contract Renewal?

Before renewing a carrier contract, ask:

How has this provider actually performed?

Review:

• Outage history
• Service quality
• Escalation experience
• Response
• Recurring issues
• SLA results
• Business impact

Renewal decisions should be based on evidence, not simply price.

Can SLA Monitoring Identify a Bad Circuit?

Yes.

Suppose one location repeatedly experiences:

• High packet loss
• Latency spikes
• Short outages
• WAN flapping

while other locations using the same carrier remain healthy.

That may indicate a specific circuit or local carrier infrastructure problem.

History helps distinguish chronic circuit issues from broader provider problems.

Can SLA Monitoring Identify a Regional Carrier Problem?

Yes.

Imagine:

Ten locations in the same region

Same carrier

Same latency increase

Same time

Centralized monitoring may reveal the event immediately.

Without centralized data, those incidents might appear unrelated.

Why Should Backup Circuits Be Included in SLA Monitoring?

Backup circuits matter because they are part of the continuity plan.

Monitor:

• Availability
• Performance
• Outages
• Latency
• Packet loss

If the backup is unhealthy, you should know before the primary fails.

What Should You Ask Your Carrier During a Service Review?

Ask:

1. How does your performance data compare with ours?
2. What caused recurring outages?
3. Are any circuits showing chronic issues?
4. Are there known capacity concerns?
5. Have routes or infrastructure changed?
6. What remediation has been completed?
7. Are any service upgrades recommended?
8. Are we receiving the appropriate service level for our applications?

Bring monitoring evidence.

How Can Independent Monitoring Reduce Carrier Disputes?

Objective data changes the conversation.

Without monitoring:

Customer: The internet keeps going down.

Carrier: We do not see anything.

With monitoring:

Customer: We experienced four external connectivity failures this week. During each event the local gateway and firewall remained reachable while the upstream path failed during these specific timestamps.

That is a technical discussion.

Not an argument.

The ADAM Pulse Approach to ISP SLA Monitoring

ADAM Pulse is designed to help organizations maintain an independent history of network performance.

The objective is to answer:

Which circuit failed?

When did it fail?

How long did it fail?

Was the firewall still available?

Was the gateway still available?

Did packet loss occur?

Did latency increase?

Has the same problem happened before?

Is this circuit becoming unreliable?

How does this carrier perform across our locations?

From Carrier Complaint to Carrier Performance Management

There is a major difference between:

Calling the ISP when something breaks

and:

Managing carrier performance over time.

Carrier performance management means understanding:

• Reliability
• Quality
• Recurrence
• SLA history
• Escalation effectiveness
• Business impact

That information can influence both troubleshooting and purchasing decisions.

Stop Depending on the Carrier to Tell You How Your Circuit Performed

Your provider should absolutely be part of the troubleshooting process.

But your organization should also maintain its own network history.

ADAM Pulse provides managed network monitoring designed to help organizations independently track circuit availability, latency, packet loss, historical outages, and network performance across multiple carriers and locations.

Know when the outage happened.

Know what remained online.

Know how the circuit performed.

Know whether it keeps happening.

Then have a better conversation with your carrier.

Learn more about ADAM Pulse and talk with USA Telecom about ISP performance and SLA monitoring.

Frequently asked questions

Sources

• FCC — Measuring Broadband America. Methodology for measuring latency and packet loss alongside throughput.
• Cisco — What Is Network Latency?
• Cisco — Troubleshoot Packet Drops. Congestion, buffer exhaustion and interface errors as drop causes.
• NIST — The NIST Cybersecurity Framework (CSF) 2.0 (NIST CSWP 29, 26 February 2024). Continuous monitoring (DE.CM) and the logging that supports it (PR.PS-04).

USA Telecom Consulting LLC is a Service-Disabled Veteran-Owned Small Business running a 24/7 NOC. We monitor networks, circuits and firewalls for regulated and defense-supply-chain organizations.

← More from the ADAM Pulse Knowledge Base

Prepared by ADAM Pulse (USA Telecom Consulting LLC) — managed AI governance, network, and NOC services. Support: (888) 989-4872 · support@adampulse.us