Sydney Datacentre - Unplanned carrier outage - 24 Apr 2020, 2:12 AM

Customer Identification: Customer services via Sydney Datacentre
Start Date: 24 Apr 2020, 2:12 AM 
End Date:24 Apr 2020, 2:57 AM
Event Type: Un-Planned outage in upstream carrier
Subject: Service degradation via Sydney datacenter
Expected Service Impact: Any customer hosted applications via Sydney datacenter 



RedShield's Sydney datacenter service provider experienced an intermittent network connectivity issue, that lasted for approximately 45 minutes. The RedShield monitoring systems detected a service interruption affecting monitor probes from Australia, USA and New Zealand for an impact period of 10-11 minutes, whilst probes from Asia locations showed no issues.

The affected traffic was automatically redirected to the backup datacenters using DNS redirection within 1-2 minutes of monitor failure. Some customers using RedShield's anycast network would have experienced service disruption, on those hostnames which cannot be automatically redirected by DNS. BGP routes were not withdrawn due to the brief nature of the incident. 

RedShield's Sydney datacenter network is provided by IBM, uses redundant hardware and connectivity, and directly peers with 1,956 other service providers.  

The issue has been resolved by IBM and no further updates on this are expected. Please open a support ticket with RedShield via if any further information is required. 


Below is IBM's service announcement advising of the issue:


Start time: 24 Apr 2020, 2:12 AM
End time: 24 Apr 2020, 2:57 AM
Update time: 24 Apr 2020, 02:57
Severity: Medium


Network Specialists were alerted to a loss of connectivity to dar02.syd04. Customer hosts located in the SYD04 data-center may be experiencing intermittent network connectivity at this time. Network specialists are currently investigating.

Update History
- As of Thursday 23-Apr-2020 14:57 UTC
At 23 April 2020 14:42 UTC, connectivity to dar02.syd04 was restored mitigating any impact. Network specialists are working with the vendor to determine the cause of this failure.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request