Unplanned Maintenance - QLD ADSL services

Old, inactive threads
Post Reply
shoner
Posts: 756
Joined: Mon Apr 20, 2009 2:50 pm

Unplanned Maintenance - QLD ADSL services

Post by shoner » Tue Jan 31, 2012 11:06 am

Unplanned Maintenance in QLD ADSL connections

Event

We are experiencing routing issue in QLD

Impact

Most ADSL1 and ADSL2 services in QLD are effected

Our engineers are currently working on this in order to rectify the issue as soon as possible.
"Helping Making a Better World"

Log a fault ticket Here
or call Exetel VOIP numbers (02) 8030 1000 or 1300 788 141 (log faults 24x7)
Exetel Support Portal

shoner
Posts: 756
Joined: Mon Apr 20, 2009 2:50 pm

Re: Unplanned Maintenance - QLD ADSL services

Post by shoner » Tue Jan 31, 2012 11:38 am

It appears to be an issue with PIPE networks and is affecting other peering partners as well.

It is still being investigated.
"Helping Making a Better World"

Log a fault ticket Here
or call Exetel VOIP numbers (02) 8030 1000 or 1300 788 141 (log faults 24x7)
Exetel Support Portal

shoner
Posts: 756
Joined: Mon Apr 20, 2009 2:50 pm

Re: Unplanned Maintenance - QLD ADSL services

Post by shoner » Tue Jan 31, 2012 1:10 pm

Our engineers have applied a temporary fix. (peering services disabled)

Most affected services should be working now.
"Helping Making a Better World"

Log a fault ticket Here
or call Exetel VOIP numbers (02) 8030 1000 or 1300 788 141 (log faults 24x7)
Exetel Support Portal

stevecJ
Forum Admin
Posts: 1041
Joined: Wed Jan 06, 2010 9:48 am

Re: Unplanned Maintenance - QLD ADSL services

Post by stevecJ » Tue Jan 31, 2012 8:07 pm

This is still being investigated.

No ETA at the moment.
To Log a fault ticket, please click click here or alternatively call Exetel VOIP numbers (02) 8030 1000 or 1300 788 141 (log faults 24x7)

=================
Exetel Support Portal
=================

HarshaU
Exetel Staff
Posts: 6
Joined: Tue Sep 06, 2011 4:10 pm
Location: Sri Lanka

Re: Unplanned Maintenance - QLD ADSL services

Post by HarshaU » Wed Feb 01, 2012 3:14 pm

PIPE has confirmed that the issue is now resolved.

Post Reply