Identified - Optus Engineers have detected an inland break on the Sydney to Melbourne IOF between Campbellfield and Sunshine Exchanges in Victoria. This outage is also impacting the Melbourne to Adelaide IOF. Optus Fibre Engineers have assessed the damage. Conduits are broken 2 metres
deep from the surface. Conduits will need to be excavated. This is expected to take 3-4 hours. Splicing will commence after this has completed

Any faults on Optus NBN/ULL/Mobile in affected areas should be considered to be part of this outage.
Jun 26, 16:50 AEST
Update - AAPT/TPG has been advised that Telstra continues to progress with the rebuild of the Parklea exchange. There is no timeframe available yet for the completion of this work.

Telstra has advised that the temporary structures have been scheduled to be relocated to the Parklea site on 22/06/2017. The integration of the structures to the exchange is expected to occur. The relevant drawings are then expected to be provided to AAPT/TPG to allow the Fibre and Field Technicians to plan and reinstate Fibre work. The 3rd party provider is expected to commence the re-termination of Copper cabling and complete the jumpering to the AAPT/TPG equipment over the following week. No ETR has been provided by Telstra for service restoration.

The next update will be provided on 26/06/2017 or as soon as further information becomes available.
Jun 20, 13:09 AEST
Update - AAPT/TPG has been advised that Telstra continues to progress with the rebuild of the Parklea exchange. There is no timeframe available yet for the completion of this work.

Telstra has authorised the final work to be completed on the temporary structures. This work involves the installation of the MDF and Power to the AAPT/TPG rack. AAPT/TPG technicians are scheduled to complete this work by 15/06/2017. The temporary structures are expected to be transported to the Parklea site by 16/06/2017. Integration of the structures to the exchange foundation is expected to commence with no ETR available from Telstra for this work as yet.

An ETR for total service restoration is unavailable. The next update will be provided on 19/06/2017 or as soon as further information becomes available.
Jun 13, 14:33 AEST
Update - AAPT/TPG has been advised that Telstra continues to progress with the rebuild of the Parklea exchange. There is no timeframe available yet for the completion of this work.

The site has been cleared and council approvals have been granted which has allowed the exchange foundation (concrete slab) to be completed. The work continues in preparation for the prefabricated structures to be delivered and installed. Final assembly of cabling and power is expected to occur after the prefabricated structures are delivered.

AAPT/TPG has completed the installation of equipment at the Erskine Park staging site. The delivery of the prefabricated structures to the Parklea site has not been confirmed but is possibly expected to occur by 09/06/2017.

An ETR for total service restoration is unavailable. The next update will be provided on 12/06/2017 or as soon as further information becomes available.
Jun 7, 12:21 AEST
Update - AAPT/TPG has been advised that Telstra continues to progress with the rebuild of the Parklea exchange. There is no timeframe available yet for the completion of this work.

While the rebuild continues at Parklea, equipment is being prepared at a temporary staging site in Erskine Park. AAPT/TPG staff have been approved for induction and installation of equipment into the Erskine Park site on 30/05/2017.

Final assembly of cable and power at the Parklea site is expected to occur when the replacement structures are delivered from the temporary staging site. No ETA has been provided on when the temporary structures are to be delivered to the Parklea site.

An ETR for total service restoration is unavailable. The next update will be provided on 05/06/2017 or as soon as further information becomes available.
May 29, 11:56 AEST
Update - AAPT have further advised today that they expect the rebuild of core infrastructure at the exchange to require a further two weeks, at which point AAPT can commence restoring services.
May 19, 09:29 AEST
Update - Telstra's service status has updated to indicate service restoration between Friday 19th May and Monday 29th May, however these dates are subject to change. AAPT have advised they expect to be restoring services next week, however this is dependent on site cleanup.
May 17, 09:48 AEST
Update - Telstra have advised that some services have been restored over the weekend, however we anticipate that issues relating to this outage will continue for several weeks due to the complexity of the event and the complete destruction of the exchange caused by the fire.
May 15, 10:18 AEST
Update - Telstra are still waiting for the arrival of the MEOW. We have also been advised of a substantial amount of toxic materials on site which need to be removed before service restoration can occur.
May 10, 14:03 AEST
Update - Telstra are deploying the Mobile Exchange on Wheels (MEOW) from Victoria and it should arrive today.
May 10, 11:07 AEST
Update - Some photos of the external damage: https://twitter.com/big_gaffa/status/861778669324382208
May 9, 14:16 AEST
Update - Site investigations have been completed, and Telstra has determined they are deploying a mobile exchange to the site to begin to restore services. There is no Estimated Time for Restoration at this stage.
May 9, 13:11 AEST
Identified - Telstra has advised of a fire in the Parklea Exchange overnight. The exchange is currently inoperable. Services fed from this exchange are offline at present with no ETR.
May 9, 09:10 AEST
Network Services Degraded Performance
IP Transit Operational
Ethernet services Operational
NBN Degraded Performance
ADSL Services Operational
Fixed Wireless Ethernet Operational
Intercapital Capacity Operational
3G/4G Data Services Degraded Performance
Private WAN (MPLS VPN) Operational
Managed VPN Operational
Voice Services Operational
Voice trunking Operational
Hosted voice Operational
ISDN Services Operational
Telstra Rebill Operational
Email Services Operational
SpamCloud Operational
Hosted Exchange Operational
POP/IMAP Legacy Email Operational
Hosting and Data Centre Operational
Virtual Machine Hosting Operational
Co-location Operational
Web Hosting Operational
Managed Backup (Dell Rapid Recovery) Operational
Managed Backup (Veeam) Operational
Billing Systems Operational
Helpdesk Services Operational
AWS cloudFront Operational
AWS ec2-ap-southeast-2 Operational
AWS ec2-ap-southeast-1 Operational
Xero Ltd - API Accounting API Operational
Xero Ltd - API Files API Operational
Xero Ltd - API Payroll API Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
Network Availability (syd01 Data Centre)
Fetching
Network Availability (syd02 Data Centre)
Fetching
Network Availability (mel01 Data Centre)
Fetching
SIP Trunking Availability
Fetching
Hosted Voice Availability
Fetching
Past Incidents
Jun 25, 2017

No incidents reported.

Jun 24, 2017

No incidents reported.

Jun 23, 2017

No incidents reported.

Jun 22, 2017

No incidents reported.

Jun 21, 2017

No incidents reported.

Jun 19, 2017

No incidents reported.

Jun 18, 2017

No incidents reported.

Jun 17, 2017

No incidents reported.

Jun 16, 2017

No incidents reported.

Jun 15, 2017

No incidents reported.

Jun 14, 2017

No incidents reported.

Jun 13, 2017
Resolved - The issue appears to be isolated to Asterisk and Asterisk derivative PBX platforms which stop registering after receiving a 'Forbidden - wrong password on authentication' method.

The issue is supposedly fixed in asterisk builds following 1.8.25, 11.8 and 12.1. More details about the bug and the patch that was introduced are at https://issues.asterisk.org/jira/browse/ASTERISK-17138
Jun 13, 11:54 AEST
Identified - Earlier this evening we experienced an issue with our SIP platform that temporarily rejected a number of SIP registration requests resulting in SIP peers being unable to reach our switching platform.

We have observed that some customer systems running, in particular the Asterisk PBX software, have not correctly recovered once the issue was resolved. We have identified that issuing a 'sip reload' or Asterisk restart will cause the PBX to renew its registration request against our servers.
Jun 12, 23:34 AEST