An ISP escalates to an FNO only after confirming an access-layer fault through structured diagnostics. Escalation requires validated WAN sync failure, verified router integrity, and elimination of LAN or ISP-core issues.
Understanding the ISP vs FNO Responsibility Boundary
In South Africa’s open-access fibre model:
- The ISP manages authentication, routing, and customer support
- The FNO (Fibre Network Operator) owns the physical fibre infrastructure and access layer
Escalation is not automatic. It occurs only when the fault is confirmed to be within the FNO-controlled access layer. Accurate classification protects repair timelines and prevents rejected tickets.
What Counts as an Access-Layer Fault?
An access-layer fault typically includes:
- Loss of WAN sync
- Physical fibre break
- OLT port failure
- Signal loss between ONT and exchange
- Infrastructure outage in the area
It does not include:
- WiFi instability
- Router misconfiguration
- Device issues
- ISP authentication errors
Escalation must match responsibility ownership.
Step-by-Step Escalation Criteria
Automated Diagnostic Trigger
- Support Robotics identifies WAN disconnect events, repeated session drops, device unreachable state, and persistent sync failure.
- See detection logic: How Support Robotics Detects Fibre Line Faults.
- No escalation occurs yet.
ACS Telemetry Validation
- Agents confirm router online/offline status, WAN sync state, session authentication logs, and uptime and reboot history.
- If router is reachable and WAN active, the issue is not access-layer. If router is unreachable and WAN shows loss of sync, access-layer suspicion increases.
Eliminate Customer-Side Causes
- Before escalation: Ethernet and cable integrity verified, router hardware confirmed operational, power supply confirmed stable, and internal configuration reviewed.
- If an internal cause is detected, escalation is stopped.
Confirm Persistent WAN Sync Failure
- Escalation requires confirmed WAN down state — not a transient drop, not a short reconnect cycle, and not an authentication-only failure.
- Repeated and persistent sync failure indicates access-layer fault.
Structured Escalation to FNO
- Once validated: fault details compiled, signal state documented, diagnostics attached, and escalation logged formally.
- See lifecycle context: What Happens After You Log a Fibre Ticket?
- This ensures the FNO receives a validated fault report, not a speculative complaint.
Key Term: WAN Sync
The physical and logical connection state between the customer’s ONT/router and the fibre access network. Loss of WAN sync indicates a potential access-layer disruption requiring FNO investigation.
Why Escalation Cannot Be Immediate
Immediate escalation without validation causes:
- Ticket rejection by FNO
- Delayed repair
- Repeat troubleshooting
- Extended downtime
FNOs require confirmed access-layer evidence before dispatch. Structured escalation improves resolution speed overall.
Multi-FNO Environment (South Africa)
UrbanX operates across:
- Vumatel
- Openserve
- Frogfoot
- MetroFibre
- Other regional FNOs
Each FNO has separate diagnostic processes, escalation acceptance criteria, and dispatch timelines. Accurate pre-escalation validation ensures faster acceptance, fewer rejections, and reduced repeat tickets.
When Escalation Is NOT Required
Escalation does not occur if:
- Router is reachable and WAN active
- Issue isolated to WiFi
- Authentication error exists
- Short transient drop occurred
- Device misconfiguration detected
Responsibility boundary determines escalation.
What Happens After Escalation
After escalation:
- FNO acknowledges ticket
- Access-layer diagnostics begin
- Field dispatch scheduled if required
- Repair status updated
The ISP continues monitoring during this process.