Vendor Status Watch

← all vendors

Helpjuice status history

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

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

How long do Helpjuice incidents last?

67 minmedian incident duration4 measured
94 min90th percentile1 in 10 ran longer
76 minmedian, major/critical only2 incidents

From 4 incidents with a vendor-posted start and resolve time. Longest on record: DB Maintenance — 94 min (2026-05-09 17:09 UTC). Excluded, never estimated: 1 scheduled maintenance. 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 (5)

StartedIncidentStatusImpactDuration
2026-08-12 11:46 UTCRead-Only Mode Activatedresolvedmaintenance4 h 13 min
2026-05-09 17:09 UTCDB Maintenanceresolvedmajor1 h 34 min
2026-01-28 17:00 UTCSlowness Issuesresolvednone0 min
2026-01-06 16:27 UTCDegraded performance on knowledge basesresolvedminor1 h 17 min
2025-10-08 13:42 UTCDegraded performance on knowledge basesresolvedmajor58 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 Helpjuice with the template

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

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