AARNet Support Outage History
8 incidents recorded over the last 365 days, 2 of them resolved, 1 still open. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded AARNet Support Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 10, 2026 | Planned Outage: JIRA (ticket.aarnet.edu.au)Scheduled maintenance is currently in progress. We will provide updates as necessary. | 4h 0m | Scheduled |
| Sep 23, 2026 | Asia/Europe International Connectivity - DegradedRepair and restoration activities continue across the affected international subsea cable systems, with progress made on several repairs and revised restoration timelines provided by our cable partners. The latest… | — | Investigating |
| Apr 23, 2026 | AARNet Mirror in degraded stateAll workarounds have been reverted, and Mirror is now working as expected. Fault resolved. | 182h 46m | Resolved |
| Mar 31, 2026 | Jira platform is unavailableThis incident has been resolved. | 35 min | Resolved |
| Feb 27, 2026 | Planned Maintenance - Service Management PortalThe scheduled maintenance has been completed. | 15 min | Scheduled |
| Feb 21, 2026 | Planned Maintenance - Salesforce Customer PortalThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Nov 27, 2025 | Planned Maintenance Notice: AARNet Service Management PortalThe scheduled maintenance has been completed. | 1h 30m | Scheduled |
| Nov 6, 2025 | Planned Maintenance Notice: AARNet Service Management PortalMaintenance has been completed | 3h 30m | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next AARNet Support incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This AARNet Support Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before AARNet Support acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single AARNet Support outage in this window ran 7d 14h, against a mean recovery of 1d 3h. If you depend on AARNet Support in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.