Demo – made-up data. Northline, the sites and the numbers are invented. Notices 3.5 – work in progress
VANTAGENorthline
Collected✕7 sites need attention

Circuit SLA

Each internet line against its target · built Sun Nov 22 2026 04:16 PM

Uptime, outages, latency and packet loss for every circuit, this month so far and last month, from what each collection recorded. Keep the CSV with a carrier claim or a renewal. Circuits · Availability · Ping.

36 circuits2 below target this month0 below target last month

Below target this month

SiteCircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
PhoenixExample Fiber
wan1 · Example Fiber
99.9%99.423%180 min18.5 ms9.8 ms1.2 ms0%0.5%0.5 h
PhoenixMetro Cable
wan2 · Metro Cable
99.9%99.417%182 min28.3 ms9.9 ms1.4 ms0%0.5%0.5 h
Atlanta2 on target or not known

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.3 ms9.7 ms1.2 ms0%0.5%0.5 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.4 ms11.1 ms1.3 ms0%0.5%0.5 h

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.5 ms9.8 ms1.2 ms0%0.5%0.2 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.2 ms11 ms1.4 ms0%0.5%0.2 h
Azure East2 on target or not known

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Path A
wan1 · Path A
99.9%100.000%0 min08.5 ms9.8 ms1.2 ms0%0.5%0.5 h
Path B
wan2 · Path B
99.9%100.000%0 min09.4 ms11.1 ms1.3 ms0%0.5%0.5 h

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Path A
wan1 · Path A
99.9%100.000%0 min08.6 ms9.8 ms1.4 ms0%0.5%0.2 h
Path B
wan2 · Path B
99.9%100.000%0 min09.9 ms11 ms1.4 ms0%0.5%0.2 h
Azure West2 on target or not known

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Path A
wan1 · Path A
99.9%100.000%0 min08.3 ms9.8 ms1.2 ms0%0.5%0.5 h
Path B
wan2 · Path B
99.9%100.000%0 min09.2 ms11.1 ms1.3 ms0%0.5%0.5 h

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Path A
wan1 · Path A
99.9%100.000%0 min08.4 ms9.8 ms1.4 ms0%0.5%0.2 h
Path B
wan2 · Path B
99.9%100.000%0 min09.6 ms11.1 ms1.3 ms0%0.5%0.2 h
Boston2 on target or not known

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.3 ms9.8 ms1.4 ms0%0.5%0.5 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.3 ms11.1 ms1.3 ms0%0.5%0.5 h

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.8 ms9.9 ms1.3 ms0%0.5%0.2 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.7 ms10.9 ms1.4 ms0%0.5%0.2 h
Charlotte2 on target or not known

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.3 ms9.8 ms1.3 ms0%0.5%0.5 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.4 ms11.1 ms1.3 ms0%0.5%0.5 h

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.4 ms9.7 ms1.4 ms0%0.5%0.2 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.4 ms11 ms1.3 ms0%0.5%0.2 h
Chicago4 on target or not known

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.4 ms9.8 ms1.3 ms0%0.5%0.5 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.6 ms11.1 ms1.4 ms0%0.5%0.5 h
Starlink
wan3 · Starlink
99.9%100.000%0 min043.5 ms50.5 ms1.3 ms0%0.5%0.5 h
Example Fiber West
wan4 · Example Fiber West
99.9%—0 min0—————520.3 h

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.2 ms9.7 ms1.2 ms0%0.5%0.2 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.1 ms11.1 ms1.3 ms0%0.5%0.2 h
Starlink
wan3 · Starlink
99.9%100.000%0 min042.2 ms50.2 ms1.3 ms0%0.5%0.2 h
Example Fiber West
wan4 · Example Fiber West
99.9%—0 min0—————213.9 h
Dallas2 on target or not known

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.3 ms9.9 ms1.4 ms0%0.5%0.5 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.2 ms11.1 ms1.3 ms0%0.5%0.5 h

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.5 ms9.9 ms1.4 ms0%0.5%0.2 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.5 ms11 ms1.2 ms0%0.5%0.2 h
Denver2 on target or not known

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min0296.6 ms346.8 ms1.3 ms0%0.5%0.5 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.5 ms11.1 ms1.2 ms0%0.5%0.5 h

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min0291.9 ms343.7 ms1.2 ms0%0.5%0.2 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.4 ms10.8 ms1.3 ms0%0.5%0.2 h
Detroit2 on target or not known

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.1 ms9.7 ms1.4 ms0%0.5%0.5 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.4 ms11 ms1.3 ms0%0.5%0.5 h

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.7 ms9.9 ms1.1 ms0%0.5%0.2 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.6 ms11.1 ms1.4 ms0%0.5%0.2 h
Houston2 on target or not known

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.4 ms9.9 ms1.3 ms0%0.5%0.5 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.6 ms11.1 ms1.4 ms0%0.5%0.5 h

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.4 ms9.8 ms1.2 ms0%0.5%0.2 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.4 ms11.1 ms1.3 ms0%0.5%0.2 h
Los Angeles2 on target or not known

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.3 ms9.8 ms1.3 ms0%0.5%0.5 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.3 ms11.1 ms1.2 ms0%0.5%0.5 h

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.4 ms9.8 ms1.4 ms0%0.5%0.2 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.5 ms11 ms1.2 ms0%0.5%0.2 h
Miami2 on target or not known

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.1 ms9.8 ms1.2 ms0%0.5%0.5 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.3 ms11.1 ms1.3 ms0%0.5%0.5 h

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.5 ms9.8 ms1.2 ms0%0.5%0.2 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.6 ms10.9 ms1.5 ms0%0.5%0.2 h
Minneapolis2 on target or not known

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.5 ms9.8 ms1.3 ms0%0.5%0.5 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.4 ms11 ms1.2 ms0%0.5%0.5 h

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.4 ms9.8 ms1.4 ms0%0.5%0.2 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.7 ms11.1 ms1.1 ms0%0.5%0.2 h
New York2 on target or not known

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.5 ms9.8 ms1.3 ms0%0.5%0.5 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.4 ms11.1 ms1.3 ms0%0.5%0.5 h

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.2 ms9.8 ms1.4 ms0%0.5%0.2 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.4 ms11 ms1.4 ms0%0.5%0.2 h
Philadelphia2 on target or not known

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%—0 min0—————520.3 h
Metro Cable
wan2 · Metro Cable
99.9%—0 min0—————520.3 h

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%—0 min0—————213.9 h
Metro Cable
wan2 · Metro Cable
99.9%—0 min0—————213.9 h
Phoenix2 below target

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%99.423%180 min18.5 ms9.8 ms1.2 ms0%0.5%0.5 h
Metro Cable
wan2 · Metro Cable
99.9%99.417%182 min28.3 ms9.9 ms1.4 ms0%0.5%0.5 h
3 outages
  • Example Fiber: 2026-11-10 11:05 for 180 min
  • Metro Cable: 2026-11-10 11:05 for 180 min
  • Metro Cable: 2026-11-22 16:15 for 2 min (still down)

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.2 ms9.8 ms1.2 ms0%0.5%0.2 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min08.6 ms9.9 ms1.2 ms0%0.5%0.2 h
Seattle2 on target or not known

November 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.4 ms9.8 ms1.2 ms0%0.5%0.5 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.5 ms11.1 ms1.2 ms0%0.5%0.5 h

October 2026

CircuitTargetUptimeDownOutagesLatency95thJitterLoss95thNot known
Example Fiber
wan1 · Example Fiber
99.9%100.000%0 min08.3 ms9.8 ms1.1 ms0%0.5%0.2 h
Metro Cable
wan2 · Metro Cable
99.9%100.000%0 min09.4 ms11 ms1.3 ms0%0.5%0.2 h
How it is measured

Every collection records each SD-WAN member as up, slow or down with its latency, jitter and loss (the FortiGate's own health check). A state lasts until the next record, at most 3 hours; longer gaps, failed collections and maintenance windows count as not known and are not held against the carrier. Uptime is up plus slow over the known time.

The target is circuit_sla.target_pct (99.9%) unless the site's Library circuits.csv gives the circuit an sla_pct. Latency and loss are marked when they pass circuit_sla.latency_ms or loss_pct (off unless set).

The health check measures the path to its probe server, not only the carrier: a busy FortiGate or a far probe adds latency. Check an outage against the carrier's own report before you claim. Nothing here changes a site's colour.

Backups

philadelphia: no backup for 2 days – the FortiGate did not answer (site unreachable). See Change → Backups.