# Typical Fibre Repair Timelines in South Africa

Source: https://urbanx.co.za/knowledge-hub/support-diagnostics/typical-fibre-repair-timelines-sa

**Answer:** After confirmed FNO escalation, individual fibre faults typically resolve within 1–3 business days, while area outages can take 24–72+ hours depending on severity, civil damage, and dispatch scheduling. Repair time depends on fault classification and access-layer conditions.

Part of [Gamer-Centric Support & Intelligent Diagnostics](https://urbanx.co.za/knowledge-hub/support-diagnostics) · 9 min read · by UrbanX Support Engineering

## Understanding Repair Responsibility

In South Africa’s open-access fibre model:

- The ISP manages diagnostics and escalation
- The FNO (Fibre Network Operator) manages the physical access layer
- Repair timelines begin only after escalation is accepted

Escalation reference: [When Does an ISP Escalate to an FNO?](/knowledge-hub/support-diagnostics/isp-escalate-to-fno). Repair time does not include pre-escalation validation inside the ticket lifecycle.

## Repair Progression Flow

1. **Escalation Acceptance**
   - After structured validation: ticket submitted to FNO, access-layer fault documented, and telemetry evidence attached.
   - FNO reviews and accepts the escalation. Time impact: same-day to next business day acknowledgement.
2. **Outage Classification**
   - The fault is classified as: individual line fault, area outage, civil damage incident, or infrastructure equipment failure.
   - Classification determines dispatch priority and scheduling model.
3. **Dispatch Scheduling**
   - If field intervention is required: technician slot assigned, access permission confirmed (estate, complex, locked cabinet), and travel time scheduled.
   - Delays occur if access is restricted, weather conditions are unsafe, or civil teams are required.
4. **Physical Repair**
   - Repair actions may include fibre re-splicing, drop cable replacement, OLT port reset, cabinet repair, or line re-termination.
   - Complex repairs involving trenching or pole work extend timelines.
5. **Signal Restoration & Verification**
   - After repair: WAN sync restored, access-layer signal validated, and ISP monitoring confirms stability.
   - Ticket then proceeds to resolution confirmation: [What Happens After You Log a Fibre Ticket?](/knowledge-hub/support-diagnostics/after-logging-fibre-ticket)

## Individual Fault vs Area Outage

| Fault Type | Typical Timeline | Variables Affecting Duration |
| --- | --- | --- |
| Individual Line Fault | 1–3 business days | Technician availability, access permission |
| Area Outage | 24–72+ hours | Infrastructure damage severity |
| Civil Damage | 2–5+ days | Trenching, municipal approval |
| OLT/Exchange Equipment Failure | 24–48 hours | Replacement hardware availability |

> **INFO:** These are general operational ranges, not guaranteed SLA contracts.

## Factors That Extend Repair Timelines

Several real-world factors can push repairs beyond typical windows:

- Weather conditions — heavy rain, lightning, or flooding delays field dispatch
- Estate or complex access — technicians require access clearance for cabinets and distribution points
- Civil infrastructure damage — if fibre is cut due to construction, splicing is required with possible municipal coordination and multiple teams involved
- Hardware replacement — exchange-level component replacement increases downtime

## Key Term: Access-Layer Fault

- **Access-Layer Fault** — A physical or signal-level failure between the ONT and the fibre distribution network (cabinet or exchange), requiring FNO intervention and possible field dispatch.

## Residential vs Business Services

Residential services typically operate under best-effort SLA windows. Business-grade services may include:

- Shorter dispatch windows
- Priority classification
- Faster escalation handling

However, physical repair complexity still affects total downtime.

## Why Some Repairs Exceed Expected Timeframes

Repair time may extend when:

- Escalation requires additional validation
- Fault is intermittent and not reproducible
- Area outage affects multiple subscribers
- Civil teams are required
- Replacement fibre stock is limited

> **WARNING:** Structured escalation reduces rejection but cannot eliminate infrastructure dependency.

## South African Multi-FNO Context

UrbanX operates across:

- Vumatel
- Openserve
- Frogfoot
- MetroFibre
- Regional FNOs

Each FNO has independent dispatch systems, separate repair queues, and different operational capacity. Repair duration reflects FNO operational workflow, not ISP routing performance.

## What Does NOT Affect Repair Time

The following are not access-layer issues and do not enter FNO repair queues:

- NAT type
- Game server congestion
- WiFi instability
- International routing latency

> **INFO:** Only confirmed access-layer faults enter FNO repair queue.

## Frequently Asked Questions

**Does escalation guarantee same-day repair?**

No. Escalation initiates repair workflow but dispatch scheduling depends on FNO capacity.

**Why do area outages take longer?**

They often involve shared infrastructure damage affecting multiple subscribers.

**Can weather delay fibre repair?**

Yes. Field safety protocols can delay dispatch.

**Does rebooting help once escalated?**

No. Physical access-layer faults require FNO intervention.

**Can the ISP speed up FNO repair?**

The ISP can provide validated diagnostics, but physical repair scheduling remains FNO-controlled.