Good Day,
We are experiencing the following network incident.
Network Incident Reference: #1170 Network Incident Description: Confirmed Fibre Break Area/s Affected: Bryanston South Network Type Affected: Active Ethernet Current Resident Impact: Residents have no connectivity Current Network Incident Status: Technicians are on-site localising the fault
4 Comments. Leave new
Good Day,
Network Incident Reference: #1181 Network Incident Description: Confirmed Fibre Break Area/s Affected: Bryanston South Network Type Affected: Active Ethernet Current Resident Impact: Residents have no connectivity Current Network Incident Status: Technicians have localised the fault and are evaluating the repair needed
On Fri, Apr 26, 2019 at 10:24 AM Vumatel Network Incident < networkincident@vumatel.co.za> wrote:
Good Day,
Network Incident Reference: #1181 Network Incident Description: Confirmed Fibre Break Area/s Affected: Bryanston South Network Type Affected: Active Ethernet Current Resident Impact: Residents have no connectivity Current Network Incident Status: Technicians have localised the fault and have started repairs
On Fri, Apr 26, 2019 at 11:25 AM Vumatel Network Incident < networkincident@vumatel.co.za> wrote:
Good Day,
Network Incident Reference: #1181 Network Incident Description: Confirmed Fibre Break Area/s Affected: Bryanston South Network Type Affected: Active Ethernet Current Resident Impact: Residents have no connectivity Current Network Incident Status: Technicians are still busy with repairs
On Fri, Apr 26, 2019 at 10:24 AM Vumatel Network Incident < networkincident@vumatel.co.za> wrote:
Good Day
Please note that the following Network Incident has been resolved.
Network Incident Reference: #1181 Network Incident Description: Confimred fibre break Area/s Affected: Bryanston South Network Type Affected: Active Ethernet Current Resident Impact: Connectivity has restored Current Network Incident Status: Technicians have repaired the fibre and services have been restored
On Fri, Apr 26, 2019 at 1:53 PM Pierre Bredahl (WIRUlink Support) < support@wirulink.zendesk.com> wrote: