Network Operations Center & Uptime
SWWWC network operations center posture for BEAD reviewers and procurement officers — 24/7 NOC staffing, monitoring tooling and probe coverage, escalation tiers tied to the 99.9% business SLA, scheduled maintenance windows, change management, and on-call contact.
Current measured uptime — same data as /status
This number is the same 30-day rolling uptime that appears on the BEAD submission package at /grants. Both pages read the SQL rollup directly from the monitoring_probes table — there is no manual override. When probes fail, both numbers move together.
Continuity. The values on this page mirror the same monitoring_probes rollup that powers the public /status page and the FEAD headline at /grants. Reviewers cross-referencing the three pages should see identical numbers — when they do not, the SQL aggregation is the source of truth.
24/7 in-house on-call rotation
SWWWC operates its network operations center in-house. There is no third-party SOC referral in the response path — incidents are detected, triaged, contained, notified, and reviewed internally by named operators.
Synthetic probes against every tower-site target
Synthetic uptime probes (UptimeRobot / SmokePing) run against every tower-site target. Probe rows are summarized into the monitoring_probes table, which is the same source of truth that powers the public /status page.
Continuity. These rows are mirrored live at /status — both pages read the monitoring_probes table. The per-probe uptime cards on /status show the same probe_source / site_id / target tuples listed above, with the live uptime_pct and last_checked_at pulled from the same query.
T1 / T2 / T3 — tied to the 99.9% business SLA
Each tier has an ack window (the maximum time between incident detection and operator acknowledgement), a mitigation window (the target time to restore service or contain the issue), and a notify window (the target time to publish a customer-facing update).
T1 incidents count against the 99.9% business SLA referenced on /infrastructure and in §6 of the capability statement. The 30-day rolling uptime shown above is the same number those SLA windows are measured against.
T2 incidents are escalated to named NOC leadership, the on-call rotation is doubled, and customer-facing notification is dispatched within the public update window.
T3 incidents trigger direct coordination with the upstream provider, an SWWWC executive-level briefing, and a public status-posted RCA within 5 business days.
Tier 1 specifically. T1 incidents count against the 99.9% business SLA referenced on /infrastructure and in §6 of the capability statement. The 30-day rolling uptime shown above is the same number those SLA windows are measured against — there is no separate, manually-tuned SLA per tier.
Standing window, advance notice, and review cadence
SWWWC schedules network-impacting changes inside standing maintenance windows with minimum advance notice. Emergency changes (reactive patches to a production-impacting issue) follow a shorter path with mandatory post-hoc review.
Active maintenance notice slot. For the current active maintenance window, see /status — that page is authoritative for the live state. The fields above describe the standing policy, not a specific scheduled event.
End-to-end in-house network physical layer
SWWWC builds and owns the network physical layer end-to-end — 32+ tower sites across 6,400+ square miles, dual upstream providers for path redundancy, in-house tower crews, and synthetic monitoring against every site. Per-site sector counts, capacity per sector, equipment detail, and the full coverage map are available at /infrastructure; per-site sector detail is one click deeper at /infrastructure/<site>.
24/7/365 named operator, escalation email, and emergency line
Customers, grant reviewers, and partner organizations reach the SWWWC NOC through the channels below. The NOC lead is the named primary; the email routes into the on-call rotation; the emergency line is answered live 24/7/365 by the on-call operator.
BEAD reviewer cross-links
The artifacts listed below compose the standing BEAD submission package. Each one is one click deep — reviewers verify there is no drift between the capability statement, the live status page, the security posture, and this network operations artifact.
Need a network operator?
Grant reviewers, ISP partners, and enterprise prospects — reach the SWWWC NOC directly on questions about coverage, capacity, monitoring, or service-level commitments. We respond to government and enterprise inquiries within one business day.