FireNet experienced a notice incident on May 31, 2017, lasting 3h 25m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating May 31, 2017, 11:33 PM UTC
We are aware of issue effecting some customers, Megaports engineering team and network operations team are investigating and will provide updates as they come available. Customers may of noticed intermittent connectivity issues to some local websites.
- investigating May 31, 2017, 11:42 PM UTC
FireNet engineers have disabled the peering link that we have to MegaPort while their engineers investigate. Traffic will flow over different paths so impact should be limited. Further updates to follow.
- monitoring Jun 01, 2017, 12:01 AM UTC
MegaPort have restored services. Megaport will provide further details shortly on the cause of the issue. No further impact is expected. Peering links to Megaport will be enabled shortly.
- resolved Jun 01, 2017, 02:59 AM UTC
Megaport have advised that they had a High CPU Event on our device located at Sydney SY1. This event affected services that connected to and transited that site for the duration of the incident. Megaport engineering is currently investigating the root cause in an effort to avoid a recurrence in the future.