Network status
Service health for our fiber, SD-WAN, DNS and cloud regions — with 90 days of uptime history, planned maintenance and honest incident write-ups.
PreviewReal-time status is coming soon
This page is a preview. The live feed will connect when our monitoring API launches; until then the history, maintenance and incidents below are illustrative sample data. If something looks wrong on your service right now, email the NOC — they are watching the real network 24/7.
Services
Each bar is one day. Hover, tap or use the arrow keys to see the details.
Residential XGS-PON · Phase 1 under construction, first connections Q2 2027
Not yet in service
Salt Lake valley routes · IP transit & BGP edge
99.999% uptime
Controller, policy engine & customer dashboard
99.987% uptime
Compute, private cloud, storage & backup
99.999% uptime
Compute, private cloud, storage & backup
99.990% uptime
Compute, private cloud, storage & backup
99.999% uptime
Compute, private cloud, storage & backup
99.999% uptime
Recursive DNS & Quantum Shield filtering
99.999% uptime
noc@ mailbox, ticket routing & notifications
99.979% uptime
Scheduled maintenance
We schedule maintenance in overnight windows and announce it here in advance. All times are Mountain Time.
MNT-2610-01
Rolling upgrade of storage controllers, one node at a time with data fully replicated. No customer impact is expected.
MNT-2610-02
Routers are upgraded one at a time. Single-path business circuits may see up to two reroutes of under 60 seconds each; SD-WAN sites fail over automatically.
MNT-2610-03
The data-center operator services one power feed at a time. Racks stay on the redundant feed throughout; no impact expected.
Incident history
Every incident gets a timeline and a plain-English summary. Resolved incidents from the last 90 days:
A third-party construction crew damaged one of the two long-haul fiber paths between Salt Lake City and Los Angeles. Traffic failed over to the second path automatically, but at a higher round-trip time until we re-weighted routing. No packets were dropped and LAX1 workloads kept running.
An analytics database maintenance job started during business hours and slowed dashboard queries. Edge devices, tunnels and customer traffic were not affected. The job now runs only inside the weekly maintenance window.
After a routine certificate renewal, our outbound mail relay queued messages instead of delivering them. Incoming email to noc@ was received normally and no messages were lost; queued replies were delivered once the relay configuration was corrected.
No other incidents in the last 90 days.
Get notified
Email the NOC to be added to our maintenance and incident notification list. We write before planned maintenance and whenever an incident starts, changes or is resolved.
Tell us what you want to hear about