NetDocuments AU status history
Current state: operational — “All Systems Operational” per https://trust-au.netdocuments.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do NetDocuments AU incidents last?
From 8 incidents with a vendor-posted start and resolve time. Longest on record: Performance Metrics Not Loading — 10.7 days (2026-02-02 22:18 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (8)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-03 02:18 UTC | Service Disruption - AU Service | resolved | minor | 2 h 00 min |
| 2026-07-16 09:59 UTC | M365 Outlook and Co-Author Login Error | resolved | minor | 2 h 32 min |
| 2026-03-02 22:51 UTC | Service Incident | resolved | critical | 1 h 35 min |
| 2026-02-25 14:51 UTC | Performance Metrics Not Loading | resolved | none | 2 d 0 h |
| 2026-02-17 14:55 UTC | Performance Metrics Not Loading | resolved | none | 3 d 0 h |
| 2026-02-02 22:18 UTC | Performance Metrics Not Loading | resolved | none | 10 d 16 h |
| 2025-10-05 22:43 UTC | NetDocuments E-mail Filing | resolved | minor | 4 h 31 min |
| 2025-09-30 17:22 UTC | Service Disruption | resolved | major | 1 h 04 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch NetDocuments AU with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"netdocuments-au"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}