Vendor Status Watch

← all vendors

Jama Software status history

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

0incidents, last 30 days
4incidents, last 90 days
14incidents on record
Incidents per week, last 12 weeks:

How long do Jama Software incidents last?

73 minmedian incident duration14 measured
3.1 h90th percentile1 in 10 ran longer
70 minmedian, major/critical only7 incidents

From 14 incidents with a vendor-posted start and resolve time. Longest on record: Jama Connect Status — 6.2 h (2026-04-16 10: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 (14)

StartedIncidentStatusImpactDuration
2026-08-06 17:11 UTCJama Connect Statusresolvedmajor43 min
2026-08-04 16:29 UTCJama Connect Statusresolvedcritical1 h 27 min
2026-06-30 16:57 UTCJama Connect Statusresolvedminor15 min
2026-06-19 21:43 UTCJama Connect Statusresolvedminor1 h 16 min
2026-05-24 01:15 UTCJama Connect Performance Degredationresolvedmajor1 h 48 min
2026-05-20 12:58 UTCJama Connect Performance Degredationresolvedminor3 h 08 min
2026-04-30 11:52 UTCJama Connect Statusresolvedminor1 h 41 min
2026-04-16 10:43 UTCJama Connect Statusresolvedmajor6 h 13 min
2026-04-08 18:10 UTCJama Connect Statusresolvedminor2 h 50 min
2026-04-08 06:49 UTCJama Connect Statusresolvedminor34 min
2026-02-25 20:14 UTCJama Connect Statusresolvedmajor32 min
2025-11-12 18:36 UTCJama Connect Performance Degredationresolvedminor12 min
2025-10-23 19:24 UTCJama Connect Statusresolvedmajor42 min
2025-08-25 07:42 UTCJama Connect Statusresolvedmajor1 h 10 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 Jama Software with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "jama-software"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}