Vendor Status Watch

← all vendors

Nutshell status history

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

0incidents, last 30 days
1incidents, last 90 days
7incidents on record
Incidents per week, last 12 weeks:
Get Nutshell alerts in your Slack — free templateRSS for Nutshell

How long do Nutshell incidents last?

30 minmedian incident duration7 measured
8.0 h90th percentile1 in 10 ran longer
—median, major/critical onlynone posted

From 7 incidents with a vendor-posted start and resolve time. Longest on record: Nutshell outage — 9.0 h (2025-10-20 12:30 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 (7)

StartedIncidentStatusImpactDuration
2026-07-08 00:49 UTCDatabase Upgraderesolvednone11 min
2026-06-04 16:45 UTCSlowdown & delays for some customersresolvedminor30 min
2026-04-10 00:17 UTCDatabase upgraderesolvednone4 h 52 min
2026-03-09 21:23 UTCReports of Nutshell not loading for several customersresolvedminor14 min
2025-10-20 12:30 UTCNutshell outageresolvedminor8 h 58 min
2025-09-23 12:59 UTCInvestigating reports of slownessresolvedminor7 h 57 min
2025-08-21 12:00 UTCTemporary Nutshell access issuesresolvednone0 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 Nutshell with the template

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

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