Update - This is a fault between two network segments interconnected using a third party, we are actively building our own capacity between the two segments with redundant paths via other carriers.
Other network segments in service are unaffected.
We apologise for any inconveniences this fault is causing.
Dec 12, 22:02 AEDT
Update - We are still waiting on our upstream suppliers parts to come in, this has taken too long and at this point we have decided that we will be selecting a new provider of our primary backhaul capacity and have put out an RFQ to selected suppliers for service provision in January / February.
We have also issued an RFQ to equipment suppliers for high capacity microwave hardware capable of supplying the full peak requirements of our network for the foreseeable future.
In the interim we are working on additional capacity that should satisfy normal usage requirements over the christmas break and/or until our primary capacity comes online or is replaced.
We are negotiating with contractors to get the additional temporary installed as soon as possible, however weather has been an issue in the last few days.
We will provide further updates as they come to hand.
Dec 12, 16:03 AEDT
Update - An email has been sent to all customers with information pertaining to this fault. This email was sent at approximately 1pm. If you have not received this email please check your spam or junk folders.
Dec 8, 13:30 AEDT
Update - Engineers are continuing to work on restoring the primary backhaul path. We apologise for the inconvenience.
Dec 7, 15:59 AEDT
Update - We have implemented a **temporary fix** for the affected network path, with this in mind we have **temporarily** reduced the maximum speed of customer services in order to accommodate the smaller link and keep a level of QoS over this link.
Engineers are working on a solution to bring the primary link back into service as soon as possible.
Dec 6, 13:39 AEDT
Identified - The issue has been identified and a fix is being implemented.
Dec 6, 11:52 AEDT
Investigating - We are currently investigating this issue.
Dec 6, 08:45 AEDT