Totango Outage History

Totango is up right now

Totango had 6 outages in the last 2 years totaling 18h 44m of downtime — averaging 0.2 incidents per month.

There were 6 Totango outages since June 10, 2025 totaling 18h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.totango.com

Minor February 25, 2026

Account and Segment Experiencing High Load Times

Detected by Pingoru
Feb 25, 2026, 07:20 PM UTC
Resolved
Feb 25, 2026, 10:34 PM UTC
Duration
3h 13m
Affected: Totango Web Application
Timeline · 5 updates
  1. investigating Feb 25, 2026, 07:20 PM UTC

    We are currently investigating the issue with high load times in Accounts and Segments

  2. identified Feb 25, 2026, 07:21 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Feb 25, 2026, 07:31 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Feb 25, 2026, 09:35 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Feb 25, 2026, 10:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 9, 2025

Totango Performance Issues

Detected by Pingoru
Dec 09, 2025, 04:25 PM UTC
Resolved
Dec 09, 2025, 06:43 PM UTC
Duration
2h 18m
Affected: Totango Web Application
Timeline · 4 updates
  1. investigating Dec 09, 2025, 04:25 PM UTC

    We are currently investigating this issue.

  2. identified Dec 09, 2025, 05:50 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Dec 09, 2025, 05:53 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Dec 09, 2025, 06:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 20, 2025

Application not loading

Detected by Pingoru
Oct 20, 2025, 09:45 AM UTC
Resolved
Oct 20, 2025, 03:07 PM UTC
Duration
5h 22m
Affected: Totango Web Application
Timeline · 2 updates
  1. monitoring Oct 20, 2025, 09:45 AM UTC

    Earlier today, our application experienced login and availability issues due to a widespread AWS outage. During this time, we were also unable to update our status page as it was affected by the same incident. Service has now been fully restored, and the application is operational again. We’ll continue monitoring to ensure stability. Thank you for your patience and understanding.

  2. resolved Oct 20, 2025, 03:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 1, 2025

AI CSM Chatbot Blocking Visibility

Detected by Pingoru
Aug 01, 2025, 02:46 PM UTC
Resolved
Aug 01, 2025, 05:46 PM UTC
Duration
3h
Affected: Totango Web Application
Timeline · 3 updates
  1. identified Aug 01, 2025, 02:46 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Aug 01, 2025, 04:10 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 01, 2025, 05:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 22, 2025

Degraded Performance issues

Detected by Pingoru
Jul 22, 2025, 09:23 AM UTC
Resolved
Jul 22, 2025, 11:44 AM UTC
Duration
2h 20m
Affected: Totango Web Application
Timeline · 4 updates
  1. investigating Jul 22, 2025, 09:23 AM UTC

    We are currently investigating this issue.

  2. investigating Jul 22, 2025, 09:24 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jul 22, 2025, 11:23 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 22, 2025, 11:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 10, 2025

Login and degraded performance issues

Detected by Pingoru
Jun 10, 2025, 10:53 AM UTC
Resolved
Jun 10, 2025, 01:23 PM UTC
Duration
2h 29m
Affected: Totango Web Application
Timeline · 3 updates
  1. investigating Jun 10, 2025, 10:53 AM UTC

    We are currently investigating this issue.

  2. monitoring Jun 10, 2025, 11:53 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 10, 2025, 01:23 PM UTC

    This incident has been resolved.

Read the full incident report →