Data & accountability
How we show need, reliability pressure, and reporting intent
Donors, municipalities, and block partners asked for one place to see resident demand signals alongside how we plan to report once the network is carrying real traffic.
The tables and charts here come from the survey aggregate file we ship with the site—useful for prioritizing neighborhoods and calibrating subsidy conversations, not a substitute for field verification or live NOC dashboards.
Resident interest snapshot
Counts reflect households in the current aggregate (n=412). “Impact” bars count how often households cited each stressor—respondents could select more than one, so categories are not mutually exclusive.
Where connectivity hurts most
Mentions across surveyed households (multi-select).
Outage frequency (last six months)
Self-reported buckets; tail matters for trust.
When pilot installs generate ticket volume, we will publish refreshed cuts here and cross-link narrative learnings on Updates. Until then, treat this page as a planning mirror aligned with the stewardship commitments on Transparency.
What we report each quarter
Uptime, mean time to restore, incident categories, ticket volume, installs completed, partner satisfaction, and Digital Navigator outcomes roll into a single cadence so residents are not chasing fragments across PDFs and inboxes.
Operations targets (placeholders)
These readouts swap from X / 99.x% placeholders to pilot-backed numbers the moment telemetry and ticketing hooks are stable—same layout, audited values.
During pilots we tag outages so crews fix root causes—not symptoms. Percentages below are a shape example only; live distributions will appear in quarterly packets once ticket data stabilizes.
We report outcomes residents can verify—not intentions buried in footnotes.
Need context for eligibility or pricing?
Address checks stay on the homepage. Affordable access tiers and the estimator live on Affordable access. Resident expectations and escalation paths are summarized on Residents.