Sites, circuits, overlays & provider accountability
A branch can have an online router and an unusable business service. AmrudAi brings together site experience, WAN and Internet circuits, SD-WAN paths, shared services and provider evidence so the NOC can identify the affected layer and coordinate the right response.
The application experience
See the complete workspace. Enlarge any image to inspect its panels, navigation and evidence at actual size.
End the branch-versus-provider guessing game.
Bring circuits, SD-WAN edges, tunnels, probes and service checks into one investigation. Independent Sensor views help separate a branch LAN issue, underlay degradation, overlay policy behavior and a destination service problem.
The capability in detail
Compare availability, latency, loss, jitter and service checks across the branch estate. Filter by region, provider, application or service criticality to find common patterns and focus the NOC on sites with the greatest operational impact.
Normalize SD-WAN controller or fabric, site, edge, circuit, overlay tunnel and path entities. Follow how an impaired underlay changes tunnel and service behavior without losing the vendor-specific evidence needed for a deeper investigation.
Connect application or path policy bindings with the relevant SLA/SLO class and observed latency, loss and jitter. Understand which traffic is affected by a path-quality change and compare that result with the service's actual reachability.
Compare branch-to-data-center and data-center-to-branch evidence where available, alongside selected Internet or cloud paths. Historical fingerprints and independent tests help distinguish a local access problem, changed transit path and destination issue.
Link circuit IDs, bandwidth, provider, site, demarcation, primary or backup role and support references to monitored interfaces and paths. Give an escalation the operational context needed to reach the correct provider team.
Review primary and alternate links, overlay state and the observed service result during a failover. Preserve timing, remaining headroom and shared dependencies so a backup that is online is also assessed for its ability to carry the service.
Bring provider status, planned maintenance, outage or restoration timestamps and ticket updates into the incident when exposed by the provider API. Correlate those statements with your own observed path and synthetic results.
Correlate DNS and HTTP checks, VPN tunnel health and SD-WAN evidence with supported SASE/SSE/ZTNA connector or service observations. Follow the services that make a branch usable, with security enforcement remaining in the relevant control system.
Compare circuit availability and path quality with the configured service window, target and exclusions. Carry supporting incidents, evidence quality and provider ownership into repeatable review reports and follow-up actions.
From information to action
Select the branch, business service and complaint window. Compare nearby or similar sites to establish whether the problem is isolated.
Review circuit quality, tunnel/path decisions, DNS and application checks using the same interval.
Compare independent vantages and provider notices. Attach circuit identifiers, path results and relevant symptoms to the ticket.
Confirm usable application reachability and stable path quality, then include the incident in the configured provider or branch service report.
Built around your operating environment
Model branches around their actual circuits, application paths, provider responsibilities and service hours.
Connect the workflow
Yes. Vendor adapters normalize common site, edge, underlay, overlay, path and SLA-class concepts into a shared model. Vendor-specific attributes remain available when they are needed to explain a particular fabric or device behavior.
It compares circuit and interface evidence, independent path tests, branch service checks, overlay state and provider information. Disagreement remains visible; a carrier notice or a single failed probe does not by itself determine the conclusion.
Yes. Failover investigation connects the alternate path's availability, latency, loss, headroom and service checks. That provides evidence about the service after the transition as well as the state of the backup link.
Yes. Circuit and provider ticket information can support the incident and service review. Availability and path-quality calculations use the evidence and responsibility rules defined in your service-assurance policy.
Explore the technology, service dependencies and operating requirements that matter to your team.
Search the complete website · Esc to close · Tab to navigate results