AARNet Outage History

AARNet is up right now

Pingoru has recorded 46 incidents for AARNet: 4 in the last 12 months and 1 in the last 90 days.

Source: status.aarnet.edu.au

46incidents recorded
4last 12 months
1last 90 days
3 daystypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking AARNet in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20261183 of 720 (25%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202610 of 720 (0%)
October 202600 of 524 (0%)

Incidents, newest first

Minor April 23, 2026 AARNet Mirror in degraded state 7d 14h AARNet Mirror

Started Apr 23, 2026, 12:46 AM UTC· resolved Apr 30, 2026, 03:32 PM UTC

  1. investigating Apr 23, 2026, 12:46 AM UTC

    We are aware of an ongoing issue impacting the AARNet Mirror. AARNet Engineers are actively investigating and working to restore normal service as soon as possible.

  2. investigating Apr 23, 2026, 01:19 AM UTC

    Mirror has been restored online but is in a hazardous state with slightly stale data. Root cause investigation is ongoing.

  3. resolved Apr 30, 2026, 03:32 PM UTC

    All workarounds have been reverted, and Mirror is now working as expected. Fault resolved.

Read the full incident report →

Major March 31, 2026 Jira platform is unavailable 35m AARNet Service Management Portal

Started Mar 31, 2026, 04:33 AM UTC· resolved Mar 31, 2026, 05:09 AM UTC

  1. investigating Mar 31, 2026, 04:33 AM UTC

    We are aware of an ongoing issue impacting the Jira platform, affecting both AARNet internal and external users. Our engineering team is actively investigating and working to restore normal service as soon as possible

  2. identified Mar 31, 2026, 04:43 AM UTC

    The issue was identified as being related to the Jira database. Services were restarted to restore normal operation.

  3. resolved Mar 31, 2026, 05:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 27, 2025 Jira platform is unavailable and currently under investigation. 13m Customer Portal, AARNet Service Management Portal

Started Oct 27, 2025, 06:51 AM UTC· resolved Oct 27, 2025, 07:04 AM UTC

  1. investigating Oct 27, 2025, 06:51 AM UTC

    We are aware of an ongoing issue impacting the Jira platform, affecting both AARNet internal and external users. Our engineering team is actively investigating and working to restore normal service as soon as possible

  2. resolved Oct 27, 2025, 07:04 AM UTC

    The Jira outage was caused by a software patch failure that has been resolved and no further disruptions are expected.

Read the full incident report →

Notice May 29, 2025 NOC-113039 AARNet Routing issue (Victoria) 2h 5m

Started May 29, 2025, 11:20 PM UTC· resolved May 30, 2025, 01:25 AM UTC

  1. investigating May 29, 2025, 11:20 PM UTC

    Incident - NOC113039 Incident Start time : 08:28 AEST Description: Routing issue in Victoria We have monitored an unplanned outage in Victoria. Our network operations team is currently investigating the fault. Identification of specific impacted services is in progress and will be shared as soon as possible.

  2. identified May 29, 2025, 11:34 PM UTC

    AARNet has detected an outage impacting Victorian customers. The root cause is unknown at this stage however investigation is underway. Further updates will be provided as soon as more information is available.

  3. monitoring May 29, 2025, 11:49 PM UTC

    AARNet’s operations engineers are continuing to investigate the root cause. Our monitoring system indicates ongoing service recovery however, the service remains in a hazardous state while the fault investigation is in progress.

  4. resolved May 30, 2025, 01:25 AM UTC

    AARNet's operations engineers have mitigated the issue and continue to work to identify the root cause. Services are operational, please contact the NOC directly on 1300 275 662 (option 1) or [email protected] if you are still experiencing issues. Incident Resolution Time : 09:00 AEST

Read the full incident report →