FireNet incident

NT based services interuption

Minor Resolved View vendor source →

FireNet experienced a minor incident on May 1, 2017, lasting 18h 58m. The incident has been resolved; the full update timeline is below.

Started
May 01, 2017, 10:37 AM UTC
Resolved
May 02, 2017, 05:36 AM UTC
Duration
18h 58m
Detected by Pingoru
May 01, 2017, 10:37 AM UTC

Update timeline

  1. identified May 01, 2017, 10:37 AM UTC

    Engineers have identified a fault that is causing a disruption to NT based services. The outage has been caused by a fibre break. 3rd party engineers are currently investigating. Further updates to follow. Please contact the FireNet NOC should you have any questions, comments, or concerns. Email: [email protected] Phone one of the following numbers: Australia: 1300 636 636 International customers please call +61 2 9397 7050

  2. identified May 01, 2017, 12:22 PM UTC

    3rd party engineers have located the fibre break near Katherine NT, 3rd Party Fibre crew advised, no ETA. Further updates to follow.

  3. identified May 01, 2017, 03:07 PM UTC

    3rd Party confirmed a fibre crew has been dispatched from Darwin and on route to break site near Katherine, no ETA available. Further updates to follow

  4. identified May 01, 2017, 10:46 PM UTC

    3rd Party Fibre Techs have located the fibre break caused by heavy machinery. They are currently investigating what is required to restore service. Further updates to follow.

  5. identified May 01, 2017, 11:31 PM UTC

    3rd party carrier advises techs on site excavating the damaged area. Further updates to follow

  6. identified May 02, 2017, 02:04 AM UTC

    3rd party carrier advises that excavation completed. Fibre being prepared for splicing. ETR TBA

  7. identified May 02, 2017, 02:56 AM UTC

    Fibre splicing under way. ETR 14:00 AEST Further updates to follow

  8. monitoring May 02, 2017, 04:01 AM UTC

    All services restored at 01:31 PM. Will confirm with 3rd party carrier if this is a permanent fix. NOC monitoring.

  9. resolved May 02, 2017, 05:36 AM UTC

    Carrier advises that no further impact is expected.