Vendor Status Watch

← all vendors

Spiceworks status history

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

0incidents, last 30 days
2incidents, last 90 days
10incidents on record
Incidents per week, last 12 weeks:

How long do Spiceworks incidents last?

6.7 hmedian incident duration10 measured
6.4 days90th percentile1 in 10 ran longer
6.1 hmedian, major/critical only4 incidents

From 10 incidents with a vendor-posted start and resolve time. Longest on record: Cloud Help Desk Mobile App notifications not being sent — 28.0 days (2025-10-07 13: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 (10)

StartedIncidentStatusImpactDuration
2026-07-22 17:04 UTCCloud Help Desk - Performance issues, slow page loading and error messagesresolvedminor2 h 41 min
2026-06-22 14:06 UTCCloud Help Desk - Error page when loading ticketsresolvedmajor5 h 34 min
2026-05-27 13:07 UTCCloud Help Desk - Ticket queues not loading or server error pageresolvedmajor6 h 43 min
2026-04-28 15:14 UTCCloud Help Desk Intermittent slow page loadingresolvedminor2 d 2 h
2026-03-03 14:09 UTCCloud Help Desk Delayed email notificationsresolvedminor6 h 43 min
2026-01-02 09:32 UTCCloud Help Desk - Outbound email notifications not being sentresolvedcritical6 d 8 h
2025-10-20 09:55 UTCCloud Help Desk outageresolvedminor21 h 45 min
2025-10-08 14:10 UTCConnectivity Dashboard - "data did not load!" error displayedresolvedcritical42 min
2025-10-07 13:29 UTCCloud Help Desk Mobile App notifications not being sentresolvedminor28 d 1 h
2025-09-08 14:23 UTCCloud Help Desk - Slow or failed page loading for ticketsresolvedminor3 h 45 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 Spiceworks with the template

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

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