Totango status history
Current state: operational — “All Systems Operational” per https://status.totango.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Totango incidents last?
From 3 incidents with a vendor-posted start and resolve time. Longest on record: Application not loading — 5.4 h (2025-10-20 09:45 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 (3)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-02-25 19:20 UTC | Account and Segment Experiencing High Load Times | resolved | minor | 3 h 13 min |
| 2025-12-09 16:25 UTC | Totango Performance Issues | resolved | minor | 2 h 18 min |
| 2025-10-20 09:45 UTC | Application not loading | resolved | none | 5 h 22 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 Totango with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"totango"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
