Vendor Status Watch

← all vendors

HeroCoders status history

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

4incidents, last 30 days
29incidents, last 90 days
53incidents on record
Incidents per week, last 12 weeks:

How long do HeroCoders incidents last?

9 minmedian incident duration52 measured
7.3 h90th percentile1 in 10 ran longer
0 minmedian, major/critical only6 incidents

From 52 incidents with a vendor-posted start and resolve time. Longest on record: Data Center to Cloud JCMA migration is not working — 5.8 days (2026-06-17 11:46 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 (53)

StartedIncidentStatusImpactDuration
2026-09-11 12:53 UTCSlower response (Issue Checklist Pro)resolvedcritical0 min
2026-09-11 09:08 UTCSlower response (Issue Checklist Pro)resolvedcritical0 min
2026-09-11 09:07 UTCSlower response (Issue Checklist Pro)resolvedcritical0 min
2026-08-29 13:00 UTCSlower response (Issue Checklist Pro)resolvedcritical0 min
2026-08-11 05:30 UTCPartial Outage - Checklist for Jira apps.resolvedminor7 h 18 min
2026-07-31 06:48 UTCChecklist for Jira | Enterprise - degraded performanceresolvedminor9 min
2026-07-28 06:55 UTCSlower response (Issue Checklist Pro)resolvedminor1 h 13 min
2026-07-28 06:46 UTCSlower response (Issue Checklist Pro)resolvedminor8 min
2026-07-28 06:29 UTCChecklist for Jira | Enterprise - degraded performanceresolvedminor1 h 53 min
2026-07-28 06:21 UTCSlower response (Issue Checklist Pro)resolvedminor7 min
2026-07-28 06:11 UTCSlower response (Issue Checklist Pro)resolvedminor3 min
2026-07-28 05:54 UTCSlower response (Issue Checklist Pro)resolvedminor8 min
2026-07-28 05:43 UTCSlower response (Issue Checklist Pro)resolvedminor10 min
2026-07-28 05:09 UTCSlower response (Issue Checklist Pro)resolvedminor9 min
2026-07-28 05:08 UTCSlower response (Issue Checklist Pro)resolvedminor16 min
2026-07-28 04:49 UTCSlower response (Issue Checklist Pro)resolvedminor13 min
2026-07-28 04:49 UTCSlower response (Issue Checklist Pro)resolvedminor13 min
2026-07-27 22:33 UTCSlower response (Issue Checklist Pro)resolvedminor8 min
2026-07-27 22:33 UTCSlower response (Issue Checklist Pro)resolvedminor8 min
2026-07-27 22:33 UTCSlower response (Issue Checklist Pro)resolvedminor8 min
2026-07-27 22:27 UTCSlower response (Issue Checklist Pro)resolvedminor12 h 34 min
2026-07-27 22:22 UTCSlower response (Issue Checklist Pro)resolvedminor12 h 37 min
2026-07-27 12:30 UTCSlower response (Issue Checklist Pro)resolvedminor1 h 19 min
2026-07-27 12:30 UTCSlower response (Issue Checklist Pro)resolvedminor1 h 19 min
2026-07-27 12:30 UTCSlower response (Issue Checklist Pro)resolvedminor1 h 19 min
2026-07-27 12:30 UTCSlower response (Issue Checklist Pro)resolvedminor1 h 19 min
2026-07-01 08:00 UTCThe JCMA is currently undergoing maintenance.resolvedmaintenance8 d 0 h
2026-06-22 14:56 UTCSlower response (Issue Checklist Pro)resolvedminor24 h 23 min
2026-06-22 14:56 UTCSlower response (Issue Checklist Pro)resolvedminor24 h 23 min
2026-06-17 11:46 UTCData Center to Cloud JCMA migration is not workingresolvedminor5 d 18 h
2026-06-11 04:44 UTCSlower response (Issue Checklist Pro)resolvedminor8 min
2026-06-11 04:33 UTCSlower response (Issue Checklist Pro)resolvedminor18 min
2026-06-10 03:42 UTCSlower response (Issue Checklist Pro)resolvedminor18 min
2026-06-10 03:24 UTCSlower response (Issue Checklist Pro)resolvedminor35 min
2026-06-09 23:04 UTCSlower response (Issue Checklist Pro)resolvedminor9 min
2026-06-09 23:04 UTCSlower response (Issue Checklist Pro)resolvedminor9 min
2026-06-09 05:02 UTCSlower response (Issue Checklist Pro)resolvedminor8 min
2026-06-09 05:02 UTCSlower response (Issue Checklist Pro)resolvedminor8 min
2026-06-08 22:18 UTCSlower response (Issue Checklist Pro)resolvedminor8 min
2026-06-08 22:18 UTCSlower response (Issue Checklist Pro)resolvedminor8 min
2026-06-05 05:05 UTCSlower response (Issue Checklist Pro)resolvedminor56 min
2026-06-02 05:02 UTCSlower response (Issue Checklist Pro)resolvedminor8 min
2026-06-02 05:02 UTCSlower response (Issue Checklist Pro)resolvedminor8 min
2026-06-01 05:05 UTCSlower response (Issue Checklist Pro)resolvedminor2 h 35 min
2026-05-29 01:27 UTCSlower response (Issue Checklist Pro)resolvedminor8 min
2026-05-28 22:17 UTCSlower response (Issue Checklist Pro)resolvedminor10 min
2026-05-28 05:56 UTCSlower response (Issue Checklist Pro)resolvedminor8 min
2026-05-28 05:56 UTCSlower response (Issue Checklist Pro)resolvedminor9 min
2026-05-28 05:50 UTCSlower response (Issue Checklist Pro)resolvedminor17 min
2026-05-28 05:47 UTCSlower response (Issue Checklist Pro)resolvedminor21 min
2026-05-27 22:26 UTCSlower response (Issue Checklist Pro)resolvedminor8 min
2026-05-27 14:36 UTCSlower response (Issue Checklist Pro)resolvedcritical3 h 01 min
2026-05-27 14:31 UTCSlower response (Issue Checklist Pro)resolvedcritical3 h 06 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 HeroCoders with the template

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

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