Vendor Status Watch

← all vendors

Gladly status history

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

4incidents, last 30 days
7incidents, last 90 days
23incidents on record
Incidents per week, last 12 weeks:

How long do Gladly incidents last?

115 minmedian incident duration23 measured
8.8 h90th percentile1 in 10 ran longer
53 minmedian, major/critical only9 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-10 15:08 UTCIntermittent Report Loading Issuesresolvedmajor9 h 22 min
2026-09-09 22:19 UTCReports Not Loadingresolvedminor4 h 25 min
2026-09-09 12:50 UTCReports not loadingresolvedminor1 h 59 min
2026-08-31 22:55 UTCReports not loadingresolvedminor4 h 47 min
2026-08-01 06:06 UTCInvestigating Login Issueresolvedcritical53 min
2026-07-30 19:37 UTCGladly AI Elevated Handoffs on Chat, Email and SMSresolvedminor3 min
2026-06-22 13:52 UTCInvestigating Gladly Team not loadingresolvedminor3 h 06 min
2026-06-02 14:52 UTCGladly Team not loadingresolvednone1 h 28 min
2026-05-22 04:08 UTCIntermittent issues loading conversations from the APAC regionresolvedminor1 h 16 min
2026-05-20 19:31 UTCGladly AI Issues Identifiedresolvedmajor1 h 55 min
2026-05-08 01:24 UTCIntermittent Latency in Liveboards and Routingresolvedminor1 h 55 min
2026-04-02 05:43 UTCGladly Login Issuesresolvedmajor0 min
2026-01-27 19:06 UTCIncreased Unexpected Handoffs (Gladly Structured Threads - Legacy)resolvednone8 h 51 min
2026-01-22 07:51 UTCInvestigating Login Issueresolvedcritical26 min
2026-01-17 19:43 UTCIntermittent issues loading conversationsresolvednone12 min
2026-01-08 06:02 UTCGladly Login Issues Upon Page Refreshresolvedmajor0 min
2025-12-19 16:59 UTCInvestigating Latencyresolvedminor1 h 04 min
2025-12-05 08:56 UTCInvestigating Login Issueresolvedcritical24 min
2025-10-20 14:16 UTCInvestigating Performance Issueresolvedminor7 h 44 min
2025-10-20 07:10 UTCInvestigating Performance Issueresolvedcritical2 h 45 min
2025-10-09 13:24 UTC'Shared' reports category missing (Insight Builder) and Language filterresolvednone10 h 10 min
2025-09-25 00:39 UTCGladly Reports and Insight Builder Data Latencyresolvedminor33 min
2025-08-21 17:35 UTCUnable to log into Gladlyresolvedmajor2 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
}