Exalate status history
Current state: operational — “All Systems Operational” per https://status.exalate.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Exalate incidents last?
From 20 incidents with a vendor-posted start and resolve time. Longest on record: Jira Cloud: Script Configuration Update Available — 33.2 days (2025-10-03 09:43 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 (20)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-27 04:36 UTC | Atlassian has an active incident that might be affecting your connections | postmortem | none | 51 min |
| 2026-07-24 06:12 UTC | App name change/proxy user on Atlassian Jira Cloud | resolved | minor | 10 h 20 min |
| 2026-07-16 11:28 UTC | JiraCloud nodes experiencing some instablility | resolved | minor | 5 h 50 min |
| 2026-07-13 22:15 UTC | Exalate looping synchronizations in Jira Cloud forge app | postmortem | critical | 23 h 59 min |
| 2026-06-23 09:10 UTC | Exalate.app is not loading the connections. | postmortem | major | 3 h 37 min |
| 2026-05-04 13:24 UTC | Some exalate cloud nodes unavailable | resolved | minor | 8 h 03 min |
| 2026-04-15 09:03 UTC | Exalate.app Not loading workspaces | postmortem | major | 3 h 13 min |
| 2026-04-06 11:07 UTC | Exalate.app Not loading workspaces | postmortem | major | 4 h 23 min |
| 2026-04-02 15:41 UTC | Some Exalate Nodes are currently unreachable | resolved | major | 5 h 44 min |
| 2026-03-16 15:13 UTC | Exalate App unavailable | postmortem | minor | 2 h 00 min |
| 2026-03-13 11:56 UTC | Exalate Website Unavailable | postmortem | minor | 6 h 22 min |
| 2026-03-09 06:59 UTC | Some exalate cloud nodes unavailable | postmortem | minor | 2 h 00 min |
| 2026-01-23 09:59 UTC | Exalate.app page is not loading. | postmortem | critical | 2 h 18 min |
| 2025-12-12 16:15 UTC | Exalate nodes unrachable | postmortem | major | 12 h 10 min |
| 2025-11-27 11:47 UTC | Some Exalate nodes are unavailable | postmortem | major | 19 h 21 min |
| 2025-11-20 09:43 UTC | SyncRoom website and Community not loading. | postmortem | minor | 1 h 39 min |
| 2025-10-04 06:18 UTC | Some Exalate nodes down (specially on Jira Cloud) | postmortem | major | 35 min |
| 2025-10-03 09:43 UTC | Jira Cloud: Script Configuration Update Available | postmortem | minor | 33 d 4 h |
| 2025-09-24 10:56 UTC | Some Exalate nodes unavailable | postmortem | major | 27 h 25 min |
| 2025-08-29 16:18 UTC | Jira Cloud IssueLinks being Removed | postmortem | minor | 6 d 19 h |
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 Exalate with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"exalate"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}