Gladly status history
Current state: operational — “All Systems Operational” per https://gladly.statuspage.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Gladly incidents last?
From 23 incidents with a vendor-posted start and resolve time. Longest on record: 'Shared' reports category missing (Insight Builder) and Language filter — 10.2 h (2025-10-09 13:24 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 (23)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-10 15:08 UTC | Intermittent Report Loading Issues | resolved | major | 9 h 22 min |
| 2026-09-09 22:19 UTC | Reports Not Loading | resolved | minor | 4 h 25 min |
| 2026-09-09 12:50 UTC | Reports not loading | resolved | minor | 1 h 59 min |
| 2026-08-31 22:55 UTC | Reports not loading | resolved | minor | 4 h 47 min |
| 2026-08-01 06:06 UTC | Investigating Login Issue | resolved | critical | 53 min |
| 2026-07-30 19:37 UTC | Gladly AI Elevated Handoffs on Chat, Email and SMS | resolved | minor | 3 min |
| 2026-06-22 13:52 UTC | Investigating Gladly Team not loading | resolved | minor | 3 h 06 min |
| 2026-06-02 14:52 UTC | Gladly Team not loading | resolved | none | 1 h 28 min |
| 2026-05-22 04:08 UTC | Intermittent issues loading conversations from the APAC region | resolved | minor | 1 h 16 min |
| 2026-05-20 19:31 UTC | Gladly AI Issues Identified | resolved | major | 1 h 55 min |
| 2026-05-08 01:24 UTC | Intermittent Latency in Liveboards and Routing | resolved | minor | 1 h 55 min |
| 2026-04-02 05:43 UTC | Gladly Login Issues | resolved | major | 0 min |
| 2026-01-27 19:06 UTC | Increased Unexpected Handoffs (Gladly Structured Threads - Legacy) | resolved | none | 8 h 51 min |
| 2026-01-22 07:51 UTC | Investigating Login Issue | resolved | critical | 26 min |
| 2026-01-17 19:43 UTC | Intermittent issues loading conversations | resolved | none | 12 min |
| 2026-01-08 06:02 UTC | Gladly Login Issues Upon Page Refresh | resolved | major | 0 min |
| 2025-12-19 16:59 UTC | Investigating Latency | resolved | minor | 1 h 04 min |
| 2025-12-05 08:56 UTC | Investigating Login Issue | resolved | critical | 24 min |
| 2025-10-20 14:16 UTC | Investigating Performance Issue | resolved | minor | 7 h 44 min |
| 2025-10-20 07:10 UTC | Investigating Performance Issue | resolved | critical | 2 h 45 min |
| 2025-10-09 13:24 UTC | 'Shared' reports category missing (Insight Builder) and Language filter | resolved | none | 10 h 10 min |
| 2025-09-25 00:39 UTC | Gladly Reports and Insight Builder Data Latency | resolved | minor | 33 min |
| 2025-08-21 17:35 UTC | Unable to log into Gladly | resolved | major | 2 h 23 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 Gladly with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"gladly"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}