Vendor Status Watch

← all vendors

Exalate status history

Current state: operational — “All Systems Operational” per https://status.exalate.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
5incidents, last 90 days
20incidents on record
Incidents per week, last 12 weeks:

How long do Exalate incidents last?

5.8 hmedian incident duration20 measured
27.4 h90th percentile1 in 10 ran longer
5.0 hmedian, major/critical only10 incidents

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)

StartedIncidentStatusImpactDuration
2026-08-27 04:36 UTCAtlassian has an active incident that might be affecting your connectionspostmortemnone51 min
2026-07-24 06:12 UTCApp name change/proxy user on Atlassian Jira Cloudresolvedminor10 h 20 min
2026-07-16 11:28 UTCJiraCloud nodes experiencing some instablilityresolvedminor5 h 50 min
2026-07-13 22:15 UTCExalate looping synchronizations in Jira Cloud forge apppostmortemcritical23 h 59 min
2026-06-23 09:10 UTCExalate.app is not loading the connections.postmortemmajor3 h 37 min
2026-05-04 13:24 UTCSome exalate cloud nodes unavailableresolvedminor8 h 03 min
2026-04-15 09:03 UTCExalate.app Not loading workspacespostmortemmajor3 h 13 min
2026-04-06 11:07 UTCExalate.app Not loading workspacespostmortemmajor4 h 23 min
2026-04-02 15:41 UTCSome Exalate Nodes are currently unreachableresolvedmajor5 h 44 min
2026-03-16 15:13 UTCExalate App unavailablepostmortemminor2 h 00 min
2026-03-13 11:56 UTCExalate Website Unavailablepostmortemminor6 h 22 min
2026-03-09 06:59 UTCSome exalate cloud nodes unavailablepostmortemminor2 h 00 min
2026-01-23 09:59 UTCExalate.app page is not loading.postmortemcritical2 h 18 min
2025-12-12 16:15 UTCExalate nodes unrachablepostmortemmajor12 h 10 min
2025-11-27 11:47 UTCSome Exalate nodes are unavailablepostmortemmajor19 h 21 min
2025-11-20 09:43 UTCSyncRoom website and Community not loading.postmortemminor1 h 39 min
2025-10-04 06:18 UTCSome Exalate nodes down (specially on Jira Cloud)postmortemmajor35 min
2025-10-03 09:43 UTCJira Cloud: Script Configuration Update Availablepostmortemminor33 d 4 h
2025-09-24 10:56 UTCSome Exalate nodes unavailablepostmortemmajor27 h 25 min
2025-08-29 16:18 UTCJira Cloud IssueLinks being Removedpostmortemminor6 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
}