Vendor Status Watch

← all vendors

Samanage status history

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

3incidents, last 30 days
7incidents, last 90 days
29incidents on record
Incidents per week, last 12 weeks:

How long do Samanage incidents last?

4.2 hmedian incident duration29 measured
15.1 h90th percentile1 in 10 ran longer
106 minmedian, major/critical only4 incidents

From 29 incidents with a vendor-posted start and resolve time. Longest on record: Service Desk GenAI is not successfully generating descriptions/summaries in a timely manner. — 6.1 days (2025-10-17 14:29 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 (29)

StartedIncidentStatusImpactDuration
2026-09-10 15:38 UTCElevated 500 errorsresolvedcritical47 min
2026-09-08 14:27 UTCService Desk Slow Performanceresolvedminor1 h 48 min
2026-08-31 15:15 UTCService Desk Slow Performanceresolvedminor2 h 27 min
2026-07-14 14:30 UTCElevated 500 errorsresolvedmajor1 h 31 min
2026-07-07 15:59 UTCDelayed Visibility of Incidents in the Service Desk UIresolvedminor3 h 00 min
2026-06-30 17:22 UTCDelayed Visibility of Incidentsresolvedminor4 h 40 min
2026-06-23 16:14 UTCUS Data Center - Delayed Visibility of Incidentsresolvedminor2 h 16 min
2026-06-03 12:18 UTCService Desk Slow Performanceresolvedminor2 h 07 min
2026-05-06 13:23 UTCError 500: Service interruptionresolvedmajor2 h 01 min
2026-04-29 19:01 UTCError 500: Service interruptionresolvedmajor4 h 27 min
2026-04-03 12:33 UTCSlow Performance & Error 500resolvedminor9 h 23 min
2026-03-18 09:14 UTCOverlapping Text Fields in Incident/Service Request Ticketsresolvedminor4 h 15 min
2026-02-02 15:49 UTCApplication Slow Performanceresolvedminor3 h 05 min
2026-01-28 19:54 UTCIntermittent issues loading service requestsresolvedminor18 h 17 min
2026-01-27 18:51 UTCUS & AU Data Centers - Service Request Approval Workflow Issueresolvedminor9 h 58 min
2026-01-27 00:03 UTCAU DC - New Tickets Not Appearing in Service Desk UIresolvedminor2 h 06 min
2026-01-12 19:49 UTCApplication Slow Performanceresolvedminor6 h 34 min
2026-01-12 07:43 UTCNew tickets that were created are not appearing in the Service Desk UIresolvedminor4 h 45 min
2026-01-09 09:27 UTCScheduled Service Catalog Item Not Runningresolvedminor1 h 32 min
2026-01-06 10:47 UTCService Desk Application Performance Degradationresolvedminor7 h 11 min
2026-01-05 13:35 UTCService Desk Round-Robin Assignment Option Problemresolvednone5 h 38 min
2025-11-18 13:32 UTCPossible Service Desk Features Degradationresolvednone9 h 45 min
2025-10-20 11:29 UTCPerformance Issue with Service Desk US Datacenterresolvedminor15 h 03 min
2025-10-17 14:29 UTCService Desk GenAI is not successfully generating descriptions/summaries in a timely manner.resolvedminor6 d 3 h
2025-10-02 20:15 UTCUS Data Center - System Performance Issuesresolvedminor3 h 09 min
2025-09-30 09:58 UTCError 500 - Computer Assets Details Pageresolvednone4 h 14 min
2025-09-04 14:49 UTCUser Search Not Returning Resultsresolvednone17 h 35 min
2025-09-03 17:15 UTCUS Data Center – Intermittent Latencyresolvedminor7 h 17 min
2025-08-26 13:59 UTCDelay in Incident Creationresolvedminor3 h 07 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 Samanage with the template

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

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