Resound has implemented a system-driven network model where every customer connection updates gaiia in real time. The result is a single live view of the network, accurate enough that Resound's team uses it to enforce SLAs, troubleshoot in real time, and run the foundation of an automated incident management practice. By anchoring subscriber identity and IP assignment to network infrastructure rather than customer equipment, Resound ensures that both security controls and service enforcement remain accurate as the edge environment changes.
Resound is a Texas-based internet provider delivering fiber and fixed wireless services across a rapidly expanding multi-state footprint. Built for resilience, performance, and scale, the network combines modern access technologies with disciplined operational systems to deliver high-quality connectivity across diverse operating environments.
Rather than relying on a single monolithic platform, Resound has engineered a composable network architecture by integrating best-of-breed systems into a cohesive, high-performance operating model. This approach allows the organization to evolve its infrastructure over time while maintaining consistent service delivery and operational control.
As the company scales, Resound’s leadership remains focused on a defining principle: owning the delivery of customer experience through real-time visibility and operational accountability.
As Resound expanded across technologies and markets, the next evolution was clear: ensuring that operational visibility moved at the same speed as the network itself.
Before this work, finding out which subscriber was attached to which upstream device meant reconciling three systems that each knew part of the truth:
Core systems across the network maintained accurate data within their respective domains. However, traditional approaches introduced natural latency between when network conditions changed and when those changes were fully reflected across operational views.
For an organization committed to proactive service delivery and strict SLA adherence, this created an opportunity to build a real-time, system-driven network model that reflects the live state of the network continuously. The main goals were to reduce swivel-chair activities for NOCs and CSRs, and better set the team up for outage management.
When the DHCP lease event fires, Infoblox posts the payload to gaiia. A workflow that Resound's team built in the gaiia Workflow Editor picks it up and runs five steps in seconds:
From both a network engineering perspective and from supporting our field technicians who are interfacing with customers on a day-to-day basis, having live reconciliation happening on our network while we sleep is the closest thing to magic I've seen in this role. We're now actively working to reduce the latency between when an IP changes and when gaiia can see it and apply policies, as well as reducing the human error involved in making every IP change by hand. Our partnership with gaiia was vital for how quickly we were able to move on these issues.
The NOC now operates from a single live subscriber-to-site map. When a network site goes down, the team knows which customers are impacted in seconds, not after piecing it together from CSVs and memory. Field changes propagate cleanly because the router on the truck and the router in the system are the same router. And downstream automation (outage notifications, proactive RMA, capacity reporting) finally has a reliable data layer to stand on.
A rep can see, on the account page, the IP currently leased to the customer and the upstream device serving them. A subscriber reporting packet loss can be traced from their account to the radio they're on in one click. Ticket templates and workflows pull from a single live state, not a periodic dump.
Deployed equipment and the system's record of it stay aligned automatically. A tech who swaps a router doesn't have to update the same change in three places, because the system reflects it the moment the new device pulls a lease. Operational data in the field is now reliable enough to act on without second-guessing.
By implementing a real-time, system-driven model, Resound has established:
Most importantly, by anchoring topology in live network behavior: Resound ensures its operational view reflects actual service delivery conditions, supporting stronger SLA ownership and a more proactive customer experience.
“For us, this is fundamentally about owning the customer experience end-to-end. When your operational view of the network lags behind reality, you’re always reacting. By grounding our topology in live network behavior and automating it through gaiia, we’re able to operate with real-time awareness and ensure customers consistently receive the service levels we’ve committed to.”
